Repository navigation
fix(telemetry): separate result streams and preserve startup panic privacy - #15
Merged
Merged
Conversation
rldyourmnd
changed the title
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.
Add a selectable bounded stderr sink so the native agent can reserve stdout for one JSON result. Install a safe panic fallback before output initialization, including when the console is unavailable.
The owned Compose fixture driver can expose private loopback gateway/query receipts for real native acceptance, retaining finite lifetime and cleanup ownership. Android sink acceptance now selects its output explicitly.
Validation: SDK tests and process acceptance (stderr diagnostics, one stdout result, unavailable-console panic privacy), canonical checks, Android x86_64 Clippy, and the real Compose pipeline with PostgreSQL, Vector and OpenObserve.