Repository navigation
[HOLD for payment 2024-07-17] report.errorFields.notFound is being cleared incorrectly #43357
Description
Activity
Triggered auto assignment to @puneetlath (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.errorFields.notFoundgets set byOpenReportwhen the report doesn't exist or you don't have access to it. It gets cleared on success here but we should also clear it when the report gets shared to the user and we push it with an Onyx update. We can do that by updating Report::structureReportForOnyx. Once that's done we can remove this side effect.Reacted by Puneet LathMakes sense @arosiclair. Will you raise a PR?
Yup this is just low priority for me atm. I'll get to it soon
PR's are ready just have to wait for the Auth PR to be deployed before posting the App PR. ETA is end of next week.
Is there any App aspect to this? Or it's al back-end?
28 remaining items
@shubham1206agra friendly reminder about the checklist so we can pay tomorrow.
Payment Summary
- ROLE: @shubham1206agra paid $(AMOUNT) via Upwork (LINK)
BugZero Checklist (@puneetlath)
- I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
- I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
- I have paid out the Upwork contracts or cancelled the ones that are incorrect
- I have verified the payment summary above is correct
@puneetlath, @arosiclair, @shubham1206agra Eep! 4 days overdue now. Issues have feelings too...
@shubham1206agra bump on the checklist.
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:
- [@shubham1206agra] The PR that introduced the bug has been identified. Link to the PR: Add possibility to leave from workspaces and workspace expense chats #35671
- [@shubham1206agra] 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: Add possibility to leave from workspaces and workspace expense chats #35671 (comment)
- [@shubham1206agra] 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: NA
- [@shubham1206agra] Determine if we should create a regression test for this bug. Yes
- [@shubham1206agra] 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.
- [User A] Log in as workspace admin
- [User A] Create a room
- [User A] Copy the URL and send it to user B.
- [User B] As a non-workspace member, go to the URL
- [User B] Verify a Not Found screen displays
- [User A] As the admin, invite the user to the room
- [User B] Verify the Not Found screen is removed and the non-member can see the room
- [@puneetlath] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
@shubham1206agra I sent you an offer: https://www.upwork.com/nx/wm/offer/103254802
Please ping me here when you've accepted.
Regression test update: https://github.com/Expensify/Expensify/issues/415177
@puneetlath Accepted
Paid, thanks!
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
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: Latest
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): N/A
Logs: N/A
Expensify/Expensify Issue URL: N/A
Issue reported by: @arosiclair
Slack conversation: #35671 (comment)
Action Performed:
Expected Result:
The not found error is cleared by an update from the backend
Actual Result:
We're clearing the error using a side effect in ReportScreen here.
Workaround:
N/A
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
N/A
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @puneetlath