-
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
[$250] Reports w/ 404 are stuck in LHN #45551
Comments
Triggered auto assignment to @strepanier03 ( |
@strepanier03 Huh... This is 4 days overdue. Who can take care of this? |
@strepanier03 Still overdue 6 days?! Let's take care of this! |
Working on this now, sorry for the delay. |
What timing, I have a chat that follows this pattern in my LHN right now that showed up this morning 😂. There's no way to dismiss it and it's stuck with a RBR in my LHN all day so far. |
Here's the Onyx Data for that chat:
|
Job added to Upwork: https://www.upwork.com/jobs/~016fe03af3d662fd8f |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ikevin127 ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.You see a Hmmm it's not here, but the report is stuck in your LHN with a red dot (RBR indicator), and can't be cleared. What is the root cause of that problem?After the user is removed from the room, the report data is still present in Onyx and it has a Lines 123 to 127 in b0f810d
And then here we always put this report in LHN if Lines 130 to 136 in b0f810d
So this report is always displayed in LHN What changes do you think we should make in order to solve the problem?We should check if the report has not found an error we will not push this report here.
Lines 130 to 136 in b0f810d
Then when we go to Lines 5531 to 5533 in b0f810d
Lines 5373 to 5375 in b0f810d
What alternative solutions did you explore? (Optional) |
@strepanier03 @nkdengineer I cannot reproduce the issue, I followed the steps and the result on my side is:
Note: The room was freshly created when I attempted reproducing. Here's a video of how it looks on my side: Web: Chrome / Safariweb.movTo me ^ this looks like the correct and expected behaviour, meaning: silently being removed, without any Not found page being shown or RBR errors. If anyone has clear / more detailed steps as to how this can be consistently reproduced, please let me know so we can move forward with a fix. Otherwise, I'd add the cc @roryabraham (since you reported this) |
@strepanier03 are you still able to reproduce this? |
@strepanier03, @ikevin127 Whoops! This issue is 2 days overdue. Let's get this updated quick! |
|
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@strepanier03 @ikevin127 this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
|
@strepanier03, @ikevin127 Whoops! This issue is 2 days overdue. Let's get this updated quick! |
|
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Issue not reproducible during KI retests. (First week) |
@strepanier03, @ikevin127 Huh... This is 4 days overdue. Who can take care of this? |
Looks like issue is not reproducible anymore (reference). |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Issue not reproducible during KI retests. (Second week) |
@strepanier03, @ikevin127 Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@strepanier03, @ikevin127 Whoops! This issue is 2 days overdue. Let's get this updated quick! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Looks like issue is not reproducible anymore (reference, 2nd week test reference). @strepanier03 Maybe we can close this, wdyt ? |
@strepanier03, @ikevin127 Huh... This is 4 days overdue. Who can take care of this? |
Looks like issue is not reproducible anymore (reference, 2nd week test reference). @strepanier03 Maybe we can close this, wdyt ? |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
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: 9.0.8-0
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: @roryabraham
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1721060374459769
Action Performed:
Expected Result:
You should see a
Hmmm it's not here
(404 error), then when you navigate away the report should disappear from the LHN.Actual Result:
You see a
Hmmm it's not here
, but the report is stuck in your LHN with a red dot (RBR indicator), and can't be cleared.Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Recording.337.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @ikevin127The text was updated successfully, but these errors were encountered: