-
-
Notifications
You must be signed in to change notification settings - Fork 87
The transaction_id within events is not serialised in many endpoints #3000
Copy link
Copy link
Open
Labels
O-FrequentAffects or can be seen by most users regularly or impacts most users' first experienceAffects or can be seen by most users regularly or impacts most users' first experienceT-DefectBugs, crashes, hangs, security vulnerabilities, or other reported issues.Bugs, crashes, hangs, security vulnerabilities, or other reported issues.good first issueGood for newcomersGood for newcomersspec-complianceFix something that doesn't comply with the specsFix something that doesn't comply with the specs
Metadata
Metadata
Assignees
Labels
O-FrequentAffects or can be seen by most users regularly or impacts most users' first experienceAffects or can be seen by most users regularly or impacts most users' first experienceT-DefectBugs, crashes, hangs, security vulnerabilities, or other reported issues.Bugs, crashes, hangs, security vulnerabilities, or other reported issues.good first issueGood for newcomersGood for newcomersspec-complianceFix something that doesn't comply with the specsFix something that doesn't comply with the specs
Type
Fields
Give feedbackNo fields configured for issues without a type.
This issue was originally created by @sandhose at matrix-org/dendrite#3000.
Similar to matrix-org/synapse#15173 in Synapse
There are many endpoints that return events, and in those representations they should include the
transaction_idin the unsigned part of the event.I wrote a Complement test to highlight that Synapse had this issue by testing using the
/rooms/{roomId}/event/{eventId}endpoint, and Dendrite also fails on this test. I haven't tested the other endpoints, nor covered them in the Complement test. matrix-org/complement#621