Skip to content

Bound multiline flow span metadata - #90

Draft
jskoiz wants to merge 1 commit into
mainfrom
c1/issue-77-flow-span-metadata
Draft

Bound multiline flow span metadata#90
jskoiz wants to merge 1 commit into
mainfrom
c1/issue-77-flow-span-metadata

Conversation

@jskoiz

@jskoiz jskoiz commented Aug 21, 2026

Copy link
Copy Markdown
Owner

Summary

  • Replace per-byte flow SourceMark metadata with compact affine source segments.
  • Cap retained flow metadata at 4,096 segments while retaining normalized flow parsing and a safe final-tail fallback for oversized metadata regions.
  • Add a bounded multiline-flow metadata regression and an exact physical-source-location regression.

Closes #77

Verification

Local proof:

  • cargo fmt --all --check
  • git diff --check
  • cargo check --locked --lib
  • cargo clippy --locked --lib -- -D warnings
  • cargo test --locked --lib — 67 passed
  • cargo test --locked --test diagnostics — 44 passed
  • cargo test --locked --test yaml_test_suite multiline_flow — 2 passed
  • cargo test --locked --test dos_hardening multiline_unterminated_flow — 2 passed

Hosted/merge state:

  • This is a draft PR; hosted CI has not been observed in this task.
  • The PR has not been merged.

Notes/Risks

  • Exact source locations are retained through the bounded segment budget; after overflow, spans use the first omitted source boundary, except that the final flow tail remains exact. Parsing behavior and normalized flow text are unchanged.
  • No exploit payloads were added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[P1] Bound per-byte flow span metadata

1 participant