Verify cancelled ingestion preserves concurrent writes - #3
Draft
RhysSullivan wants to merge 1 commit into
Draft
RhysSullivan wants to merge 1 commit into
RhysSullivan wants to merge 1 commit into
Conversation
RhysSullivan
added this pull request to stack #4
September 24, 2026 17:34
RhysSullivan
force-pushed
the
test/ingest-cancellation
branch
from
September 28, 2026 13:12
f631e64 to
6e30aee
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Exercise the real collector over HTTP while an external SQLite lock holds concurrent writes. Cancel one caller, release the lock, and require the other callers to receive 200 with their data persisted.
The test fails with 503 on the original implementation and passes with the worker lifetime fix. The combined run passed 61 tests.