Skip to content
This repository has been archived by the owner on Sep 11, 2024. It is now read-only.

Perform a local rejection for failed invite rejections, #3167

Closed
wants to merge 3 commits into from

Conversation

t3chguy
Copy link
Member

@t3chguy t3chguy commented Jul 1, 2019

which synapse does not send its own local-rejection down sync

Fixes element-hq/element-web#3743
3743

Signed-off-by: Michael Telatynski [email protected]

which synapse does not send its own local-rejection down sync

Signed-off-by: Michael Telatynski <[email protected]>
@t3chguy
Copy link
Member Author

t3chguy commented Jul 1, 2019

Scrap that, further testing shows that refreshing just brings the room back because js-sdk processes the sync response once again

This fix has swiftly become quite messy :((

t3chguy added 2 commits July 1, 2019 08:20
Signed-off-by: Michael Telatynski <[email protected]>
@t3chguy
Copy link
Member Author

t3chguy commented Jul 1, 2019

I'm going to expand on this by implementing a method in the various js-sdk stores to "locallyRejectInvite" so that there's 0 chance of a race condition with nextBatch

@Ezwen
Copy link

Ezwen commented Oct 31, 2019

Any news on this? Thanks for looking into it :)

@t3chguy
Copy link
Member Author

t3chguy commented Oct 31, 2019

I wrote some code but it had a lot of edge cases where it would come back. I think implementing it more as an ignore invites from room X would be clearer in behaviour.

@Ezwen
Copy link

Ezwen commented Oct 31, 2019

ah I see, but then one would want to cancel ignores somehow I suppose?

@t3chguy
Copy link
Member Author

t3chguy commented Jul 12, 2020

Synapse fixed the stuck invite bug 🎉

@t3chguy t3chguy closed this Jul 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

client gets stuck with invites even after they get rejected
2 participants