Repository navigation
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (3)
💤 Files with no reviewable changes (2)
Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 0 remain after this review. WalkthroughThe automatic presence re-entry failure message now includes the affected ChangesPresence Re-entry Error Message
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to Failed automatic re-entry now identifies the affected client in the 91004 message, and the enabled regression test checks that value. No actionable merge-blocking risk remains in the reviewed changes. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. A rabbit checks the message line Comment |
ttypic
left a comment
There was a problem hiding this comment.
LGTM, thanks for contribution!
RTP17e requires the 91004 ErrorInfo on a failed automatic re-enter to name the member. Interpolate entry.clientId into the existing message, unskip the UTS assertion, and drop the resolved deviations.md entry.
f4f4d87 to
d6d9041
Compare
Summary
RealtimePresence._ensureMyMembersPresent()interpolatesentry.clientIdinto the 91004 ErrorInfo on the channelupdatethat auto re-enter already emits when the ENTER was NACKed. RTP17e requires that message to name the member that failed to re-enter.The UTS test that asserts
reason.messageincludesmy-clientnow runs withoutRUN_DEVIATIONS, and the matchingdeviations.mdentry is removed.Decision: put
entry.clientIdinto the current'Presence auto re-enter failed'string, quoted like the MICRO log in the same function. Alternative: copy Dart (Automatic re-entry failed for clientId "...") or .NET (Cannot automatically re-enter {clientId} on channel {channelName}). The spec and the UTS test only require the clientId to appear, so keeping the existing phrase is the smallest change. Can switch to a sibling SDK's string.Independent of #2301.
Fixes #2209
Test plan
npx mocha --no-config --exit --require tsx/cjs --timeout 30000 --grep "RTP17e - failed re-entry emits UPDATE with error" test/uts/realtime/unit/presence/realtime_presence_reentry.test.tspasses withoutRUN_DEVIATIONS(Node 20)expected 'Presence auto re-enter failed' to include 'my-client')realtime_presence_reentry.test.tsstill passSummary by CodeRabbit