Uh oh!
There was an error while loading. Please reload this page.
Adaptive batch size, guarded retry, and max_tokens bump for enrich step - #454
Closed
neoneye wants to merge 2 commits into
Closed
Adaptive batch size, guarded retry, and max_tokens bump for enrich step#454neoneye wants to merge 2 commits into
neoneye wants to merge 2 commits into
Conversation
Bump gpt-oss-20b max_tokens from 8192 to 128000 to match its 131K context window. Add adaptive batch sizing based on context_window (not num_output, which just reflects max_tokens config) — batch_size=2 when context_window < 6000. Replace raise-on-error batch loop with guarded retry: split once (MAX_RETRY_DEPTH=1) within a 300s budget, then skip. Report actual batches_succeeded instead of hardcoded 1. Document consequence-echoing and UUID format inconsistency in OPTIMIZE_INSTRUCTIONS. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Collect batch retries, skipped batches, unknown lever IDs, validation errors, and incomplete levers into an errors list persisted alongside metadata and characterized_levers in the raw output file. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
neoneye
commented
Mar 30, 2026
MemberAuthor
Self-improve iteration — analysis 57Verdict: CONDITIONAL Wins:
Regression — max_tokens too high: gpt-oss-20b: 2/5 functional success (same as before, but failure mode changed from timeout → silent empty output) Fix needed: Reduce |
neoneye
commented
Mar 30, 2026
MemberAuthor
Closing — max_tokens=128000 leaves only 3072 input tokens, causing BadRequestError for 3/5 gpt-oss-20b plans. Will rework with max_tokens=65536 and explicit context_window=131072. |
This was referenced Mar 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
context_windowmetadata (notnum_outputwhich just reflects max_tokens config); usesbatch_size=2whencontext_window < 6000. gpt-oss-20b hascontext_window=3900so it getsbatch_size=2batches_succeededinstead of hardcoded1in runner.pySupersedes #453 which had a bug where
num_output(inflated by the max_tokens bump) disabled the adaptive batch size for gpt-oss-20b.Test plan
🤖 Generated with Claude Code