Closed lanitochka17 closed 2 months ago
Triggered auto assignment to @strepanier03 (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details.
@strepanier03 FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
Message disappears
When we delete a message that isn't a thread parent message, the current request is included to handle conflicting request and then we merge the successData
into Onyx after we merge the optimistic data of the request here. That is the root cause of the issue
We should handle merge the optimistic data of the request after we handle conflicting request
To do that we should move this block after we push the request here
Raising this internally because I'm finding contradicting expected behavior.
Okay "greyed out and struck through" is the expected behavior.
Job added to Upwork: https://www.upwork.com/jobs/~0123d5e156c38fe58b
Triggered auto assignment to Contributor-plus team member for initial proposal review - @hungvu193 (External
)
Hey @roryabraham, I believe this issue is a regression from your recent PR, do you want to fix this as a separate issue or treat it as a regression?
I'd be happy to fix this in a follow-up, I don't think we should revert this, as the bug(s) I fixed were worse than this one.
Thanks, @nkdengineer. I'm not convinced by the solution of moving the updating optimisticData after SequentialQueue.push(request)
. Also, it didn't work when you turned off and then turned on your internet connection few times.
https://github.com/Expensify/App/assets/16502320/f8f72a92-377c-4a8d-b144-f1eebc797d19
Hello @hungvu193
Can you please hold this issue on another similar issue?
Thanks
Can you please link that similar issue here?
Hello @hungvu193
Can you please hold this issue on another similar issue?
Thanks
Awesome, @strepanier03 let's put this on hold for https://github.com/Expensify/App/issues/39432
HOLD, should be fixed in https://github.com/Expensify/App/issues/39432
Still on hold, good to keep pausing.
Still on HOLD, will resume https://github.com/Expensify/App/issues/39432 as soon as I can
Thanks Rory!
still on hold
Currently on hold.
VSB is on hold. Thinking of moving this to monthly.
Moving to monthly for now.
Going to retest this, it's been quite some time since it was created and tested.
On v9.0.28-2, I am unable to repro. Going offline and deleting a message strikes the message through as expected.
I'm going to close this out as already fixed. Reopen if you disagree.
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.58-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: https://expensify.testrail.io/index.php?/tests/view/4467827 Email or phone of affected tester (no customers): natnael.expensify+3@gmail.com Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
Message should be grayed out, and struck through
Actual Result:
Message disappears
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/78819774/878be84c-f887-4d93-9b10-6ee07461dd8a
View all open jobs on GitHub
Upwork Automation - Do Not Edit