-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2024-12-07] [$250] Dedupe multiple LogOut requests #53070
Comments
PR -> #53143 |
Triggered auto assignment to @zanyrenney ( |
@mountiny Please assign me to the issue as well. Thanks. |
$250 to @rojiphil |
Job added to Upwork: https://www.upwork.com/jobs/~021862137674835272041 |
Current assignee @rojiphil is eligible for the External assigner, not assigning anyone new. |
📣 @rojiphil 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
@zanyrenney I have accepted the offer. Thanks. |
payment summary paid @rojiphil $250 via Upwork. |
PR is merged so payment complete and now closing! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.68-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-12-07. 🎊 For reference, here are some details about the assignees on this issue:
|
@rojiphil @zanyrenney @rojiphil The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
Problem
We are seeing some scenarios where multiple LogOut requests are serialized in a row. When multiple such requests are sent, it's redundant, as only one is relevant. It slows down the app, and contributes to server traffic.
Solution
Dedupe multiple LogOut requests
Issue Owner
Current Issue Owner: @Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @zanyrenneyThe text was updated successfully, but these errors were encountered: