-
-
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
First sync response for newly joined room is ignored if it is returned in the ongoing /sync request #15428
Comments
Added the HAR I recorded while reproducing this. The HAR contains a lot of noise, so I also created a summary with only the non-OPTIONS requests that contain the room name that manifested the problem in the response body. There you can clearly see that the sync response before the /join contains all the state events for the newly joined room, and the /sync that comes after is almost empty. Element web (app) showed the wrong room name ( First I thought this was a synapse bug, but this appears to be valid behaviour. |
I wonder if this is related to #8246 |
Thanks for the HAR @bwindels - tried to reproduce this in a unit test with no luck unfortunately
I also cannot reproduce this using the app, if anyone has seen this recently please comment here |
e.g. the sync request started prior to /join request. I can only reproduce the problem when joining
#dendrive-dev:matrix
(!yjVgJUsMLYLAONsoii:jki.re
).The text was updated successfully, but these errors were encountered: