Skip to content

[DO NOT MERGE] feat: automatically recover from ConversationAlreadyExists caused by epoch-0 groups#2365

Draft
SimonThormeyer wants to merge 5 commits into
mainfrom
simon/feat/process-welcome
Draft

[DO NOT MERGE] feat: automatically recover from ConversationAlreadyExists caused by epoch-0 groups#2365
SimonThormeyer wants to merge 5 commits into
mainfrom
simon/feat/process-welcome

Conversation

@SimonThormeyer

@SimonThormeyer SimonThormeyer commented Jul 23, 2026

Copy link
Copy Markdown
Member

See above.

Don't merge, because we haven't decided yet that this is the path we'd like to go.

@SimonThormeyer
SimonThormeyer force-pushed the simon/feat/process-welcome branch from 1c6dd0e to 50512c8 Compare July 23, 2026 09:28

@coriolinus coriolinus left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I like this approach, thanks for writing it!

(Approval obviously also depends on fixing CI though.)

// If the conversation exists locally as a pending conversation or as a conversation with epoch 0, we can clear
// it and keep the one we just created, because this will lead to the desired state, compatible with what we had
// locally. A fresh group with this `id`, just not created by us.
// This resolves WPB-21116.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

It is not clear to me that this is the best solution for WPB-21116, in part because it is unclear how exactly the problem arises. So I would prefer to not proceed with this until we get more clarity on the original issue.

@SimonThormeyer SimonThormeyer changed the title Simon/feat/process welcome [DO NOT MERGE] feat: automatically recover from ConversationAlreadyExists caused by epoch-0-groups Jul 24, 2026
@SimonThormeyer SimonThormeyer changed the title [DO NOT MERGE] feat: automatically recover from ConversationAlreadyExists caused by epoch-0-groups [DO NOT MERGE] feat: automatically recover from ConversationAlreadyExists caused by epoch-0 groups Jul 24, 2026
@SimonThormeyer
SimonThormeyer force-pushed the simon/feat/process-welcome branch from 50512c8 to 137c3bb Compare July 24, 2026 11:33
…on<_>>`

Returning `None` is just more appropiate than returning a
`ConversationNotFound` error
We don't always want to return an error when a conversation with a given
id doesn't exist.
@SimonThormeyer
SimonThormeyer force-pushed the simon/feat/process-welcome branch from 137c3bb to 03552fa Compare July 24, 2026 15:01
@SimonThormeyer
SimonThormeyer force-pushed the simon/feat/process-welcome branch 2 times, most recently from 622108f to 89a1486 Compare July 24, 2026 15:25
@SimonThormeyer
SimonThormeyer force-pushed the simon/feat/process-welcome branch from 89a1486 to 7129cce Compare July 24, 2026 15:28
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