-
Notifications
You must be signed in to change notification settings - Fork 0
fix: resolve critical meeting stability and UI regressions #65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+27
−18
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: Brints/spoken-api
Length of output: 1427
🏁 Script executed:
Repository: Brints/spoken-api
Length of output: 1458
🏁 Script executed:
Repository: Brints/spoken-api
Length of output: 174
🏁 Script executed:
Repository: Brints/spoken-api
Length of output: 1155
🏁 Script executed:
Repository: Brints/spoken-api
Length of output: 273
🏁 Script executed:
Repository: Brints/spoken-api
Length of output: 2459
🏁 Script executed:
Repository: Brints/spoken-api
Length of output: 1729
🏁 Script executed:
Repository: Brints/spoken-api
Length of output: 1739
Verify
ConnectionManager.send_to_usersignature and connection lookup semantics.The new payload correctly enables client routing per the PR objective. The implementation confirms:
Signature match:
send_to_user(room_code: str, target_user_id: str, message: dict)is correctly called with positional arguments in the right order.Connection keying: Connections are consistently keyed by
user_idinactive_connections[room_code][user_id]. The listener retrieves the target WebSocket using the same key. However, if the admitted user's WebSocket is not yet established or has disconnected, the unicast message will silently drop with only a log warning—no error is propagated back to the caller.State mutation risk: The user is admitted in state on line 502 before the send attempt on lines 508–510. If the send fails (or silently drops), the user is still marked admitted in Redis but never notified. Consider wrapping the send in a try/catch and logging the error, or implement a notification retry mechanism so the user can reconnect and receive the admitted signal.
🤖 Prompt for AI Agents