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
Commit 1453824
Browse filesBrowse the repository at this point in the historyBrowse files
fix(analyst): bound spill memory per row and keep the routing notice under tight output limits
- The full-text spill serialiser emitted one string fragment per JSON token and
held them all until the join, so a permitted wide numeric result retained
millions of fragments. It now emits one bounded string per row; the tagged
serialisation and the 32 MiB preflight are unchanged.
- Under a tiny `tool_output.max_lines` the fail-open routing notice was clipped
before its text and then overwritten. The notice is reserved first and the
result and remaining notes are fitted into what is left.
Tests: 2,000 × 150 numeric rows spill with identical bytes and one retained
chunk per row; a full-text query under a ten-line limit keeps the routing notice.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
spill=`All ${result.rows.length} returned rows saved to ${metadata.result_path}. JSONL text: columns/values per row; $bigint, $date (ISO), $bytes (base64) tags; strings unchanged. Use read with char_offset/max_chars to recover any clipped text.`
473
475
}catch{
474
476
spill=`Spill failed (write/serialization error or ${SQL_MAX_SPILL_BYTES/1024/1024} MiB size limit); returned rows were not saved.`
0 commit comments