-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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-05-08] HIGH: [API Reliability] [$500] Multiple calls to GetNewerActions
on report open
#39674
Comments
Triggered auto assignment to @twisterdotcom ( |
GetNewerActions
on report openGetNewerActions
on report open
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
39674.mp4 |
I still can't reproduce this. Nobody else has reported it recently. |
39674-2.mp4So, an example of a single report loading When I load it, there are two First:
Second:
Maybe this is normal, maybe not? |
GetNewerActions
on report openGetNewerActions
on report open
Job added to Upwork: https://www.upwork.com/jobs/~01d7ea3b088204e3df |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.HIGH: [Needs Reproduction] [Reliability] Multiple calls to GetNewerActions on report open What is the root cause of that problem?There is two different bugs.
What changes do you think we should make in order to solve the problem?
Add below
What alternative solutions did you explore? (Optional)Add below props to Flatlist .
|
GetNewerActions
on report openGetNewerActions
on report open
@shahinyan11 Thanks for the proposal. Your RCA is not complete. Can you explain why is the PS: I think that's a different bug than what's reported, I'm suspecting |
ProposalUpdated. Added solution for two bugs. |
@shahinyan11 Thanks for the update. The root cause is still not correct. The call sequence is as follow: App/src/pages/home/report/ReportActionsView.tsx Lines 193 to 197 in b59ae94
Thus not checking for |
@s77rt In our case the |
@s77rt @roryabraham Here's the PR for the patch #41189 |
@s77rt @janicduplessis - are we getting @shahinyan11 to do anything here? If not, I'm kind of willing to pay out $250 regardless for their help here. |
Looks like the RN patch also fixed the RNW bug 🎉 |
I think we are good for this issue. Yes please pay out @shahinyan11 also for his help and work on this. |
@janicduplessis @janicduplessis Thank you for appreciating my work |
Payment Summary (to be paid after 7 days):
|
GetNewerActions
on report openGetNewerActions
on report open
GetNewerActions
on report openGetNewerActions
on report open
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.68-3 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-05-08. 🎊 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:
|
GetNewerActions
on report openGetNewerActions
on report open
Payment Summary
BugZero Checklist (@twisterdotcom)
|
Can we close this? i think the next steps will be handled in #41153 |
@francoisl, @twisterdotcom, @s77rt Huh... This is 4 days overdue. Who can take care of this? |
@twisterdotcom did you get a chance to issue the payments you had summarized in this comment? |
This is paid already |
Yes, we can close. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.4.60-7
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @quinthar
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1712180926567259
Action Performed:
Expected Result:
Shouldn't call
GetNewerActions
multiple timesActual Result:
GetNewerActions
called 5times, despite not scrolling anywhere. Also, all 5 calls seem identicalWorkaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @twisterdotcomThe text was updated successfully, but these errors were encountered: