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
Description:
The "Task executions" view shows the wrong status for RUNNING tasks. They are reported as "ERROR"/
The detail view shows the correct status as "RUNNING". The tasks run fine. No, errors in the logs.
Release versions:
Fails in 2.10.0
Was ok in 2.9.6
Screenshots:
The text was updated successfully, but these errors were encountered:
On the UI we're reading the status property which seems to be not aligned to the model defined for the Task Executions list.
This should be TaskExecutionStatus as I dig into the TaskDefinitionResource class. @cppwfs Can you please confirm this property TaskExecutionStatus is the correct one for the list on this page ?
@cppwfs
Yes, the loader was started twice (because it reported the status as ERROR). Both tasks were running in parallel and succeeded without error.
The same behavior is observed with only 1 task running. I wonder where the ERROR status is coming from.
It is not set in the backend response, but the status is set to ERROR in the frontend model.
The UI seems to set status code to ERROR if the exitCode is not 0, but the task is running and the exitCode is not yet set. I would expect the STATUS should be RUNNING or at least UNKNOWN.
Description:
The "Task executions" view shows the wrong status for RUNNING tasks. They are reported as "ERROR"/
The detail view shows the correct status as "RUNNING". The tasks run fine. No, errors in the logs.
Release versions:
Fails in 2.10.0
Was ok in 2.9.6
Screenshots:
The text was updated successfully, but these errors were encountered: