-
Notifications
You must be signed in to change notification settings - Fork 39
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
Ignore more stray timelines in Accumulate #255
Conversation
Described in #211 (comment). This is essentially cherry picked from #248, in particular the commit 8c7046e This should prevent creating new snapshots that don't reflect the state of the room. We'll need a followup task to clean up bad snapshots.
I will need to
|
Easier than I expected to get the tests happy. It looks like the test changes in #248 are fixups to ensuring that we never send a nonempty state block with an empty timeline. This PR targets empty state blocks and nonempty timelines, so I think that is irrelevant here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems sane.
These rooms have invalid state snapshots, leading to correctness problems. The existence of such snapshots leaves us open to performance problems due to gappy state updates. We have prevented invalid state snapshots from being formed (#255, #266) in the future. The remaining hole is to discard existing invalid snapshots. Closes #256.
Described in #211 (comment).
This is essentially cherry picked from #248, in particular the commit
8c7046e
This should prevent creating new snapshots that don't reflect the state of the room. We'll need a followup task to clean up bad snapshots.