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

Msg entirely vanished by turning into the next sent msg #3206

Open
ara4n opened this issue Aug 27, 2024 · 2 comments
Open

Msg entirely vanished by turning into the next sent msg #3206

ara4n opened this issue Aug 27, 2024 · 2 comments
Labels
A-Timeline O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@ara4n
Copy link
Member

ara4n commented Aug 27, 2024

Steps to reproduce

  1. opened a room
  2. sent a msg
  3. sent another msg
  4. watch in confusion as the first msg beautifully animates into the second msg, as if it was an edit - about the point that the remote echo of the first msg should have been received
  5. double check that it was not an edit (it was not)
  6. double check that i am sober (i am)
  7. go back to roomlist
  8. go back to room
  9. now both msgs are visible.

screenshot of the missing msg:

IMG_8892

screenshot having reopened the room:

IMG_8893

rageshake has event & room ids

Outcome

What did you expect?

msgs not to disappear before my very eyes

What happened instead?

a beautiful dissolving animation as my msg vanished temporarily.

this is the second time i’ve seen this (previously on macos a few weeks back)

cc @bnjbvr as he’s looking at timeline and echo weirdness

Your phone model

No response

Operating system version

No response

Application version

690

Homeserver

No response

Will you send logs?

Yes

@ara4n ara4n added A-Timeline T-Defect O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround labels Aug 28, 2024
@bnjbvr
Copy link
Member

bnjbvr commented Aug 29, 2024

The "turning into the next sent msg" part is worrying, as it indicates a "unique id" for a timeline item is not so unique, and has been shared with another timeline item. I've identified one possible cause of that issue in matrix-org/matrix-rust-sdk#3916, but there might be other more subtle failure modes for this.

@bnjbvr
Copy link
Member

bnjbvr commented Aug 29, 2024

double check that i am sober (i am)

Need a blood sample to exclude auto-brewery syndrome hypothesis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Timeline O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Development

No branches or pull requests

2 participants