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

Clients can crash in various ways if comment is deleted that an inbox notification still references #1621

Open
nvie opened this issue May 21, 2024 · 0 comments
Labels
bug Something isn't working triage needed The issue needs to be reviewed by the team

Comments

@nvie
Copy link
Collaborator

nvie commented May 21, 2024

Describe the bug

When you're displaying a list of inbox notifications and another user deletes the comment that is associated to that notification, the client can crash. Depending on exact setup and timing, this can fail in three ways:

Here are recordings of the three ways I could trigger an error and make one of the clients crash. These are three different stack traces:

First error (triggered manually)

bug1.mp4

Second error (triggered manually)

Screen.Shot.2024-05-21.at.13.46.23.mp4

Third error (triggered by CI)

Screen.Shot.2024-05-21.at.13.59.29.mp4

To Reproduce

I've replicated these bugs in our E2E test app. To manually reproduce it (for the first two errors):

  • Go to e2e/next-sandbox, run turbo run dev
  • Open http:https://localhost:3007/
  • Open "Inbox notifications (user 12)"
  • Open "Inbox notifications (user 7)" in another tab
  • Do what I did in the screen recordings

For the third error, make this one-line change, and simply run the test suite to see it happen.

Expected behavior

The clients should never crash, no matter how the app is used.

@nvie nvie added bug Something isn't working triage needed The issue needs to be reviewed by the team labels May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage needed The issue needs to be reviewed by the team
Projects
None yet
Development

No branches or pull requests

1 participant