Skip to content
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

conversations: don't update xconvmodseq on replicas #4851

Merged
merged 2 commits into from
Mar 19, 2024

Conversation

brong
Copy link
Member

@brong brong commented Mar 18, 2024

It will be synced anyway; we sync_log the affected mailboxes; and this stops it being accidentally bumped by the replica if the message changes are synced out of order.

It will be synced anyway; we sync_log the affected mailboxes;
and this stops it being accidentally bumped by the replica if the
message changes are synced out of order.
@ksmurchison
Copy link
Contributor

@brong this CI failure looks like nonsense, but can we force it to run again?

Copy link
Contributor

@ksmurchison ksmurchison left a comment

Choose a reason for hiding this comment

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

Other than the CI failure this LGTM. Just a simple plumbing the silent flag through.

We should probably understand the CI failure before merging.

@rsto
Copy link
Member

rsto commented Mar 18, 2024

The build was failing because the unit tests calling conversation_update were broken, now that the function signature changed. I pushed a fix for that and it now tests cleanly.

@brong brong merged commit be968c3 into master Mar 19, 2024
2 checks passed
@brong brong deleted the xconvmodseq-noreplica branch March 19, 2024 05:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants