SOlution 1.0 by sborichevskyi · Pull Request #131 · mate-academy/node_chat

sborichevskyi · 2025-09-18T15:05:35Z

No description provided.

mateacademy-ai-mentor

Review Summary

Decision: Request changes — There are multiple critical blockers that break core functionality and violate requirements.

Critical issues to fix:

src/createServer.js: Root route uses res.sendStatus(200).json(...) which sends two responses and will throw “Cannot set headers after they are sent.” Change to res.status(200).json({ message: 'Server is running' }) (line ~20).
src/services/message.service.js and retrieval path: Messages must include author and be ordered chronologically. Update findRoomsMessages to include User and order: [['createdAt','ASC']], and return DTOs like { author: user.name, text, time: createdAt }. Also change sendMessage to return the created DB record (with createdAt and author), not the plain input object.
src/messageServer.js: Calls non-existent messageService.createMessage (runtime error). Align with the service (sendMessage) or export createMessage from the service. Wrap async handlers in try/catch and ensure broadcasts include author and time.
Room join flow: There is no HTTP endpoint to persist DB membership. Add a route like POST /:roomId/join (room.router.js) and implement joinRoom in the controller to add req.user to the room in the DB; otherwise isUserInRoom blocks history access for new members.
src/routes/room.router.js: Create route is incorrectly mounted at POST('/:roomId'). Change to POST('/') to match controller expectations and avoid confusion.
src/controllers/room.controller.js (mergeRooms): Validate req.user before using user.id and normalize targetRoomId (e.g., parseInt) before passing to services to avoid crashes/type issues. Remove the redundant if (!roomInfo) check.

Minor improvements (non-blockers): add centralized error-handling middleware; normalize headers in auth middlewares; await Room.create in room.service.createRoom; validate userId in user.controller routes/authorization.

You’ve built a solid structure (models, associations, routers), but resolving the blockers above is necessary for the chat to function (message creation/broadcasting, history with author/time, and joining rooms). Keep going—you’re close.

✨ Please rate this review in the Platform's notification center¹. I will be grateful for your feedback! ✨

Important

Fix the issues, commit the changes, and then re-request my review using the Re-request review button² in the Reviewers tab.

Tip

If you have any comments about this review, please leave a message in the Add a comment section below and mention me with the @mateacademy-ai-mentor tag³.
I will read your message during my next review of your pull request. Please do not reply directly to my comments, as that feature is not supported yet.

Caution

Do not close the pull request until the review is complete. Closing it early can lead to unexpected behavior and disrupt the review process.

mateacademy-ai-mentor · 2025-09-18T17:50:44Z

+const getRoomInfoByRoomId = async (req, res) => {
+  const { roomId } = req.params;
+  const room = await roomService.findRoomById(roomId);
+  const messages = await messageService.findRoomsMessages(roomId);


The controller calls messageService.findRoomsMessages(roomId) but the current message service returns raw messages without joining the User (author) and without ordering by creation time. The task requires that messages include author, time and text and that history is returned chronologically. Update message retrieval to include the User association and order by createdAt (ASC), or have the service return mapped objects like { author, text, time } so clients get the author name and timestamp. See message.service.js and message model for context.

mateacademy-ai-mentor · 2025-09-18T17:50:44Z

+
+  if (!roomInfo) {
+    return res.status(400).json({ message: 'Cannot transfer rooms info' });
+  }


This check is redundant: roomInfo was just constructed and will always be truthy. Remove the if (!roomInfo) block — it cannot fail and adds unnecessary code. Keeping it may hide real errors elsewhere; instead, rely on earlier checks and propagate actual errors if needed.

mateacademy-ai-mentor · 2025-09-18T17:50:44Z

+  const user = req.user;
+  const { targetRoomId } = req.body;
+
+  const usersRooms = await roomService.findRoomsByUserId(user.id);


In mergeRooms the code calls roomService.findRoomsByUserId(user.id) before checking whether user exists. If req.user is undefined this will throw. Validate user (and currentRoom) before using user.id or calling services that use it. Reorder the checks so if (!user) appears before any use of user.id.

mateacademy-ai-mentor · 2025-09-18T17:50:44Z

+
+  if (!user) {
+    return res.status(404).json({ error: 'User not found' });
+  }


The user existence check happens after usersRooms is used. Move the if (!user) check earlier (before calling findRoomsByUserId) to avoid possible runtime exceptions when req.user is missing.

mateacademy-ai-mentor · 2025-09-18T17:50:44Z

+  await userService.mergeUsers(currentRoom.id, targetRoomId);
+  await messageService.mergeMessages(currentRoom.id, targetRoomId);


When you call userService.mergeUsers(currentRoom.id, targetRoomId) and messageService.mergeMessages(currentRoom.id, targetRoomId) you pass targetRoomId directly (likely a string). Earlier you parsed it to find targetRoom. Normalize the ID (e.g. parseInt(targetRoomId, 10)) or ensure the services accept string IDs — keep types consistent to avoid subtle bugs.

mateacademy-ai-mentor · 2025-09-18T17:50:50Z

+  for (const user of usersToMerge) {
+    if (!targetUserIds.has(user.id)) {
+      await targetRoom.addUser(user);
+    }
+  }
+
+  return { merged: usersToMerge.length, into: targetRoomId };


mergeUsers returns { merged: usersToMerge.length, into: targetRoomId }, which reports the total number of users in the source room rather than how many users were actually added to the target. Instead, track a counter of how many users are newly added (increment when await targetRoom.addUser(user) runs) and return that value so callers get a truthful merged count. This fixes incorrect reporting when some users are already present in the target room.

mateacademy-ai-mentor · 2025-09-18T17:50:50Z

+const findUsersByRoomId = async (roomId) => {
+  const room = await Room.findByPk(roomId, {
+    include: User,
+  });


Good: findUsersByRoomId uses Room.findByPk(roomId, { include: User }) and returns room.Users. This leverages the model associations correctly to fetch members of a room. Keep this approach — it aligns with the project associations and makes merge logic simpler elsewhere.

mateacademy-ai-mentor · 2025-09-18T17:50:50Z

+  return async function (req, res, next) {
+    try {
+      await action(req, res, next);


This wrapper correctly awaits the async action and forwards errors to the Express error handler via next(error) — this is the correct pattern for async Express controllers and matches how routers wrap controllers in this project (e.g. user and room routers). No change required here.

mateacademy-ai-mentor · 2025-09-18T17:50:50Z

+    } catch (error) {
+      next(error);


Optional improvement: consider adding conditional logging here (e.g. log in development) before forwarding the error to help debugging. Keep logging behind an environment check so production logs are not noisy.

mateacademy-ai-mentor · 2025-09-18T17:50:51Z

+export const catchError = (action) => {
+  return async function (req, res, next) {
+    try {
+      await action(req, res, next);


Optional: in some test scenarios it can be helpful to return the action's return value (e.g. return await action(...)) so callers can inspect it; not required for Express but worth considering if you introduce tests that call the wrapper directly.

mateacademy-ai-mentor

Sorry, the pull request review was unsuccessful for the following reasons:

Warning

No changes were made in the pull request since the last review. Please make sure that you have added files to the pull request and committed the changes.
_{[CODE: NCM]}

If the issue is within your control, please address it.
The next review attempt will automatically launch in about 1 hour.
If you believe this is an error or need assistance, please contact the support team.

mateacademy-ai-mentor

Sorry, the pull request review was unsuccessful for the following reasons:

Warning

No changes were made in the pull request since the last review. Please make sure that you have added files to the pull request and committed the changes.
_{[CODE: NCM]}

If the issue is within your control, please address it.
The next review attempt will automatically launch in about 1 hour.
If you believe this is an error or need assistance, please contact the support team.

mateacademy-ai-mentor

Review Summary

Decision: REQUEST_CHANGES

There are several critical blockers that will break core flows at runtime and prevent the task from being completed reliably.

Critical issues to fix:

joinRoom passes arguments in the wrong order: roomService.addUserToRoom(roomId, userId) but the service expects (userId, roomId). Swap to roomService.addUserToRoom(userId, roomId) in src/controllers/room.controller.js (join handler). This currently prevents persisting membership and blocks accessing history via membership-guarded routes.
Message merge is broken: messageService.mergeMessages uses DTOs from findRoomsMessages and then calls .save() on them. Replace logic to operate on Message model instances (e.g., Message.update({ roomId: target }, { where: { roomId: source } }) or fetch instances and save in a transaction). As-is, mergeRooms will throw at runtime.
Socket message creation mismatch: in src/messageServer.js you call messageService.createMessage({ roomId, userId, text }), but the service signature is (roomId, userId, text). Change the call to await messageService.createMessage(roomId, userId, text) (or adjust the service to accept an object).
userService.getUserNameById is incorrect: wrong where key and missing await. Implement with const user = await User.findByPk(userId); return user ? user.name : null; to avoid runtime exceptions.
Route error handling: the join route in src/routes/room.router.js is not wrapped with catchError. Wrap it to ensure async errors are forwarded: roomRouter.post('/:roomId/join', isAuth, catchError(roomController.joinRoom));.

Important improvements (non-blocking but recommended):

In getRoomInfoByRoomId, validate the room exists before fetching messages; remove the unreachable if (!roomInfo) check; normalize roomId to a number.
Enforce non-empty text for messages in message.service.createMessage and in the socket handler (trim and validate before saving).
Harden middlewares (isAuth, isNotAuth, isUserInRoom) with trimming, defensive checks for req.user, and try/catch that calls next(err).

You’ve built a solid structure with correct models, associations, and route coverage. Fixing the blockers above will make joining, messaging, and merging reliable. Keep going — you’re close.

✨ Please rate this review in the Platform's notification center¹. I will be grateful for your feedback! ✨

Important

Fix the issues, commit the changes, and then re-request my review using the Re-request review button² in the Reviewers tab.

Tip

If you have any comments about this review, please leave a message in the Add a comment section below and mention me with the @mateacademy-ai-mentor tag³.
I will read your message during my next review of your pull request. Please do not reply directly to my comments, as that feature is not supported yet.

Caution

Do not close the pull request until the review is complete. Closing it early can lead to unexpected behavior and disrupt the review process.

mateacademy-ai-mentor · 2025-09-19T11:52:10Z

+const getRoomInfoByRoomId = async (req, res) => {
+  const { roomId } = req.params;
+  const room = await roomService.findRoomById(roomId);
+  const messages = await messageService.findRoomsMessages(roomId);


In getRoomInfoByRoomId you call messageService.findRoomsMessages(roomId) before validating the room. If the room doesn't exist you still made a DB call. Move the room existence check before fetching messages so you only query messages for an existing room. This avoids unnecessary work and clarifies error cases. See the call on this line.

mateacademy-ai-mentor · 2025-09-19T11:52:10Z

+  if (!roomId || !room) {
+    return res.status(404).json({ message: 'Room not Found' });


This if (!roomId || !room) check is good (you verify existence) but it should run before any message queries (see previous comment). Also consider normalizing/parsing roomId to an integer consistently if other code expects numeric ids.

mateacademy-ai-mentor · 2025-09-19T11:52:10Z

+    messages,
+  };
+
+  if (!roomInfo) {


The if (!roomInfo) check is unreachable: roomInfo is just constructed above and will always be truthy. Remove this redundant check to simplify the flow.

mateacademy-ai-mentor · 2025-09-19T11:52:10Z

+    return res.status(404).json({ message: 'Room not found' });
+  }
+
+  await roomService.addUserToRoom(roomId, userId);


Critical runtime bug: joinRoom calls roomService.addUserToRoom(roomId, userId) but addUserToRoom in room.service.js expects the signature (userId, roomId) (userId first) — passing arguments in the wrong order will make the function attempt to find the wrong user/room and fails to persist membership. Swap the arguments to roomService.addUserToRoom(userId, roomId) (or adjust the service signature) to fix joining. See room.service.js for the expected signature and implementation details .

mateacademy-ai-mentor · 2025-09-19T11:52:10Z

+  }
+
+  await roomService.addUserToRoom(roomId, userId);
+


The router currently mounts the join route without the catchError wrapper, so exceptions thrown by joinRoom won't be forwarded to the central error handler. Ensure this route is wrapped consistently (or handle errors inside this function). See router mounting of other routes for examples (they use catchError) .

mateacademy-ai-mentor · 2025-09-19T11:52:15Z

+
+  if (!room) {
+    return [];


findUsersByRoomId returns an empty array if the room doesn't exist. This is acceptable, but be explicit in docs or code comments about this behavior so callers understand they won't get an error but an empty list when the room is missing.

mateacademy-ai-mentor · 2025-09-19T11:52:16Z

+export const catchError = (action) => {
+  return async function (req, res, next) {
+    try {
+      await action(req, res, next);


The wrapper awaits the provided action. If any handler relies on this (uncommon for Express handlers but possible), consider invoking the action with the same this context to be safe: await action.call(this, req, res, next); This preserves context for edge cases.

mateacademy-ai-mentor · 2025-09-19T11:52:16Z

@@ -0,0 +1,9 @@
+export const catchError = (action) => {
+  return async function (req, res, next) {


The returned function signature (req, res, next) is correct for wrapping Express route handlers. Note: this helper must be applied where used (controllers are wrapped in routers), but middleware functions are not automatically wrapped. Make sure any async middleware that can throw is either wrapped or implements its own try/catch.

mateacademy-ai-mentor · 2025-09-19T11:52:16Z

+    } catch (error) {
+      next(error);


Catching the error and calling next(error) is the right approach to forward errors to central error middleware. Optionally you can enrich or log the error here if you want request-scoped logging before forwarding, but that is a project decision rather than a necessity.

mateacademy-ai-mentor · 2025-09-19T11:52:16Z

+export const catchError = (action) => {
+  return async function (req, res, next) {
+    try {
+      await action(req, res, next);
+    } catch (error) {
+      next(error);
+    }
+  };
+};


No functional problems found. The await handles both async functions and functions that return promises, so no additional branching is required to support typical controller patterns. Keep using this helper for async controllers as shown in routers.

mateacademy-ai-mentor

Sorry, the pull request review was unsuccessful for the following reasons:

Warning

No changes were made in the pull request since the last review. Please make sure that you have added files to the pull request and committed the changes.
_{[CODE: NCM]}

If the issue is within your control, please address it.
The next review attempt will automatically launch in about 1 hour.
If you believe this is an error or need assistance, please contact the support team.

mateacademy-ai-mentor

Review Summary

Educational approval: you’ve built a clear server structure with solid separation of concerns (controllers/services), correct Sequelize associations, and thoughtful router/middleware wiring. Nice fixes like the correct addUserToRoom argument order in joinRoom stand out.

Critical improvements to address next:

Requirement 1.6: in src/controllers/room.controller.js, joinRoom should return history after adding the user; fetch via await messageService.findRoomsMessages(parsedRoomId) and include in the response. Ensure messages contain author, text, and time in a consistent format (ISO).
Robust ID/auth checks: normalize roomId/userId with parseInt/Number.isNaN in room and user controllers/middlewares; verify req.user before using it (createRoom/join/rename/delete).
Socket layer: in src/messageServer.js fix the call to messageService.createMessage (use positional args), authenticate the socket (resolve user server-side), validate non-empty text, and emit room history on join.
Merge/delete consistency: wrap merge operations in a DB transaction and prefer service-level helpers for message deletes; avoid direct Message.destroy if a service exists.
Small polish: add a global Express error handler (createServer.js), align Socket.IO CORS with Express, trim/validate usernames in controllers/services, and fix getUserNameById to await and query by id.

Overall, you’re very close — address these targeted fixes to fully meet the checklist and harden runtime behavior. Great progress so far — keep it up!

✨ Please rate this review in the Platform's notification center¹. I will be grateful for your feedback! ✨

Rate AI review example ↩

mateacademy-ai-mentor · 2025-09-19T14:20:56Z

+
+  await roomService.addUserToRoom(userId, roomId);
+
+  return res.status(200).json({ message: 'Joined room successfully' });


Requirement 1.6 (message history retrieval on join) is not fulfilled here. After adding the user to the room you must return the room's previous messages so the client can display history. Consider calling messageService.findRoomsMessages(...) and include the messages in the JSON response (and/or include members). Example flow:

add user to room

fetch messages = await messageService.findRoomsMessages(parsedRoomId)

return { message: 'Joined room successfully', room: { id, name }, messages }
This change is required by the task checklist.

mateacademy-ai-mentor · 2025-09-19T14:20:56Z

+
+  const room = await roomService.findRoomById(roomId);


You're passing req.params.roomId directly into findRoomById. Normalize and validate it first (parseInt + Number.isNaN check) to avoid edge cases when the service expects a number. Also validate the result before proceeding. Example: const id = parseInt(roomId, 10); if (Number.isNaN(id)) return 400... then use id in service calls.

mateacademy-ai-mentor · 2025-09-19T14:20:56Z

+  const user = req.user;
+
+  if (!name) {
+    return res.status(400).json({ message: 'Room name is required' });
+  }
+
+  const newRoom = await roomService.createRoom(name);
+
+  if (!newRoom) {
+    return res.status(400).json({ message: 'Cannot create the room' });
+  }
+
+  await newRoom.addUser(user);


createRoom assumes req.user exists and then does newRoom.addUser(user). Ensure req.user is present (return 401 if not authenticated) and confirm whether addUser expects the user instance or an id. If it expects an id, use newRoom.addUser(user.id). Add an explicit check before calling addUser to avoid runtime errors when req.user is absent.

mateacademy-ai-mentor · 2025-09-19T14:20:56Z

+const deleteRoom = async (req, res) => {
+  const { roomId } = req.params;
+  const room = await roomService.findRoomById(roomId);
+
+  if (!roomId || !room) {
+    return res.status(404).json({ message: 'Room not Found' });
+  }


In deleteRoom you call roomService.findRoomById(roomId) without normalizing the id. Also the existence check uses if (!roomId || !room) which doesn't validate numeric IDs. Parse the roomId and validate with Number.isNaN, then check the room. This avoids ambiguity and possible false positives/negatives.

mateacademy-ai-mentor · 2025-09-19T14:20:56Z

+  }
+
+  await room.setUsers([]);
+  await Message.destroy({ where: { roomId: room.id } });


Line performing Message.destroy will remove message rows directly from the model. Prefer using a messageService.deleteMessagesByRoom(room.id) if available so message-related logic stays in one place and any hooks/side-effects are handled consistently. If a service helper doesn't exist, add one or document why direct model access is used.

mateacademy-ai-mentor · 2025-09-19T14:21:02Z

+const mergeUsers = async (roomId, targetRoomId) => {
+  const room = await roomService.findRoomById(roomId);
+  const targetRoom = await roomService.findRoomById(targetRoomId);
+  const usersToMerge = await findUsersByRoomId(roomId);
+  const targetUsers = await findUsersByRoomId(targetRoomId);
+
+  if (!room || !targetRoom) {
+    throw new Error('One or both rooms not found');
+  }
+
+  const targetUserIds = new Set(targetUsers.map((u) => u.id));
+
+  for (const user of usersToMerge) {
+    if (!targetUserIds.has(user.id)) {
+      await targetRoom.addUser(user);
+    }
+  }
+
+  return { merged: usersToMerge.length, into: targetRoomId };


mergeUsers has two issues:

It calls roomService.findRoomById and roomService is the exported object — prefer calling a local helper or refactoring to avoid circular import fragility. 2) The returned { merged: usersToMerge.length } reports the total users in the source room, not the number actually added to the target (some may already exist there). Consider computing addedCount during the loop and returning that, and validate inputs earlier (ensure rooms exist before attempting to find users). You may also want to run the adds in a DB transaction for atomicity.

mateacademy-ai-mentor · 2025-09-19T14:21:02Z

+const getUserNameById = async (userId) => {
+  const user = User.findOne({ where: { userId } });
+
+  return user.name;


Critical bug: getUserNameById does not await the DB call and uses the wrong where clause. Current code: const user = User.findOne({ where: { userId } }); return user.name; This will return a Promise and then attempt to access .name, causing a runtime error. Fix it by awaiting and using the correct key or findByPk, e.g.: const user = await User.findByPk(userId); return user ? user.name : null;. This is used by other services and is critical for message author resolution.

mateacademy-ai-mentor · 2025-09-19T14:21:02Z

+export const catchError = (action) => {
+  return async function (req, res, next) {


The wrapper properly awaits the action and forwards any error via next(error), which is the intended behavior for async route handlers in Express. Good. Consider adding a short comment above the function explaining it wraps 3-argument middlewares (req, res, next) to improve clarity.

mateacademy-ai-mentor · 2025-09-19T14:21:02Z

+export const catchError = (action) => {
+  return async function (req, res, next) {
+    try {
+      await action.call(this, req, res, next);


You're calling await action.call(this, req, res, next); which preserves context. As a small defensive improvement, you could validate that action is a function before calling it to fail early with a clearer error if misused (e.g., if (typeof action !== 'function') throw new Error('catchError expects a function')). This is optional but helpful during debugging.

mateacademy-ai-mentor · 2025-09-19T14:21:03Z

+    try {
+      await action.call(this, req, res, next);
+    } catch (error) {
+      next(error);


The middleware forwards errors with next(error) which relies on the app having a global Express error handler to return consistent JSON to clients. Ensure createServer.js registers an error-handling middleware after routes to handle these errors (log + res.status(...).json({ error: ... })). See createServer.js for where to add it.

mateacademy-ai-mentor

Sorry, the pull request review was unsuccessful for the following reasons:

Warning

Something went wrong while processing the review.
_{[CODE: GAE]}

If the issue is within your control, please address it.
The next review attempt will automatically launch in about 1 hour.
If you believe this is an error or need assistance, please contact the support team.

mateacademy-ai-mentor

Sorry, the pull request review was unsuccessful for the following reasons:

Warning

The test task has already been approved.
_{[CODE: AAP]}

If the issue is within your control, please address it.
The next review attempt will automatically launch in about 1 hour.
If you believe this is an error or need assistance, please contact the support team.

SOlution 1.0

68ec7e0

mateacademy-ai-mentor suggested changes Sep 18, 2025

View reviewed changes

mateacademy-ai-mentor reviewed Sep 18, 2025

View reviewed changes

Solution 1.1

7939b48

sborichevskyi requested a review from mateacademy-ai-mentor September 19, 2025 11:22

mateacademy-ai-mentor suggested changes Sep 19, 2025

View reviewed changes

mateacademy-ai-mentor reviewed Sep 19, 2025

View reviewed changes

Solution 1.2

bf2905a

sborichevskyi requested a review from mateacademy-ai-mentor September 19, 2025 13:50

mateacademy-ai-mentor approved these changes Sep 19, 2025

View reviewed changes

mateacademy-ai-mentor reviewed Sep 19, 2025

View reviewed changes

		await userService.mergeUsers(currentRoom.id, targetRoomId);
		await messageService.mergeMessages(currentRoom.id, targetRoomId);

		if (!roomId \|\| !room) {
		return res.status(404).json({ message: 'Room not Found' });

		@@ -0,0 +1,9 @@
		export const catchError = (action) => {
		return async function (req, res, next) {


		await roomService.addUserToRoom(userId, roomId);

		return res.status(200).json({ message: 'Joined room successfully' });

Conversation

sborichevskyi commented Sep 18, 2025

Uh oh!

mateacademy-ai-mentor left a comment

Choose a reason for hiding this comment

Review Summary

Footnotes

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mateacademy-ai-mentor left a comment

Choose a reason for hiding this comment

Uh oh!

mateacademy-ai-mentor left a comment

Choose a reason for hiding this comment

Uh oh!

mateacademy-ai-mentor left a comment

Choose a reason for hiding this comment

Review Summary

Footnotes

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mateacademy-ai-mentor left a comment

Choose a reason for hiding this comment

Uh oh!

mateacademy-ai-mentor left a comment

Choose a reason for hiding this comment

Review Summary

Footnotes

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment