Skip to content

Conversation

tillrohrmann
Copy link
Contributor

When trimming the log in the replicated setup, we cannot guarantee that all
log servers have seen the trim gap. Therefore, we need to make the assertions
a little bit more forgiving.

Note, this commit only fixes the test instability and leaves the trim semantics
untouched.

This fixes #3890.

We can remove the PartitionProcessorRpcError::Busy because we use flexbuffers to
encode the error variants when sending them over the wire and flexbuffers encodes
the variants by name.
When trimming the log in the replicated setup, we cannot guarantee that all
log servers have seen the trim gap. Therefore, we need to make the assertions
a little bit more forgiving.

Note, this commit only fixes the test instability and leaves the trim semantics
untouched.

This fixes restatedev#3890.
@AhmedSoliman AhmedSoliman merged commit 0dab81b into restatedev:main Oct 16, 2025
25 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Oct 16, 2025
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.

Flaky tests::three_logserver_readstream_with_trims

2 participants