Add a minimal Verifiers agentic regeneration demo#847
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
The quality checks have failed. Please run |
Merge Protections🔴 1 of 1 protections blocking · waiting on 👀 reviews
🔴 Require approval from approved reviewers listWaiting for any of
This rule is failing.All pull requests must have at least one approving review from a member of the approved reviewers list before merging.
|
There was a problem hiding this comment.
I think this PR conflates several data pipeline scripts.
- scripts/launch_vllm.py this is for online training hidden state generation, so it’s very slow, and we should not use it for regen.
- regen actually uses scripts/response_regeneration/run_all.sh
- Prepare and replay exact IDs —> this is for off-policy data preparation… we shouldn’t include it for any regen training.
This is indeed a very confusing UX. 😅 But it's a pre-existing bad design.
I suggest we fix the UX first.
What this demonstrates
verifiers==0.2.0and an exact research-environments commitinput_idsandloss_maskThe boundary is intentionally narrow: Verifiers owns environments, tools, Docker, turns, and scoring. Speculators does not add an environment wrapper or rollout loop.
Live demonstration
A Qwen3-8B Prolog run produced a six-turn trajectory with six assistant tool calls and five tool observations. The unsuccessful
max_turnstrace contained 5,708 exact tokens (4,914 sampled), and replay returned an exact token match with BF16 hidden states shaped(5708, 4, 4096).The zero reward is retained intentionally because failed trajectories are still valid on-policy data.
Scope
This omits generated rollout artifacts and does not lock ordinary transitive Python dependencies. The compatibility boundary is expressed through the direct pins in
pyproject.toml.Validation
uv sync --project scripts/agentic_regenerationsucceeds