-
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-04-25] GetMissinOnyxMessages being executed several times #39992
Comments
Triggered auto assignment to @CortneyOfstad ( |
Taking over! |
Job added to Upwork: https://www.upwork.com/jobs/~0101c143b6e4d4468d |
Current assignee @allroundexperts is eligible for the Internal assigner, not assigning anyone new. |
PR on staging as of last week — continuing to keep an eye on this! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.62-17 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-04-25. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Not overdue — payment is set for tomorrow. @allroundexperts can you have the check list completed by EOD? Thanks! |
I don't think a checklist is needed here. |
Payment Summary
BugZero Checklist (@CortneyOfstad)
|
This is set to be paid via NewDot 👍 Payment Summary@allroundexperts — to be paid $250 via NewDot 👍 |
$250 approved for @allroundexperts |
Problem
When we have multiple tabs open on new dot, all of them receive pusher updates. That's causing confusion because we're trying to apply them all, so depending on the tab you are, you'll see that they were applied, or that we've skipped them because they were already applied (in another tab).
This is also a problem when you receive an update that you are not up to date. If that happens, we will trigger N calls to GetMissingOnyxMessages.
a. Tab A receives it first, so it applied the update
b. Tab B and Tab C will log Update received was older than or the same as current state, returning without applying the updates other than successData and failureData
a. All 3 tabs will receive that update
b. All 3 tabs will call saveUpdateInformation after checking that the previousUpdateID do not match
c. Because we execute the call for GetMissingOnyxUpdate on a callback of updates on the key ONYX_UPDATES_FROM_SERVER, and we updated that key 3 times on 3.b, each tab will call GetMissingOnyxUpdates 3 times (for a total of 9 calls to our servers)
We've solved issue 3.c on PR #39943, but we were still doing 3 requests (because we triggered the call back 3 times).
Solution
Only apply onyx updates from the main active client
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: