-
Notifications
You must be signed in to change notification settings - Fork 213
fix: session rotation was relying on in-memory values and so could get out of sync with reality #2666
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
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
4 files reviewed, no comments
|
Size Change: -1.11 kB (-0.02%) Total Size: 5.11 MB
ℹ️ View Unchanged
|
56c148a to
8bae54b
Compare
…t out of sync with reality
8bae54b to
13ededf
Compare

Problem
we saw a team 2 session that appeared to be 70+ hours long
it had gone idle after 1h40
but when the user reactivated the session, the first few events in the replay stream picked up the old session id
this is supposed to be impossible 🫠
Changes
Release info Sub-libraries affected
Libraries affected
Checklist
If releasing new changes
pnpm changesetto generate a changeset file