Skip to content

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

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

Conversation

AndrewFerr
Copy link
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 [email protected]

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
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
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.

2 participants