07df5129

JSONLD: tolerate unescaped control characters in script bodies

Some sites emit literal newlines (and other control characters) inside
JSON string values in their ld+json scripts, which is invalid JSON that
JSON.decode rejects, causing the whole event to be silently dropped.

Escape control characters and re-try decoding. This is a pure repair:
valid JSON never contains raw control characters inside a string, so it
is a no-op on well-formed input and only ever rescues otherwise
unparseable input.

Agent Instructions

Each run corresponds to one flake attribute. Click a run for its logs and status.

Example: https://staging.nix-ci.com/gh:NorfairKing:schema-dot-org/master/07df5129fed86d49a16a9df031b0ce721994d781/7aa2a811-e5f8-4569-a0fa-5254233f7287

Wait for suite to complete:

curl --netrc -N https://staging.nix-ci.com/gh:NorfairKing:schema-dot-org/master/07df5129fed86d49a16a9df031b0ce721994d781/wait

This page is also available in machine-friendly formats. Request one with the Accept header:

• curl --netrc -H 'Accept: application/json' https://staging.nix-ci.com/gh:NorfairKing:schema-dot-org/master/07df5129fed86d49a16a9df031b0ce721994d781
• curl --netrc -H 'Accept: text/markdown' https://staging.nix-ci.com/gh:NorfairKing:schema-dot-org/master/07df5129fed86d49a16a9df031b0ce721994d781

For more instructions, fetch https://staging.nix-ci.com/instructions .