Repository navigation
fix: bound Orca event logging with supported settings - #698
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.
Original AT run
38110687748reached real Tab and Enter actions but exceeded the unchanged 4MiB log guard. The private Orca customization now retains INFO output, sets the supported event level to FINEST and applies a never-match object-event filter. Readiness and final evidence bind the actual values and immutable vendor source to the original Orca identity. Remaining INFO output can still exceed the budget; native journey acceptance remains pending.Validation: the admitted finite qualification passed 26 methods, including all 31 new customization cases and 39 retained logging cases. The retained complete binder exercised the existing 247 Python controls/six groups as nested work. Owner receipts matched, cleanup observed an empty group, and source/runtime pins were unchanged. No new browser, service or native journey ran. The workflow and architecture map are unaffected.