Skip to content

Conversation

jianminzhao
Copy link
Contributor

@jianminzhao jianminzhao commented Oct 15, 2025

…in merge rev

We don't need add semicolon in VersionVectorWithRegacy::write() because the VersionVector::write already added the semicolon, except when currentVersions() == 1

…in merge rev

We don't add semicolon in VersionVectorWithRegacy::write() because the VersionVector::write already added the semicolon. The exception is when the VV contains only one CV. In this case, the ASCII output of the vv does not have the ending semicolon.
@cbl-bot
Copy link

cbl-bot commented Oct 16, 2025

Code Coverage Results:

Type Percentage
branches 65.87
functions 78.18
instantiations 71.7
lines 77.27
regions 73.6

@jianminzhao jianminzhao requested review from pasin and snej October 16, 2025 06:27
@jianminzhao jianminzhao merged commit 7c82fbf into master Oct 16, 2025
8 checks passed
@jianminzhao jianminzhao deleted the cbl-7551 branch October 16, 2025 18:07
jianminzhao added a commit that referenced this pull request Oct 16, 2025
CBL-7499: Invalid binary version ID when saving a resolved conflict doc that has legacy RevID
CBL-7500: Pull lower remote legacy rev but with same generation was not resulted in conflict
CBL-7401: Port Version Vector Conflict Detection Tests from Sync Gateway Tests (#2364)
CBL-7402: Port Version Vector Local Wins /Remote Wins Conflict Resolution Tests from Sync Gateway Tests
CBL-7403: Port Version Vector Merge Conflict Resolution Tests from Sync Gateway Tests
CBL-7551: Rev message contains two ;; in the history for the client-win merge rev (#2366)
CBL-7547: Client-win resolved doc as rev-tree encoded version cannot be pushed back (#2365)
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.

4 participants