Evenfire is an intelligence layer platform for running LLM agents that take real actions, on your infrastructure
TypeScript
fix(contract): name the element-bound refusal distinctly from the byte bound (#731)
Alfredo Lopez38d6503199d6
diff --git a/packages/grok-provider-attempt-contract/index.cjs b/packages/grok-provider-attempt-contract/index.cjsindex 42e6d7ebb..10be620d1 100644--- a/packages/grok-provider-attempt-contract/index.cjs+++ b/packages/grok-provider-attempt-contract/index.cjs@@ -191,7 +191,15 @@ function checkStructure(value, maxDepth) {: Object.values(node).filter(child => child !== undefined)elements += children.lengthif (elements > LIMITS.maxRequestBodyBytes) {- return fail('limit', 'request exceeds maxRequestBodyBytes')+ // Named distinctly from the byte measurement below, which refuses with+ // the bare `request exceeds maxRequestBodyBytes`. Both are `limit`+ // failures and `fail()` carries no field beyond code and message, so the+ // wording is the only thing that tells a user report which guard fired -+ // and the two have different remedies (#731). The bound is reused rather+ // than given a constant of its own because an element is cheaper than a+ // byte to serialize: a structure with more elements than the byte cap+ // cannot fit under it.+ return fail('limit', 'request exceeds maxRequestBodyBytes element bound')}for (const child of children) {if (child !== null && typeof child === 'object') stack.push(child, depth + 1)diff --git a/packages/llm-provider-attempt-contract/index.cjs b/packages/llm-provider-attempt-contract/index.cjsindex 99ece4f0c..2db5ba59f 100644--- a/packages/llm-provider-attempt-contract/index.cjs+++ b/packages/llm-provider-attempt-contract/index.cjs@@ -182,7 +182,15 @@ function checkStructure(value, maxDepth) {const children = Array.isArray(node) ? node : Object.values(node).filter(child => child !== undefined)elements += children.lengthif (elements > LIMITS.maxRequestBodyBytes) {- return fail('limit', 'request exceeds maxRequestBodyBytes')+ // Named distinctly from the byte measurement below, which refuses with+ // the bare `request exceeds maxRequestBodyBytes`. Both are `limit`+ // failures and `fail()` carries no field beyond code and message, so the+ // wording is the only thing that tells a user report which guard fired -+ // and the two have different remedies (#731). The bound is reused rather+ // than given a constant of its own because an element is cheaper than a+ // byte to serialize: a structure with more elements than the byte cap+ // cannot fit under it.+ return fail('limit', 'request exceeds maxRequestBodyBytes element bound')}for (const child of children) {if (child !== null && typeof child === 'object') stack.push(child, depth + 1)