Skip to content

Allow WANDB_ENTITY override via caller environment#1

Open
dhadfieldmenell wants to merge 2 commits into
mainfrom
fix/wandb-entity-override
Open

Allow WANDB_ENTITY override via caller environment#1
dhadfieldmenell wants to merge 2 commits into
mainfrom
fix/wandb-entity-override

Conversation

@dhadfieldmenell

Copy link
Copy Markdown

Summary

  • training/verl_training.sh hardcoded WANDB_ENTITY="sample-efficient-rlvr", clobbering any value set by the caller before invoking the script.
  • Changes it to ${WANDB_ENTITY:-sample-efficient-rlvr} so a pre-set value wins, defaulting to the original team when unset.

Test plan

  • Verified via verl/utils/tracking.py that WANDB_ENTITY is read purely from the environment (no Hydra config key), so this is a pure shell-level fix.

dhadfieldmenell and others added 2 commits July 20, 2026 10:29
Previously hardcoded to the original authors' W&B team, which clobbers
any pre-set value and breaks logging for anyone running on their own
W&B account.
self_distillation_mask previously excluded any sample that didn't have
a successful within-group demonstration or usable feedback (gated by
reward_tensor via success_reward_threshold). But the self-distillation
loss never reads reward/advantages at all (see
compute_self_distillation_loss's argument list) — reward's only role
here was deciding which samples got distilled, conflating "the task's
reward function liked this rollout" with "this sample should be
distilled." Those are unrelated once reward is just a placeholder/proxy
rather than the actual training objective (as it is for the current
Engaging smoke test, and will be once GOOD's context replaces the
solution/feedback reprompt entirely). Every sample now participates
unconditionally.

Verified on Engaging (2x H200, Qwen3-8B, tooluse dataset): 3/3 training
steps complete, self_distillation/reprompt_sample_fraction now 1.0 at
every step (previously 1.0/0.96875/0.96875, gated by success/feedback
availability).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant