fix: handle trace event budget exhaustion - #265
Merged
Conversation
Reject undersized and statically over-budget trace events before attach. Treat nested payloads atomically so truncated events remain structurally valid, and cover the failure modes with end-to-end tests.
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.
Summary
creation
budget instead of silently dropping the event at runtime
<truncated>rather than exposing invalid nested-child markersfailure modes
Testing
cargo fmt --all -- --checkcargo clippy --all-targets --all-features -- -D warningscargo test -p ghostscope-compiler(168 passed)cargo test -p ghostscope(77 passed)new regression tests (runner
c845590953cc)Container-topology e2e was not run because this change does not affect container
or PID-namespace behavior.