Fix null prev_events and auth_events fields from being sent to homeservers #46
Conversation
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
…rvers When performing a send_join request, Synapse was receiving 'null' entries for prev_events and auth_events inside of events. Instead, it should've received empty arrays. Synapse choked on this, leading to the need to track down the bug.
kegsay
approved these changes
Dec 4, 2020
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When performing a
/send_joinrequest, Complement was responding with 'null' entries forprev_eventsandauth_eventsinside of the state events. Instead ofnull, these should've been empty arrays. It came down to nil slices being inserted into interfaces andjson.Marshalturning those intonullvalues instead. Synapse choked on this, leading to the need to track down the bug.Thanks to @kegsay who tracked down the causes so quickly!