Huge amounts of log spam around hasUserReadEvent event ID X not found in room Y: this shouldn't happen!

[ara4n]

Steps to reproduce

1. View an encrypted room with threads (with the thread panel open?)
2. Look at the console

See pages and pages of logs like:

11:39:41.137 rageshake.ts:77 Decrypted event $mgSvnesm4EKj1SIO_6oAt7JorfYVSHzuo2_EUOchSnU is not in room !UcgyhoigetVICUfvRw:matrix.org: ignoring
11:39:41.137 rageshake.ts:77 hasUserReadEvent event ID $u32VyNTT-LxPaGtx1PKU2Z4wgm2h2m-4RGr48T7Gu6w not found in room !UcgyhoigetVICUfvRw:matrix.org: this shouldn't happen!
11:39:41.339 rageshake.ts:77 Decrypted event $w3iMHLpemaWfSQseAe4SOF0pCrQ2_QzZvalosUFpGlw is not in room !UcgyhoigetVICUfvRw:matrix.org: ignoring
11:39:41.340 rageshake.ts:77 hasUserReadEvent event ID $u32VyNTT-LxPaGtx1PKU2Z4wgm2h2m-4RGr48T7Gu6w not found in room !UcgyhoigetVICUfvRw:matrix.org: this shouldn't happen!
11:39:41.342 rageshake.ts:77 Decrypted event $xHFlYbehYSQUJNtY1qsuIrQSmi0H56dxFCESQOZAPg0 is not in room !UcgyhoigetVICUfvRw:matrix.org: ignoring
11:39:41.342 rageshake.ts:77 hasUserReadEvent event ID $u32VyNTT-LxPaGtx1PKU2Z4wgm2h2m-4RGr48T7Gu6w not found in room !UcgyhoigetVICUfvRw:matrix.org: this shouldn't happen!
11:39:41.344 rageshake.ts:77 Decrypted event $kzX3HLmxOb7M0kj1nCtL-JspsEoUq9VvlzeSyjXCu2E is not in room !UcgyhoigetVICUfvRw:matrix.org: ignoring
11:39:41.344 rageshake.ts:77 hasUserReadEvent event ID $u32VyNTT-LxPaGtx1PKU2Z4wgm2h2m-4RGr48T7Gu6w not found in room !UcgyhoigetVICUfvRw:matrix.org: this shouldn't happen!
11:39:41.345 rageshake.ts:77 Decrypted event $Eq0ShRmDC6b8cf97oMj1dQjT8IbyIvZK2BsYCvfpysc is not in room !UcgyhoigetVICUfvRw:matrix.org: ignoring
11:39:41.345 rageshake.ts:77 hasUserReadEvent event ID $u32VyNTT-LxPaGtx1PKU2Z4wgm2h2m-4RGr48T7Gu6w not found in room !UcgyhoigetVICUfvRw:matrix.org: this shouldn't happen!
11:39:41.489 rageshake.ts:77 Decrypted event $Ouv3fLoDaoAdo9kUmw_5rUnwRHu8t63NpRHxDYOOy3k is not in room !UcgyhoigetVICUfvRw:matrix.org: ignoring

3. assume that this is stuck notif logging - but is it actually useful, given how amazingly spammy it is?

Outcome

What did you expect?

If these log lines shouldn't happen, then whatever is causing them should be fixed, surely.

If they /should/ happen, perhaps they can be moved down a log level?

What happened instead?

Logs full of spam making it hard to see what's going wrong.

Operating system

No response

Application version

nightly

How did you install the app?

No response

Homeserver

No response

Will you send logs?

Yes

[viceice]

Seeing this too. they seem to come from unread threads, which should be all already marked as read.

Invoking mark room as read is causing this warnings too.

Version von Element: 1.11.56-rc.0
Krypto-Version: Olm 3.2.15