chore: bump verifiers to main (v1 seq_len fix)#2692
Merged
Conversation
Advances deps/verifiers e1d4f259 -> 05c66c23, which includes the merged v1 token-usage fix (#1525): v1 envs now record final/context token usage at write time, so wandb seq_len and progress/tokens are no longer 0. Validated end-to-end with configs/debug/reverse_text_v1.toml: seq_len/all/mean 0 -> 160. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
samsja
approved these changes
Jun 2, 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 free
to 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.
What
Bumps the
deps/verifierssubmodulee1d4f259 → 05c66c23(current verifiersmain).The headline reason is the merged v1 token-usage fix (verifiers#1525): for v1 environments,
token_usage.final_input_tokens/final_output_tokenswere always 0 because the trajectory's responses are serialized to plain dicts andcompute_context_token_metricsgated onisinstance(response, Response). That zeroed our wandbseq_len/*andprogress/tokensmetrics. v1 now records those metrics at write time from the liveResponse.The bump also pulls in the other commits merged to verifiers main since
e1d4f259(Scale-SWE taskset, v1 sandbox runtime scaling, Multi-SWE patch alignment, unbounded harness max_turns, port-rebind fix).Validation
Ran
configs/debug/reverse_text_v1.tomlend-to-end on GPU against the bumped submodule:seq_len/all/meanprogress/tokensFull inference + orchestrator + trainer loop completed cleanly on the new main.
uv.lockunchanged (verifiers is a workspace/path dep).Note
Low Risk
Dependency-only submodule pointer update with no in-repo logic changes; validated on a debug v1 training run with improved metrics reporting.
Overview
Updates the
deps/verifiersgit submodule frome1d4f259to05c66c23(current upstreammain), so this repo picks up verifiers’ v1 token-usage fix: trajectory responses serialized as dicts no longer leavetoken_usage.final_input_tokens/final_output_tokensat zero, which restores meaningfulseq_len/*andprogress/tokensreporting (e.g. wandb) instead of flat zeros.The same bump also brings in other recent verifiers
mainwork (Scale-SWE taskset, v1 sandbox runtime scaling, Multi-SWE patch alignment, unbounded harnessmax_turns, port-rebind fix).uv.lockis unchanged because verifiers is a workspace/path dependency; validation noted a fullreverse_text_v1debug run with non-zero sequence-length and token progress metrics.Reviewed by Cursor Bugbot for commit db56c75. Bugbot is set up for automated code reviews on this repo. Configure here.