This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Use StateResolutionHandler to resolve state in persist_events #2864
Merged
Merged
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
447aed4
Add event_map param to resolve_state_groups
richvdh 9fcbbe8
Check that events being persisted have state_group
richvdh 225dc3b
Flatten _get_new_state_after_events
richvdh ebfe64e
Use StateResolutionHandler to resolve state in persist events
richvdh 630caf8
style nit
richvdh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -515,16 +515,21 @@ def _get_new_state_after_events(self, events_context, new_latest_event_ids): | |
if ctx.current_state_ids is None: | ||
raise Exception("Unknown current state") | ||
|
||
if ctx.state_group is None: | ||
# I don't think this can happen, but let's double-check | ||
raise Exception( | ||
"Context for new extremity event %s has no state " | ||
"group" % event_id, | ||
) | ||
|
||
# If we've already seen the state group don't bother adding | ||
# it to the state sets again | ||
if ctx.state_group not in state_groups: | ||
state_sets.append(ctx.current_state_ids) | ||
if ctx.delta_ids or hasattr(ev, "state_key"): | ||
was_updated = True | ||
if ctx.state_group: | ||
# Add this as a seen state group (if it has a state | ||
# group) | ||
state_groups.add(ctx.state_group) | ||
# Add this as a seen state group | ||
state_groups.add(ctx.state_group) | ||
break | ||
else: | ||
# If we couldn't find it, then we'll need to pull | ||
|
@@ -586,6 +591,7 @@ def get_events(ev_ids): | |
|
||
current_state = yield resolve_events_with_factory( | ||
state_sets, | ||
event_map={}, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should this be None to be a bit more consistent? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. plausibly, but it's replaced in ebfe64e anyway There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yup, didn't realise until after i had submitted the review |
||
state_map_factory=get_events, | ||
) | ||
defer.returnValue(current_state) | ||
|
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.
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.
Nit: I do prefer always using tuples rather than relying on strings working.
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.
as in you'd prefer
(event_id, )
?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.
Generally yes, (or
(event_id,)
without the space), as its very confusing if there is a bug andevent_id
suddenly becomes iterable and then the logging explodes. In this particular case its probably fine thoughThere 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.
fair