-
Notifications
You must be signed in to change notification settings - Fork 10.9k
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
regression: Handle live setting forget user session on window close update #33133
Conversation
Looks like this PR is ready to merge! 🎉 |
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release-6.12.0 #33133 +/- ##
==================================================
- Coverage 59.39% 59.38% -0.01%
==================================================
Files 2547 2547
Lines 63241 63242 +1
Branches 14223 14225 +2
==================================================
Hits 37559 37559
- Misses 22974 22975 +1
Partials 2708 2708
Flags with carried forward coverage won't be shown. Click here to find out more. |
/backport 6.10.5 |
Pull request #33150 added to Project: "Patch 6.10.5" |
/patch |
3 similar comments
/patch |
/patch |
/patch |
Pull request #33165 added to Project: "Patch 6.11.2" |
Proposed changes (including videos or screenshots)
Meteor recently developed a way to choose the client storage location between local storage and session storage.
We recently started configuring meteor to choose between both location options based on our setting
Accounts_ForgetUserSessionOnWindowClose
.There was a small issue, we are handling these updates in a
Tracker.autorun
which runs everytime any dependency changes. In this case, it wasn't handling this setting change on a live user session.We shouldn't change the client storage location in the middle of an active session, so this PR fixes it by stopping the autorun and which stops the listening of live setting update, essentially just configuring the client storage location just once in a session.
Issue(s)
Steps to test or reproduce
Further comments
CORE-653