graph build's unknown-key refusal points at the wrong line — cite the op index instead #336
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Brummel/Aura#336
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Field evidence (harvest-sweep fieldtest, 2026-07-24, source-blind against the release binary):
aura graph buildon an op-list whose element carries an unknown key (paramson line 3) refuses with the right key name but cites "line 4 column 2" — the start of the FOLLOWING valid element. Recovery is still carried by the key name (low severity), but the line pointer misleads in longer op-lists.Likely cause: serde reports the deny-unknown-fields fault at the position it detects it (after consuming the element). Fix direction: wrap the parse fault with the offending op index, as #326's original note suggested ("refusing with the offending key and op index") — the index is the op-list's natural coordinate and immune to serde's token position.
Corpus: fieldtests/harvest-sweep/hs_2_typo_key.ops.json.