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.

Sign up for GitHub

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

Jump to bottom

Server error caught in logs: M_INVALID_PARAM: MatrixError: [400] event_id $redacted01 is not related to thread $redacted02 #25424

Open
turt2live opened this issue May 23, 2023 · 0 comments
Open

Server error caught in logs: M_INVALID_PARAM: MatrixError: [400] event_id $redacted01 is not related to thread $redacted02 #25424

turt2live opened this issue May 23, 2023 · 0 comments
Labels
A-Threads 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

Comments

@turt2live
Copy link
Member

Steps to reproduce

  1. Have someone else send a message in a large encrypted room
  2. Having just started the app, send the first reply in the thread
  3. Open JS console while a new Megolm outbound session is established
  4. When the message does eventually send, note errors in console

Outcome

What did you expect?

  • No errors (this may be a race condition server-side)
  • No read receipts to be sent for my own events
  • Fewer than 7 http requests for this read receipt, particularly when it returns a 400 Bad Request http error

What happened instead?

The above. Details (should be) in the attached rageshake.

Operating system

Windows 11

Application version

Element Nightly version: 0.0.1-nightly.2023052201 Olm version: 3.2.14

How did you install the app?

The Internet

Homeserver

t2l.io

Will you send logs?

Yes
@andybalaam andybalaam added S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Occasional Affects or can be seen by some users regularly or most users rarely A-Threads labels May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Threads 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
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@andybalaam @turt2live