You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
richvdh opened this issue
May 29, 2018
· 0 comments
· Fixed by #12319
Labels
A-Syncdefects related to /syncS-MinorBlocks non-critical functionality, workarounds exist.T-DefectBugs, crashes, hangs, security vulnerabilities, or other reported issues.
however, get_state_at uses get_recent_events_for_room which returns the event with the greatest depth, so if somebody has been playing silly buggers with the depth, you may end up looking at a point in the graph where you were a member, even though at the point of the 'since' token you were not.
The text was updated successfully, but these errors were encountered:
Discovered after much in-depth investigation in #12281.
Closes: #12281Closes: #3305
Signed off by: Nick Mills-Barrett nick@beeper.com
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
A-Syncdefects related to /syncS-MinorBlocks non-critical functionality, workarounds exist.T-DefectBugs, crashes, hangs, security vulnerabilities, or other reported issues.
I rather hope this will get fixed when we make depth not be a thing, but:
synapse/synapse/handlers/sync.py
Line 1087 in 933bf2d
get_state_at
usesget_recent_events_for_room
which returns the event with the greatest depth, so if somebody has been playing silly buggers with the depth, you may end up looking at a point in the graph where you were a member, even though at the point of the 'since' token you were not.The text was updated successfully, but these errors were encountered: