Repository navigation
Classify malformed CZDS records safely in preflight and aggregation - #9
Merged
Merged
Conversation
This was referenced Oct 22, 2026
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.
Context
Production
gov.txt.gzfailed non-leading-SOA preflight withreason=record_fields. The licensed record is not available in public CI, so this change classifies the structure of malformed records without making an unverified grammar relaxation.Changes
classify_record_fields()inbuild_nsdb.py:record_blank,record_fields_comment,record_fields_directive,record_fields_space_delimited,record_fields_missing_tabs, andrecord_fields_partial_tabs.Safety and interface boundaries
process_input()and aggregation interfaces remain unchanged; compatible with checkpoint issue Resume CZDS aggregation from verified per-zone checkpoints #6.Verification required
CI must pass. After merge, rerun preflight with the protected cached CZDS set and determine the newly surfaced
reason=<subcode>before designing a targeted parsing fix.Related: #5, #6, #7