Fix record parser when the FLAGS item is omitted - #119
Merged
Conversation
Member
|
Thanks. Please update your PR: keep only the changes to |
dajiaohuang
force-pushed
the
fix/118-record-parser-flags
branch
from
August 24, 2026 14:41
8842e55 to
c78453e
Compare
Contributor
Author
|
Updated in Validation:
The full CLI command could not run in this environment because |
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.
This PR fixes #118
Problem
The record parser accepts item flag combinations that omit the FLAGS field, but parse_line unconditionally parsed that missing field and raised TypeError.
Changes
Verification