Repository navigation
deps: qualify lower-allocation typed span projection in the root stack - #178
Merged
Merged
Conversation
This was referenced Oct 21, 2026
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 ONLY the root exporter pin to reviewed/merged chucklehead-dev/jolt-otel-clickhouse#157 (
a6cbf939). Small typed span manifests on the selected native path avoid temporary location maps/vectors while preserving the classifier, fallback, complete captured attributes and confirmed Durable writes.SDK3366a332, driver3314b79, JSON/codec/provider pins, runtime floor, encoding/configuration defaults and
profiles/embeddedremain unchanged. The exporter-own SDK does not silently override Oscope's direct selection.Red/green and validation
Boundaries
Typed fixture3 uses an in-memory object backend and checks LIVE typed value/status. The independent file-backed recovery fixtures are separate cases; their greens are not a combined typed-recovery proof. Track that composition gap in #177.
No application throughput/tail, S3, Langfuse or packaging claim; no protocol/model change or unchanged exhaustive rerun. Minimal-profile refresh remains #167; this does NOT roll out stacked #144's ancestors.
Receipts and scope