claude-botandClaude Opus 5
cb751cbedc
Three of the first eleven documents in a run never terminated. One reached 10269 tokens on a classification that needs ~300, at a perfectly healthy 11 tok/s — so it read as slowness and was neither slow nor a context problem. llama-server's --n-predict defaults to -1, infinity, and paperless sets no token budget of its own and waits. Nothing anywhere bounded the request. Four documents cost most of an hour. --n-predict 768 on the sidecar caps it, and a truncated response is better evidence than a timeout: it shows what the model was doing instead of stopping. The client timeout drops to 300 s and becomes a backstop. Also: - the degeneracy check fired on 'Rechnung 2025-5425541' — 8 letters in 21 characters, below the 40% Latin threshold. Digits and punctuation are normal in a title; look for characters from other scripts directly instead of inferring them from a shortage of Latin ones. - the ctx-size comment still carried the claim bisection disproved in #777, that 32768 corrupts inference. The boundary is prompt length. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>