This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Unused legacy fallback code for public_key
response to /_matrix/identity/v2/store-invite
#6036
Labels
A-Spec-Compliance
places where synapse does not conform to the spec
O-Uncommon
Most users are unlikely to come across this or unexpected workflow
S-Tolerable
Minor significance, cosmetic issues, low or no impact to users.
T-Task
Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.
Z-Cleanup
Things we want to get rid of, but aren't actively causing pain
Noticed by @richvdh during review of https://github.com/matrix-org/synapse/pull/5979/files#r323956886
synapse/synapse/handlers/room_member.py
Lines 1037 to 1047 in c755955
synapse/synapse/handlers/room_member.py
Lines 873 to 876 in c755955
Original comment:
while I'm here (it's not really relevant to the review, but): wtf is going on here?
public_key
isn't specced anywhere, afaictpublic_key
isn't set, we setfallback_public_key
topublic_keys[0]
which, according to the spec, has a completely different shape to what we claim to return. (Edit: fixed by Corrections to the response format of/_matrix/identity/v2/store-invite
matrix-spec#1486)The calling code seems to imply that
fallback_public_key
is only used to populate some fields "For backwards compatibility", but said fields are in the spec.I'm not suggesting changing anything here as part of this PR, but it looks like there's some bogosity, which suggests to me that the code is either unused (so can be killed) or broken (so should be fixed).
The text was updated successfully, but these errors were encountered: