-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Errors in console likely linked to stuck unreads #25642
Comments
I believe this has been fixed |
I do still get this message in my console, lots of times. Not sure whether that is expected? |
@andybalaam definitely not expected. Please send logs as well as corresponding context from devtools > Notifications debug |
Logs in https://github.com/matrix-org/element-web-rageshakes/issues/22359 show lots of "Ignoring event" messages. This was from a restart of the app. I don't see any stuck unreads as far as I know. |
^ That room contains no threads. It's a DM. |
Here is an anonymised timeline from that room: |
I thought you meant errors like The other ones are fine, they just mean we're not adding a reaction/relation to the timeline but still applying it in aggregate. |
Steps to reproduce
Outcome
What did you expect?
Receipts to be sent without errors
What happened instead?
This error when some receipts are sent:
I've lost the response error message, but it was a 400 that said that the message was not in that thread.
I also see some messages like this in some rooms:
Rageshake (reported for a different issue): https://github.com/matrix-org/element-web-rageshakes/issues/21938
Operating system
No response
Browser information
No response
URL for webapp
No response
Application version
No response
Homeserver
No response
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: