docs(parsers): explain framing for later fields and rows (#12331)

This commit is contained in:
morluto authored and GitHub committed 2026-11-19 07:49:54 -05:00
1 parent 39d20dce3d
commit ddcd62009b
2 files changed
+11 -5

No files matched your search

+5 -3
View File
@@ -762,9 +762,11 @@ control that keeps completed Evidence inline and preserves the original failure.
For a seekable file with a known extent, distinguish a provably impossible wire
extent from an independent representation limit. Pair the malformed declaration
with a structurally possible over-limit control. A count-only truncated fixture
does not establish capacity behavior. This does not require decoding an opaque
compressed payload merely to apply its declared expansion limit.
with a structurally possible over-limit control. Include a length that fits the
remaining bytes by itself but would consume the framing required for a later
field or row. A count-only truncated fixture does not establish capacity
behavior. This does not require decoding an opaque compressed payload merely
to apply its declared expansion limit.
When producer order is unspecified, synchronize fixtures on the observed request
or completion event. A filename, generated key, or fixed delay does not prove
+6 -2
View File
@@ -279,8 +279,12 @@ and independently specified expectations. See [boundary regressions](testing.md#
Give each nested parser the admitted extent of its containing record.
Check a child's declared encoded range against that extent before applying
its decoding allowance. When the range cannot fit, report the format failure
even if the declared decoded size would also exceed a budget.
its decoding allowance. If the format declares more fields or rows after the
child, leave room for their minimum required framing. When the range cannot
fit, report the format failure even if the decoded size would also exceed a
budget. Keep encoded ranges separate from declared decoded lengths so an
expansion limit can preserve the source range and any independently readable
siblings.
Retain the source offset and the reason when a field is malformed or its
encoding is unsupported. A stream may need more bytes to complete a frame.
A completed artifact with the same missing bytes has truncated data. Carry