-
Notifications
You must be signed in to change notification settings - Fork 276
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
MSC4140: don't cancel delayed state on own state #17810
MSC4140: don't cancel delayed state on own state #17810
Conversation
Depends on matrix-org/complement#742 for Complement tests to pass. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good on the whole, just some small points of feedback.
The sytests pass when I run them locally. Is there a way to retry their CI runs? |
@AndrewFerr Retried 👍 |
When a user sends a state event, do not cancel their own delayed events for the same piece of state.
d45595c
to
4ecbe62
Compare
Now the only failing tests are the ones that depend on matrix-org/complement#742 (finally!). |
@AndrewFerr what's the latest on this PR and addressing any outstanding issues? |
This and matrix-org/complement#742 are both ready to be merged (though the latter should be merged first). EDIT: I'll open a new Complement PR with its branch name set such that it will be used in this PR's Complement tests in CI. |
Eugh, looks like I had the wrong understanding of how CI chooses which Complement branch to run on. In any case, I can assure you that |
Removes workaround for element-hq/synapse#17810 not having landed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM, thanks for your patience 🙏
Will merge this PR at the same time as matrix-org/complement#768.
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.
Pull Request Checklist
EventStore
toEventWorkerStore
.".code blocks
.(run the linters)