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
🤖 fix: update tb.lock before resume to apply concurrency changes immediately
Addresses Codex feedback: Previously, concurrency adjustments were written to
tb.lock AFTER a burst completed, but the next resume command would read the
tb.lock at the START of the burst. This created a 1-burst delay where the
old concurrency was used even after adjustment.
Now updates tb.lock BEFORE calling 'terminal-bench runs resume', ensuring
the new concurrency takes effect immediately. This is critical when the system
is overloaded - we need to reduce concurrency on the very next burst, not one
burst later.
Flow before fix:
Burst N completes → adjust_concurrency() → write tb.lock
Burst N+1 starts → resume reads OLD tb.lock value
Flow after fix:
adjust_concurrency() completes
Burst N+1 starts → write tb.lock → resume reads NEW tb.lock value
0 commit comments