Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

bound maximum serialization depth to < 128, similar to serde_json #1757

Merged
merged 2 commits into from
Nov 5, 2024
Merged

bound maximum serialization depth to < 128, similar to serde_json #1757

merged 2 commits into from
Nov 5, 2024

Commits on Nov 4, 2024

  1. doc: SerPolicy now enforces maximum serialization depth 

    SerPolicy now tracks node depth and omits array items or object
properties which would violate a bound on maximum document depth.

This is largely motivated by serde_json: in all conditions,
we never want to emit a document which cannot be parsed by serde_json.

The serde_json limit of 128 is generous so we follow their lead.
    @jgraettinger
    jgraettinger committed Nov 4, 2024
    Configuration menu
    Copy the full SHA
    e973bb1 View commit details
    Browse the repository at this point in the history

  2. runtime: add the source or target collection to parsing errors 

    When these occur, it can be tedious to track down which binding caused
the failure. Adding the source or target collection name is key
debugging info to aide in investigations.
    @jgraettinger
    jgraettinger committed Nov 4, 2024
    Configuration menu
    Copy the full SHA
    815f074 View commit details
    Browse the repository at this point in the history