Skip to content

MSC4140: drop delayed state interference tests#845

Open
AndrewFerr wants to merge 1 commit intomatrix-org:mainfrom
AndrewFerr:msc4140-drop-state-cancel-rule
Open

MSC4140: drop delayed state interference tests#845
AndrewFerr wants to merge 1 commit intomatrix-org:mainfrom
AndrewFerr:msc4140-drop-state-cancel-rule

Conversation

@AndrewFerr
Copy link
Member

@AndrewFerr AndrewFerr commented Feb 24, 2026

Don't test that a user's delayed state events are cancelled by a more recent state event from a different user. That behaviour has been delegated to an "alternative" in the delayed event MSC4140 for some time now, and may be removed from Synapse.

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

Pull Request Checklist

Don't test that a user's delayed state events are cancelled by a more
recent state event from a different user.  That behaviour has been
delegated to an "alternative" in the delayed event MSC for some time
now, and may be removed from Synapse.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't test that a user's delayed state events are cancelled by a more recent state event from a different user. That behaviour has been delegated to an "alternative" in the delayed event MSC4140 for some time now [...]

Can you link the relevant discussion for reference?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and may be removed from Synapse.

Is this tracked somewhere? Probably best as an issue and link it from a FIXME comment within the code. It would be nice not to forget about when time comes to stabilize this feature.

})
})

t.Run("delayed state is not cancelled by new state from the same user", func(t *testing.T) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't test that a user's delayed state events are cancelled by a more recent state event from a different user.

This is for the same user. Should we actually remove it as well?

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