Repository navigation
deps: qualify guarded stock codec in capture paths - #179
Merged
Merged
Conversation
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
Update the root exporter to merged
b4149754and both optional stock-Jolt codecaliases to
c75579b9. This brings the guarded private-byte-store encoder intoOscope's existing opt-in capture path, reducing per-byte encoder bookkeeping.
Keep the SDK, driver, JSON and provider pins, encoding defaults and minimal
embedded profile unchanged. This does not enable preparation overlap or
claim an Oscope throughput/tail improvement. Typed live-query coverage remains
separate from fresh-reader capture coverage; this does not close #177.
Validation
aliases (10 assertions pass, 1 fails), then passes after repinning (11 pass).
stock Jolt 0.8.23 and chDB 26.9.0. Capture fixtures require post-startup codec
and native-stream witnesses, not constructor activity alone, and independently
joined fresh-reader receipts.
capture gates retain their existing assertions.
standalone capture 1/45; typed live-query 1/8; optional HTTP reader capture
1/45, with 3 actual native document reads accepted and 0 declined. All pass.
exporter/codec and unchanged SDK/driver/JSON/provider SHAs. Minimal embedded
profile has no diff; source hashes stayed stable through native gates.
verification. Changelog and exact-resolution expectations are updated.
No credentials, captured telemetry or persisted database artifacts are included.
Hosted CI remains required before merge. Native correctness receipts do not
establish an application throughput or slow-tail improvement.