Skip to content
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 #39432][$500] Report - Offline deleted message is not struck through #39307

Closed
2 of 6 tasks
lanitochka17 opened this issue Mar 29, 2024 · 25 comments
Closed
2 of 6 tasks
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. External Added to denote the issue can be worked on by a contributor Reviewing Has a PR in review Weekly KSv2

Comments

@lanitochka17
Copy link

lanitochka17 commented Mar 29, 2024

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:

  1. Navigate to any report
  2. Apply offline mode
  3. Delete a message

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?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6431930_1711737045335.Screen_Recording_2024-03-29_at_9.22.11_at_night.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0123d5e156c38fe58b
  • Upwork Job ID: 1775662468195880960
  • Last Price Increase: 2024-04-03
@lanitochka17 lanitochka17 added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Mar 29, 2024
Copy link

melvin-bot bot commented Mar 29, 2024

Triggered auto assignment to @strepanier03 (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

@lanitochka17
Copy link
Author

@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

@nkdengineer
Copy link
Contributor

nkdengineer commented Apr 1, 2024

Proposal

Please re-state the problem that we are trying to solve in this issue.

Message disappears

What is the root cause of that problem?

What changes do you think we should make in order to solve the problem?

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

handleConflictingRequest: () => Onyx.update(successData),

handleConflictingRequest?.(conflictingRequest);

What alternative solutions did you explore? (Optional)

We should handle merge the optimistic data of the request after we handle conflicting request

if (optimisticData) {
Onyx.update(optimisticData);
}

To do that we should move this block after we push the request here

@strepanier03
Copy link
Contributor

Raising this internally because I'm finding contradicting expected behavior.

#17081

@melvin-bot melvin-bot bot removed the Overdue label Apr 3, 2024
@strepanier03
Copy link
Contributor

Okay "greyed out and struck through" is the expected behavior.

@strepanier03 strepanier03 added the External Added to denote the issue can be worked on by a contributor label Apr 3, 2024
@melvin-bot melvin-bot bot changed the title Report - Offline deleted message is not struck through [$500] Report - Offline deleted message is not struck through Apr 3, 2024
Copy link

melvin-bot bot commented Apr 3, 2024

Job added to Upwork: https://www.upwork.com/jobs/~0123d5e156c38fe58b

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Apr 3, 2024
Copy link

melvin-bot bot commented Apr 3, 2024

Triggered auto assignment to Contributor-plus team member for initial proposal review - @hungvu193 (External)

@hungvu193
Copy link
Contributor

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?

Revert PR
Screen.Recording.2024-04-04.at.10.22.29.mov

@roryabraham
Copy link
Contributor

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.

@hungvu193
Copy link
Contributor

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.

Screen.Recording.2024-04-04.at.13.21.00.mov

@shubham1206agra
Copy link
Contributor

Hello @hungvu193

Can you please hold this issue on another similar issue?

Thanks

@hungvu193
Copy link
Contributor

Can you please link that similar issue here?

Hello @hungvu193

Can you please hold this issue on another similar issue?

Thanks

@shubham1206agra
Copy link
Contributor

#39432

@hungvu193
Copy link
Contributor

Awesome, @strepanier03 let's put this on hold for #39432

@hungvu193
Copy link
Contributor

hold for #39432

@melvin-bot melvin-bot bot removed the Overdue label Apr 8, 2024
@roryabraham roryabraham changed the title [$500] Report - Offline deleted message is not struck through [HOLD][$500] Report - Offline deleted message is not struck through Apr 8, 2024
@strepanier03
Copy link
Contributor

Still on hold, good to keep pausing.

@melvin-bot melvin-bot bot removed the Overdue label Apr 23, 2024
@melvin-bot melvin-bot bot added the Overdue label May 2, 2024
@roryabraham
Copy link
Contributor

Still on HOLD, will resume #39432 as soon as I can

@melvin-bot melvin-bot bot removed the Overdue label May 3, 2024
@melvin-bot melvin-bot bot added the Overdue label May 13, 2024
@strepanier03
Copy link
Contributor

Thanks Rory!

@melvin-bot melvin-bot bot removed the Overdue label May 14, 2024
@melvin-bot melvin-bot bot added the Overdue label May 23, 2024
@roryabraham
Copy link
Contributor

still on hold

@melvin-bot melvin-bot bot removed the Overdue label May 23, 2024
@melvin-bot melvin-bot bot added the Overdue label Jun 3, 2024
@strepanier03
Copy link
Contributor

Currently on hold.

@melvin-bot melvin-bot bot removed the Overdue label Jun 14, 2024
@melvin-bot melvin-bot bot added the Overdue label Jun 24, 2024
@strepanier03
Copy link
Contributor

VSB is on hold. Thinking of moving this to monthly.

@melvin-bot melvin-bot bot removed the Overdue label Jun 26, 2024
@melvin-bot melvin-bot bot added the Overdue label Jul 5, 2024
@strepanier03
Copy link
Contributor

Moving to monthly for now.

@melvin-bot melvin-bot bot removed the Overdue label Jul 17, 2024
@strepanier03 strepanier03 added Monthly KSv2 and removed Weekly KSv2 labels Jul 17, 2024
@melvin-bot melvin-bot bot added Overdue Reviewing Has a PR in review Weekly KSv2 and removed Overdue Monthly KSv2 labels Aug 19, 2024
@strepanier03
Copy link
Contributor

Going to retest this, it's been quite some time since it was created and tested.

@strepanier03
Copy link
Contributor

On v9.0.28-2, I am unable to repro. Going offline and deleting a message strikes the message through as expected.

image

I'm going to close this out as already fixed. Reopen if you disagree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. External Added to denote the issue can be worked on by a contributor Reviewing Has a PR in review Weekly KSv2
Projects
No open projects
Status: No status
Development

No branches or pull requests

6 participants