-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ui] Remove simulacral allocation stat in favor of live-updating one #23306
[ui] Remove simulacral allocation stat in favor of live-updating one #23306
Conversation
@@ -185,6 +185,10 @@ export default class JobStatusPanelSteadyComponent extends Component { | |||
return this.job.allocations.filter((a) => !a.isOld && a.hasBeenRestarted); | |||
} | |||
|
|||
get runningAllocs() { | |||
return this.job.allocations.filter((a) => a.clientStatus === 'running'); | |||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@job.runningAllocs
comes from the job's summary as defined here in case you were curious
Ember Test Audit comparison
|
8e641ed
to
b8880c0
Compare
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
While most of our job status panel allocation numbers use allocations live as they're updated from the /allocations endpoint for a given job, one holdout remained: the the "X Allocations Running" number came from the
job-summary
, which tabulates at a slightly different time than allocations do (and is sometimes susceptible to inaccuracy)This changes the number in steady-state jobs to be what we actually see among currently running allocations from the /allocations endpoint. This doesn't discriminate between new-version and old-version allocations, only returning the number currently running.
Resolves #20627