Skip to content

MSC4140: don't cancel delayed state on own state#742

Closed
AndrewFerr wants to merge 1 commit intomatrix-org:mainfrom
AndrewFerr:msc4140_keep-own-conflicting-delayed-state
Closed

MSC4140: don't cancel delayed state on own state#742
AndrewFerr wants to merge 1 commit intomatrix-org:mainfrom
AndrewFerr:msc4140_keep-own-conflicting-delayed-state

Conversation

@AndrewFerr
Copy link
Copy Markdown
Member

When a user sends a state event, do not cancel their own delayed events for the same piece of state.

For context, see the relevant section in the MSC.

Signed-off-by: Andrew Ferrazzutti andrewf@element.io

Pull Request Checklist

When a user sends a state event, do not cancel their own delayed events
for the same piece of state.
@anoadragon453
Copy link
Copy Markdown
Member

Will merge once element-hq/synapse#17810 is ready to be merged. Otherwise CI will start to fail on Synapse's develop.

@AndrewFerr
Copy link
Copy Markdown
Member Author

Will replace this with a new PR whose branch name matches that of element-hq/synapse#17810, so that it will be used in CI complement tests appropriately.

@AndrewFerr AndrewFerr closed this Mar 7, 2025
@AndrewFerr AndrewFerr deleted the msc4140_keep-own-conflicting-delayed-state branch April 2, 2025 17:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants