Reject unsupported trace inputs and JSONL evidence truncation - #26
Merged
Conversation
tn-pisama
marked this pull request as ready for review
September 10, 2026 06:42
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.
Synthetic onboarding reproduced unsupported OTLP being parsed as zero spans and reported clean. This change rejects unsupported/empty native inputs and ambiguous multi-row trace-envelope JSONL instead of dropping evidence. Supported native spans with optional IDs and existing ATIF paths remain supported. Root verification: 215 tests passed, including 19 focused parser and real CLI subprocess regressions. This is technical regression evidence, not detector accuracy or customer validation. No version bump or package publication. Draft opened to run the existing Python matrix and security gates before integration.