-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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 2022-03-17] Feature Request: Data is getting written to Onyx after logout - reported by @kidroca #7434
Comments
Triggered auto assignment to @Christinadobrzyn ( |
Triggered auto assignment to @alex-mechler ( |
Tagging a couple people who were involved in the discussions around this and sending it external |
Triggered auto assignment to @dylanexpensify ( |
Yeah, this is happening. |
Working on getting posted! |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane ( |
Triggered auto assignment to @tgolen ( |
Excited to review proposals on this one! |
A solution could be:
Method 2
Pseudocode .then(response => blockinFlightRequests? undefined: onResponse(queuedRequest, response))
.catch((error) => {
if(blockinFlightRequests) {
return;
}
// When the request did not reach its destination add it back the queue to be retried
const shouldRetry = lodashGet(queuedRequest, 'data.shouldRetry');
if (shouldRetry) {
networkRequestQueue.push(queuedRequest);
return;
}
onError(queuedRequest, error);
}); But it imposes a challenge for us When should we set the blockinFlightRequests flag back to |
Not overdue |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.1.41-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 2022-03-17. 🎊 |
Triggered auto assignment to @trjExpensify ( |
Reassigning as I'm OOO next week! Thanks Tom for handling the payment if no regressions! 🙇 |
@kidroca - paid. @rushatgabhane waiting for you to accept the offer for C+. |
@trjExpensify accepted, thanks! |
Cool, settled! |
@trjExpensify |
You thought correctly! Sorry about that, I just settled the contract that was in place. So I sent you a bonus for an additional $250. Got an error message in Upwork saying there was a problem with the account. Did it again and now it looks like I've paid you an extra $250. Can you double check that? 😅 |
Just checked, indeed I've been paid twice for reporting |
Perfect, just got the email for the refund. Going to close this one out again, thanks! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
We can abort requests to save bandwidth and prevent other issues
Actual Result:
Some times we know there are requests bound to fail or requests for whom we're no longer interested in the results.
Workaround:
unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.31-0
Reproducible in staging?:
Reproducible in production?:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
New.Expensify.-.Google.Chrome.2022-01-25.21-05-00.mp4
Upwork URL: https://www.upwork.com/jobs/~01bcb9c814f48af12c
Issue reported by: @kidroca
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1642188186471800
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: