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
Faster room joins: avoid blocking when pulling events with missing prevs #13355
Merged
squahtx
merged 10 commits into
develop
from
squah/faster_room_joins_calculate_partial_state_flag_for_backfill
Jul 26, 2022
Merged
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
ad5d75e
Skip soft fail checks for rooms with partial state
ff8f6cf
Make the `partial_state` parameter to `compute_event_context` stricter
f7c9a5a
Add `partial_state` parameter to `_process_received_pdu`
bca5a17
Add `await_full_state` parameter to `get_state_groups_ids`, so that i…
1d48d23
Allow `_resolve_state_at_missing_prevs` to return partial state, othe…
6517210
Retry persisting events from federation when we lose the partial stat…
b879d8c
Add newsfile
7d55d88
Raise an error if we still have partial state on the 2nd try
7870d44
Add comment for update_state_for_partial_state_event optimisation
765614f
Update synapse/handlers/federation_event.py
squahtx 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
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.
as a random point for future reference: there is a convention that the subject line of a git commit message should be limited to 50 characters. That helps avoid this sort of thing:
There's an art to writing such a pithy summary, of course. In this case I would probably just say:
... and put "so that it can return partial state" in the body of the commit message.
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.
interesting, I wasn't aware that the subject line had a shorter recommended length.
Up until now I've been using a limit of 72 characters in merge commits (and ignoring it in commits that get squashed, like the one above). 50 characters certainly makes things tricky!
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.
Yeah, the problem comes when we're doing a commit-by-commit review: it's much nicer if there's a pithy summary for each commit. It's certainly not worth stressing overmuch over though.
Indeed. github actually seems to truncate at 66 chars, so that seems a more reasonable compromise.