Repository navigation
[trainer] fix: capture channel metadata before accounting - #1224
YLlllllllllll wants to merge 1 commit into
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: ByteDance-Seed/VeOmni/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 8 included reviews per hour; 5 remain after this review. 📝 WalkthroughWalkthrough
ChangesChannel-loss callback ordering
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~15 minutes Change: Bug fix Sequence Diagram(s)sequenceDiagram
participant BaseTrainer
participant channel_loss_callback
participant self_callbacks
BaseTrainer->>channel_loss_callback: on_step_begin(state, micro_batches, kwargs)
BaseTrainer->>self_callbacks: iterate registered callbacks
BaseTrainer->>self_callbacks: skip channel_loss_callback
Suggested reviewers: Merge Risk: ⚪ Minimal · up to The trainer preserves channel metadata visibility and avoids duplicate callback invocation; no concrete correctness or availability risk currently blocks merge. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ 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 |
Superseded by #1276. Its complete registered-callback metadata-before-meter behavior, once-only dispatch and unchanged step-end ordering are retained in the current-main channel-loss lifecycle implementation. Both unique lifecycle tests are covered there with stronger keyword-forwarding checks. Independent immutable-source comparison and five lifecycle checks passed. Review #1276, then #1006 for compact source metrics.