Skip to content

[TEST] Add assert.Unreachable when unmarshalling legacy JSON stream snapshot#7498

Closed
alexbozhenko wants to merge 1 commit intomainfrom
legacy_snapshot_unmarhsall
Closed

[TEST] Add assert.Unreachable when unmarshalling legacy JSON stream snapshot#7498
alexbozhenko wants to merge 1 commit intomainfrom
legacy_snapshot_unmarhsall

Conversation

@alexbozhenko
Copy link
Copy Markdown
Member

Follow-up to #7486

Signed-off-by: Alex Bozhenko alexbozhenko@gmail.com

Signed-off-by: Alex Bozhenko <alexbozhenko@gmail.com>
@alexbozhenko alexbozhenko requested a review from a team as a code owner October 30, 2025 16:35
@alexbozhenko
Copy link
Copy Markdown
Member Author

@MauriceVanVeen Do I understand correctly that this place also should not be reachable?

@neilalexander
Copy link
Copy Markdown
Member

It wouldn't be possible to reach this in Antithesis without having already triggered the other assert, so don't think this is needed.

@MauriceVanVeen
Copy link
Copy Markdown
Member

Indeed this is in essence redundant. The snapshot needs to be created before it can be unmarshalled. And it's more useful to only fail on the server that creates it, than also on a follower that might receive it as a result.

The legacy snapshot code also will need to remain, as otherwise it can break existing deployments.

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