[Iris] Add sections to the UI for task stats#3
Closed
wmoss wants to merge 1 commit into04-23-_iris_store_the_task_stats_in_sqlitefrom
Closed
[Iris] Add sections to the UI for task stats#3wmoss wants to merge 1 commit into04-23-_iris_store_the_task_stats_in_sqlitefrom
wmoss wants to merge 1 commit into04-23-_iris_store_the_task_stats_in_sqlitefrom
Conversation
The new UI sections show up for the task that is the Zephyr controller. Not sure if we want to bubble them up so the job view for the job that runs the single Zephyr controller task.
Owner
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Apr 23, 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
1 participant
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.
Describe what changed and why. Follow with bullets for
specific changes if needed. Keep it concise — this text becomes the squash-merge
commit message, so avoid markdown formatting (headers, tables, images).
e.g.
Title: [RL] Fix loss: use global token normalization instead of per-example
"""
This fixes a regression in the DAPO loss computation by switching
from per-example normalization (/ n_i) back to global token
normalization (/ N). Per-example normalization gives shorter responses
disproportionately more gradient weight, which hurts math reasoning
tasks where correct answers often require detailed, longer derivations.
Global normalization weights all examples equally regardless of response
length.
"""
Fixes #