Skip to content

fix(miniswe): restore bounded observations and length-aware recovery - #3624

Merged
lafrancef merged 1 commit into
mainfrom
flafrance/miniswe-bounded-observations
Sep 22, 2026
Merged

lafrancef merged 1 commit into
mainfrom
flafrance/miniswe-bounded-observations

Conversation

@lafrancef

@lafrancef lafrancef commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

Large shell outputs were replayed without mini-SWE’s default cap, and context/output limits could appear as repeated tool-call format failures. Restore the pinned mini-SWE observation template (5,000-character head and tail), retain full output in trajectories, and include command-timeout feedback.

Pass output truncation into mini-SWE’s recovery prompt and distinguish ContextWindowExceeded / OutputTokenLimitExceeded from malformed calls, allowing partial work to reach verification. To enable explicit context-overflow handling with the vLLM adapter, set policy_model.responses_api_models.vllm_model.propagate_context_overflow_errors=true as documented in the agent README. This changes model-visible observations and may affect benchmark results.

Real Qwen3.8 Flash Next TB4 rollouts at the pre-rebase commit 28920b828c8e56f0be8db693ef2fcae05eadc774 confirm bounded observations, agent-to-verifier completion, length-aware recovery, and three propagated context-overflow terminations followed by completed verification. The full 66-task comparison is still running; keep this PR as a draft until the results are reviewed. Repeated OutputTokenLimitExceeded termination has not yet been observed in the live run.

Local check limitation: pre-commit run --all-files could not start because this Jujutsu workspace has no .git directory; the full hook suite remains pending. The commit includes DCO sign-off.

Rebased onto main at e86746aa. The overlapping length-aware recovery change keeps upstream’s "stop" finish reason for non-truncated responses. The ongoing rollout retains its original commit pin; no fresh full benchmark has been run on the rebased head.

No separate issue is needed for this focused correction to the existing mini-SWE integration.

@lafrancef lafrancef added bug Something isn't working area:agent Agent harnesses and Responses API agent behavior labels Sep 22, 2026
@copy-pr-bot

copy-pr-bot Bot commented Sep 22, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@lafrancef

Copy link
Copy Markdown
Contributor Author

/ok to test 28920b8

Use the pinned mini-SWE observation template and preserve timeout feedback. Forward output limits to recovery prompts and distinguish exhausted context from malformed tool calls while retaining partial work for verification.

Signed-off-by: Frederic Lafrance <flafrance@nvidia.com>
@lafrancef
lafrancef force-pushed the flafrance/miniswe-bounded-observations branch from 28920b8 to 40c9715 Compare September 22, 2026 18:27
@lafrancef

Copy link
Copy Markdown
Contributor Author

/ok to test 40c9715

@github-actions

Copy link
Copy Markdown
Contributor

πŸ”„ Merge queue validation started! You can track the progress here: https://github.com/NVIDIA-NeMo/Gym/actions/runs/35769065832

Merged via the queue into main with commit a6b2ea5 Sep 22, 2026
37 checks passed
@lafrancef
lafrancef deleted the flafrance/miniswe-bounded-observations branch September 22, 2026 18:53
lafrancef added a commit that referenced this pull request Sep 22, 2026
…3624

Cherry-pick a6b2ea5 onto the shared episode implementation. Preserve the standalone mini-SWE and TB4 resource session adapters.

Signed-off-by: Frederic Lafrance <flafrance@nvidia.com>
@athitten athitten mentioned this pull request Oct 28, 2026
7 tasks done

This branch was previously deployed

1 inactive deployment
public β€” 40c9715c Deployed Sep 22, 2026 by copy-pr-bot[bot] via release / finalize / notify #3524
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:agent Agent harnesses and Responses API agent behavior bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants