You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2024-03-13] [Fire Cleanup] Upgrade react-navigation to fix potential crashes #34523
We have asked Callstack to fix this bug, and they are working on it. This is just a tracking issue to make sure we upgrade E/App's react-navigation version after that bug is fixed.
Hey @dangrous sorry for the delay but I needed to resolve another issue which was on my plate. Ive been talking to Satya about this one and I will create PR this week which will be approved by him next week.
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.47-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve 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:
[@paultsimura] The PR that introduced the bug has been identified. Link to the PR:
[@paultsimura] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[@paultsimura] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[@paultsimura] Determine if we should create a regression test for this bug.
[@paultsimura] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[@miljakljajic] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
It's a cleanup dependency version bump, not fixing a specific bug.
The PR that introduced the bug has been identified. Link to the PR:
The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
Determine if we should create a regression test for this bug: No
Activity
MrRefactor commentedon Jan 15, 2024
Hi! Its Kuba from Callstack, I will be working on fixing this bug in react navigation.
dangrous commentedon Jan 16, 2024
Great! Let me know how I can help.
dangrous commentedon Jan 18, 2024
Officially assigned you @MrRefactor - let me know any updates as you figure things out!
MrRefactor commentedon Jan 18, 2024
Sure thing!
dangrous commentedon Jan 25, 2024
hey @MrRefactor figured I'd check in - how are things going?
MrRefactor commentedon Jan 26, 2024
Hey @dangrous Im still working on the fix in react-navigation repo
dangrous commentedon Feb 2, 2024
@MrRefactor Do you have a rough ETA for the solution? I know these things can be finicky so doesn't have to be exact. Thanks!
MrRefactor commentedon Feb 6, 2024
Hey @dangrous Im planning to create a PR end of this week or early next week!
dangrous commentedon Feb 6, 2024
Sounds great! Looking forward to it.
dangrous commentedon Feb 13, 2024
Hey @MrRefactor checking in - let me know if I can help/review/anything!
MrRefactor commentedon Feb 14, 2024
Hey @dangrous sorry for the delay but I needed to resolve another issue which was on my plate. Ive been talking to Satya about this one and I will create PR this week which will be approved by him next week.
MrRefactor commentedon Feb 15, 2024
Hey @dangrous PR is ready and will be check by Satya
31 remaining items
melvin-bot commentedon Mar 6, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.47-10 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-03-13. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Mar 6, 2024
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:
roryabraham commentedon Mar 13, 2024
@miljakljajic looks like this shuold be ready to pay out.
@paultsimura please complete the BZ checklist above
melvin-bot commentedon Mar 13, 2024
Payment Summary
Upwork Job
BugZero Checklist (@miljakljajic)
paultsimura commentedon Mar 14, 2024
It's a cleanup dependency version bump, not fixing a specific bug.
The PR that introduced the bug has been identified. Link to the PR:The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:paultsimura commentedon Mar 15, 2024
@roryabraham Milja is OOO for the last couple of days. Could we reassign BZ for payment, or better wait?
miljakljajic commentedon Mar 18, 2024
Paying now!
miljakljajic commentedon Mar 18, 2024
I'm not seeing an Upwork job for this one - is it a standard 500 USD payment?
roryabraham commentedon Mar 18, 2024
yep, standard $500 payout for the C+ review of react-navigation upgrade
miljakljajic commentedon Mar 18, 2024
Thank you! @paultsimura - contract sent :)