Repository navigation
fix(engine): bound the relayfile record stored in message metadata - #702
Conversation
The relayfile inbound bridge stored the whole parsed provider record (up to
the 1 MiB body limit) in messages.metadata, and that metadata is copied again
into the webhook outbox and stream events. Nothing bounded it.
A record whose JSON is over 8 KiB (UTF-8; engine config
relayfileRecordMetadataMaxBytes) is now stored as record: null plus
record_omitted { reason, bytes, limit }. Path, revision and the rest of the
metadata stay, so consumers can fetch the record from relayfile. Message
text and the idempotency fingerprint are unchanged.
Co-Authored-By: Claude <noreply@anthropic.com>
… batch/20261120-0902
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
|
Review round 1: SIGNOFF (cost $2.3198, batch total $2.3198) |
|
SIGNOFF. The batch deploys only relaycast-cloud; nothing to deploy for this repo. |
[Medium impact] The code appears safe to merge once the required human approval is given.
|
Hourly batch from the relaycast agent host:
batch/20261120-0902onorigin/main, one merge commit per branch below.Changes
origin/agent/relayfile-record-capbb49118 fix(engine): bound the relayfile record stored in message metadata
The relayfile inbound bridge stored the whole parsed provider record (up to
the 1 MiB body limit) in messages.metadata, and that metadata is copied again
into the webhook outbox and stream events. Nothing bounded it.
A record whose JSON is over 8 KiB (UTF-8; engine config
relayfileRecordMetadataMaxBytes) is now stored as record: null plus
record_omitted { reason, bytes, limit }. Path, revision and the rest of the
metadata stay, so consumers can fetch the record from relayfile. Message
text and the idempotency fingerprint are unchanged.
Co-Authored-By: Claude noreply@anthropic.com
Diff vs
origin/main: 7 files changed, 222 insertions(+), 4 deletions(-)Paths:
CHANGELOG.md,docs/repository-guide.md,openapi.yaml,packages/engine/Verification
Gating
Draft on purpose. Merging, npm releases and production deploys need a human (Khaliq's direct OK). The batch only deploys to this host's stage (
dev), and only after a reviewer SIGNOFF.Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.