Skip to content

xmemory: raise recall answer budget 4KB -> 16KB - #412

Merged
pufit merged 1 commit into
mainfrom
pufit/xmemory-answer-budget-16k
Aug 25, 2026
Merged

xmemory: raise recall answer budget 4KB -> 16KB#412
pufit merged 1 commit into
mainfrom
pufit/xmemory-answer-budget-16k

Conversation

@pufit

Copy link
Copy Markdown
Member

The recall handler clips xmemory's read result to _MAX_XMEM_ANSWER_BYTES = 4_000 before appending it to the memU block. 4KB is tight for the structured read modes (raw-tables / xresponse) and for decomposed multi-sub-query answers (reader_results), which get truncated mid-payload.

This bumps the sub-budget to 16KB. Sizing: memU part is capped at 10KB (_MAX_RECALL_BYTES), so the combined worst case is ~26KB — still well under the ~55KB harness inline-output limit that these budgets exist to stay clear of (see #95).

One-line constant change + comment; no behavior change below 4KB. Full test suite passes (3360).

Generated by Nerve

@pufit
pufit merged commit a15dd70 into mainAug 25, 2026
2 checks passed
@pufit
pufit deleted the pufit/xmemory-answer-budget-16k branch August 25, 2026 19:12
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@pufit