You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the job completion plugin runs, the jobstatus of the Job it sends to the API is "COMPLETING". By contrast, when a script running later to fill in missing jobs runs, the status (taken directly from sacct) it sends is "COMPLETED".
In coldfront.core.statistics.forms.JobSearchForm, the "COMPLETING" value is mapped to the display label "Completed" so that when a user filters for jobs with status "Completed", jobs with jobstatus "COMPLETING" are returned. Jobs with jobstatus "COMPLETED" (i.e., those filled in by a script after the fact) are not returned.
The simplest approach is to update JobSearchForm to filter "Completing" and "Completed" separately, but this would be confusing for users.
Ideally, it'd be possible to map two values in a form field to the same display label.
Another option is to convert all "COMPLETING" values to "COMPLETED" (a) for all existing jobs and (b) in the API endpoint that the job completion plugin invokes.
The text was updated successfully, but these errors were encountered:
When the job completion plugin runs, the
jobstatus
of theJob
it sends to the API is "COMPLETING". By contrast, when a script running later to fill in missing jobs runs, the status (taken directly fromsacct
) it sends is "COMPLETED".In
coldfront.core.statistics.forms.JobSearchForm
, the "COMPLETING" value is mapped to the display label "Completed" so that when a user filters for jobs with status "Completed", jobs withjobstatus
"COMPLETING" are returned. Jobs withjobstatus
"COMPLETED" (i.e., those filled in by a script after the fact) are not returned.JobSearchForm
to filter "Completing" and "Completed" separately, but this would be confusing for users.The text was updated successfully, but these errors were encountered: