You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
id(world): result_too_large is an undocumented capability wire error code #837
result_event emits {"cap":"result",…,"ok":false,"error":"result_too_large"} (pkgs/id/src/world_caps.rs:325). That code is not a CapErrorCode variant, and it is missing from the module's refusal-code table (world_caps.rs:33-40). The module doc says codes are a stable wire contract that the DoS suite asserts, and F11.13's exit criterion is "every CapError carries a documented code". This one is outside both. Fix: add it to the enum and the table, or map it to failed with a reason.
result_too_large is either a CapErrorCode variant documented in the refusal-code table in world_caps.rs, or the emit site maps it to failed with a reason
The DoS suite's code assertions cover the result path (oversized result carries a documented code)
No other emit site in world_caps.rs produces an undocumented error string (grep audit recorded)
Still live: verified on current main (a2eef6f) — pkgs/id/src/world_caps.rs:325 still emits "error":"result_too_large" as a bare string; it is not in the refusal-code table (lines 33–40) and is not a CapErrorCode variant (enum at line ~359 has Denied/Unknown/BadArgs/Failed/ActorDenied/OutsideCeiling only).
Related:#789 (found while writing the F13.7 design).
Notes / risks: none material — the smallest item in this batch. Either resolution (new code vs map to failed + reason) is defensible; adding the variant keeps the oversized-result case distinguishable for clients and the DoS suite.
Suggested approach: add the variant + table row, extend the existing assertion at world_caps.rs:860 (which already checks the string appears) to assert the documented code path.
🤖 Fleet monitor intake enrichment — acceptance criteria appended to the body, labels normalized and meta/enriched applied this pass.
Task: Implementing the triage-pinned fix (task 2261, option a): add CapErrorCode::ResultTooLarge (result_too_large), document it in the world_caps refusal-code table, route result_event's oversized fallback through the enum, and strengthen the bounded-result test to assert the parsed error equals the variant's code(). Wire string unchanged.
Fix:CapErrorCode::ResultTooLarge added with code() == "result_too_large", CapError::result_too_large() constructor, refusal-code table row in the world_caps module doc, and result_event's oversized fallback routed through the enum (wire string unchanged). Bounded-result test now asserts the parsed error equals the variant's code().
Activity
docs(id): design client-side capability providers under the ceiling m…
dezren39 commentedon Oct 26, 2026
Intake review
Still live: verified on current main (a2eef6f) —
pkgs/id/src/world_caps.rs:325still emits"error":"result_too_large"as a bare string; it is not in the refusal-code table (lines 33–40) and is not aCapErrorCodevariant (enum at line ~359 has Denied/Unknown/BadArgs/Failed/ActorDenied/OutsideCeiling only).Related: #789 (found while writing the F13.7 design).
Notes / risks: none material — the smallest item in this batch. Either resolution (new code vs map to
failed+ reason) is defensible; adding the variant keeps the oversized-result case distinguishable for clients and the DoS suite.Suggested approach: add the variant + table row, extend the existing assertion at
world_caps.rs:860(which already checks the string appears) to assert the documented code path.🤖 Fleet monitor intake enrichment — acceptance criteria appended to the body, labels normalized and
meta/enrichedapplied this pass.dezren39 commentedon Nov 1, 2026
🤖 Agent note · picked up
1 remaining item
dezren39 commentedon Nov 1, 2026
🤖 Agent note · state: picked up
CapErrorCode::ResultTooLarge(result_too_large), document it in the world_caps refusal-code table, route result_event's oversized fallback through the enum, and strengthen the bounded-result test to assert the parsed error equals the variant'scode(). Wire string unchanged.Merge pull request #3786 from developing-today/queue/4859-837-result-…
dezren39 commentedon Nov 1, 2026
🤖 Agent note · state: done
CapErrorCode::ResultTooLargeadded withcode() == "result_too_large",CapError::result_too_large()constructor, refusal-code table row in the world_caps module doc, andresult_event's oversized fallback routed through the enum (wire string unchanged). Bounded-result test now asserts the parsed error equals the variant'scode().cargo test --features web --lib world_caps::(laptop): 16 passed, 0 failed. (A bareworld_capsfilter also matchescli::tests::test_cli_parse_world_caps_ceiling, which stack-overflows pre-existing on clean main — covered by id(cli): test_cli_parse_cat stack-overflows in the pkgs/id test binary (pre-existing, parse path) #3438, data point added there.)