This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Wait for lazy join to complete when getting current state #12872
Wait for lazy join to complete when getting current state #12872
Changes from 13 commits
78faa1a
334844d
fe86915
a2465b8
a2945a5
e786f68
3f74b37
c068581
6f386d1
2b674f8
ecae768
d1a1d6a
531955f
6cc7269
3a20548
6e7625e
711ea44
1f99ce0
b59418f
c6fe132
4757b00
b6cb65f
c513c20
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This is a check to see if the state event we're about to send down to clients is in the current state, and if so to always send it even if
filter_events_for_client
would filter it out. Not sure if usingget_partial_current_state_ids
is the right approach 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.
I'm not really following, but this is something we can return to.
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.
I think this means a rolling restart is unwise. We should either document it, or arrange for it to be safe.
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.
I think this is fine, as we're actually not streaming the name of the caches over replication for these, we're just sending "invalidate all current state caches kthx" instead. (
_attempt_to_invalidate_cache
only invalidates things on the local process)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.
ah. yes.
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.
I think this means a rolling restart is unwise. We should either document it, or arrange for it to be safe.