-
Notifications
You must be signed in to change notification settings - Fork 2.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
[HOLD for payment 2023-10-10] [$500] Stop storing queued Onyx updates to disk #25612
Comments
Just blocked on testing on all platforms. Will try to get this done today. |
@marcaaron Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Focusing on pagination research atm. I will try to run through test steps for this one today. |
Job added to Upwork: https://www.upwork.com/jobs/~01451356cead02359a |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @situchan ( |
Triggered auto assignment to @alexpensify ( |
This comment was marked as resolved.
This comment was marked as resolved.
Hey @alexpensify this is something I am fixing and enlisting the C+ to help with on reviews. There was no bug report or anything as it's more of an improvement, so I checked off everything on the BZ checklist. |
@marcaaron - when is the payment date for this one? |
It looks like the PR is moving along but there is a lint error to address. |
@marcaaron can you review the lint error flag? Thanks! |
Yep sorry this one slipped through the cracks - thanks for the bump @alexpensify |
Merged and waiting for deploy |
Current assignee @situchan is eligible for the External assigner, not assigning anyone new. |
@situchan - it looks like automation might not kick in, so please apply here: |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.76-6 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 2023-10-10. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External 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:
|
@situchan looks like the previous Upwork link was not working, so can you apply to this one --- https://www.upwork.com/jobs/~01a80b6b1d1c2a3260 Thanks! |
Applied thanks |
Here is the payment summary:
Upwork Job: https://www.upwork.com/jobs/~01a80b6b1d1c2a3260 *If applicable, the bonuses will be applied on the final payment Extra Notes regarding payment: Confirmed here that there is no need to complete the BZ -- #25612 (comment) |
@situchan - I've extended the contract in Upwork, please accept and I can complete he payment process. Thanks! |
The payment has been sent out. All set here, so closing for now. |
Problem
In some cases, the payload of
OpenApp
is very large and since we save all Onyx responses to disk inqueuedOnyxUpdates
this leads to double-storing our largest resource. It will be deleted after, but doesn't seem like there is a clear reason why these updates should be persisted instead of just hanging around in memory.Solution
Let's store the "queued updates" in memory instead.
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: