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

Can't load this message (m.room.message) on switching rooms #22281

Closed
DMRobertson opened this issue May 19, 2022 · 7 comments
Closed

Can't load this message (m.room.message) on switching rooms #22281

DMRobertson opened this issue May 19, 2022 · 7 comments
Labels
A-Timeline O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Cannot-Reproduce Z-Rageshake Has attached rageshake (not for log submission process) Z-Soft-Crash React soft crash caught by an error boundary

Comments

@DMRobertson
Copy link

Steps to reproduce

I navigated from one room to another. (Internal to Element-the-organisation.)

Outcome

What did you expect?

Messages timeline to load without an error.

What happened instead?

I saw some of the room's timeline, but at the bottom:

image

This persisted even as newer messages arrived.

Operating system

Fedora 36

Application version

Element version: 1.10.12 Olm version: 3.2.8

How did you install the app?

https://flathub.org/apps/details/im.riot.Riot

Homeserver

matrix.org

Will you send logs?

Yes

@andybalaam andybalaam added S-Minor Impairs non-critical functionality or suitable workarounds exist O-Occasional Affects or can be seen by some users regularly or most users rarely labels May 19, 2022
@andybalaam
Copy link
Member

I saw one of these today as well.

@andybalaam andybalaam added S-Major Severely degrades major functionality or product features, with no satisfactory workaround and removed S-Minor Impairs non-critical functionality or suitable workarounds exist labels May 19, 2022
@DMRobertson
Copy link
Author

Perhaps a duplicate of #22141?

@t3chguy
Copy link
Member

t3chguy commented May 19, 2022

2022-05-19T13:09:14.830Z E Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node. (NotFoundError | 8) doesn't look like it, but the logs don't really contain anything helpful

@t3chguy t3chguy added A-Timeline Z-Rageshake Has attached rageshake (not for log submission process) Z-Soft-Crash React soft crash caught by an error boundary labels May 19, 2022
@turt2live
Copy link
Member

this is also concerning:

2022-05-19T13:09:23.373Z W Event type not supported: type:m.room.encrypted isState:false

The removeChild could be a false-positive, but is also not fun to see in the logs.

Did it eventually fix itself eventually? From the logs it looks like the keys might have been missing at the time, so the event could have gone through the render pipeline as an unexpected event type.

@DMRobertson
Copy link
Author

Did it eventually fix itself eventually?

I think so. I scrolled back in that room and didn't see the error message. Double checking just now I can't see it either.

@turt2live
Copy link
Member

I'm even more inclined to blame this on a temporary decryption fail then. Unclear what would have caused that specifically.

@turt2live
Copy link
Member

Presuming fixed or otherwise not an issue. If this happens again, please open a new issue with new information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Timeline O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Cannot-Reproduce Z-Rageshake Has attached rageshake (not for log submission process) Z-Soft-Crash React soft crash caught by an error boundary
Projects
None yet
Development

No branches or pull requests

4 participants