Skip to content

Fix up the topological ordering for events above MAX_DEPTH #18447

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

Merged
merged 3 commits into from
May 19, 2025

Conversation

erikjohnston
Copy link
Member

Synapse previously did not correctly cap the max depth of an event to the max canonical json int. This can cause ordering issues for any events that were sent locally at the time.

This background update goes and correctly caps the topological ordering to the new MAX_DEPTH.

c.f. GHSA-v56r-hwv5-mxg6

Synapse previously did not correctly cap the max depth of an event to
the max canonical json int. This can cause ordering issues for any
events that were sent locally at the time.

This background update goes and correctly caps the topological ordering
to the new `MAX_DEPTH`.

c.f. GHSA-v56r-hwv5-mxg6
@erikjohnston erikjohnston force-pushed the erikj/rewrite_depth branch from 4e5f25d to 30772c7 Compare May 19, 2025 09:50
@erikjohnston erikjohnston marked this pull request as ready for review May 19, 2025 10:25
@erikjohnston erikjohnston requested a review from a team as a code owner May 19, 2025 10:25
Copy link
Member

@anoadragon453 anoadragon453 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some nits, otherwise LGTM. Thanks for taking this!

@erikjohnston erikjohnston merged commit 67920c0 into release-v1.130 May 19, 2025
39 checks passed
@erikjohnston erikjohnston deleted the erikj/rewrite_depth branch May 19, 2025 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants