Relationships
#4957 data query --select content and foreign-content hydration load oversized items without the resource load guard
Opened by zack · 11/20/2026
Follow-up to #4941. The ResourceLoadGuard refuses to decode stored content that would exhaust the V8 heap, but two DataQueryService paths still read and decode without it. First, the content projection for a --select content query (the projectedContent and projectedContents methods): with a select that needs no attributes, nothing is hydrated during matching, and the projection reads and encodes every matched body as UTF-8 or base64. Second, hydrateForeignRecord, which runs JSON.parse on content fetched from another namespace. Example: swamp data query 'true' --select content matching several 400 MiB text items still aborts V8 with an out-of-memory error. Fix: call the repository load guard on the recorded size before those reads and on the byte length after, keeping the include gating so a refusal never names an item the caller may not read; then confirm the design/primitives/data.md Load guard claim that every decoding path is guarded.
Open
No activity in this phase yet.
Sign in to post a ripple.