test: add always-on JetStream integration gate - #2
Merged
Merged
Conversation
11 tasks
Contributor
Author
|
Review hardening added in the latest commit: JetStream history now scans the initial pending set in fixed 256-message pulls, keeps only the requested newest events, and applies one total request-timeout budget instead of sizing the client fetch buffer to the entire stream. The real JetStream ordering test now publishes 260 records so it crosses the batch boundary. Local all-feature tests (196 unit + 29 memory integration), strict Clippy, rustdoc, formatting, and diff checks pass; the hosted pinned-NATS job is the real-server evidence. |
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
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.
Summary
limitValidation
cargo fmt --all -- --checkcargo clippy --all-targets --all-features -- -D warningscargo test --all-targets --all-features(196 unit, 29 memory integration)cargo test --all-targets --no-default-features(131 unit)RUSTDOCFLAGS="-D warnings" cargo doc --all-features --no-depsRUSTDOCFLAGS="-D warnings" cargo test --doc --all-features(2 passed)cargo package --allow-dirtyA3S_EVENT_REQUIRE_NATS=1 cargo test --test nats_integration -- --nocapture --test-threads=1(11 passed)Issue scope
This is the first always-on JetStream evidence slice for #1. It intentionally does not close the issue: server/client restart, reconnect bounds, credential rotation, consumer-drift detection, poison-message/DLQ behavior, end-to-end metadata/schema behavior, and the full observability acceptance criteria remain for follow-up work.
Pinned image:
nats:2.11.8-alpine@sha256:71092f77d707a4a81b12aca5096d6b2d2e07ad16aa57c84066940a17af74f61a.