-
Notifications
You must be signed in to change notification settings - Fork 2k
fix(grok): preserve unknown usage for malformed billing tags #3357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a valid response contains an unknown length-delimited string or bytes field, the unconditional recursion at lines 501–507 applies this new field-number validation to its opaque contents. For example, an unknown bytes field containing
0x01followed by eight zero bytes is valid protobuf wire data, but this guard interprets that payload as nested field zero, marks the entire scan incomplete, and prevents an otherwise validated active period from supplying its implicit 0% usage. Restrict completeness validation to paths known to contain submessages, or avoid propagating nested malformedness from opaque unknown fields.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in c983271. The scanner now recurses only into the message paths declared by the official billing schema. Unknown length-delimited payloads are skipped entirely after checking their outer length; their bytes contribute neither completeness failures nor invented percentages/reset dates.
The six root/config opaque-payload regressions fail with 14 assertions before the repair and pass afterward. Tests also verify that malformed messages still block implicit zero at all 16 known message paths, and historical nested timestamps remain readable. The broader Grok/architecture run passes 191 tests; full-suite and exact-head CI verification are still running before merge.