Skip to content

save code now: Simplify the request status update computation

Antoine R. Dumont requested to merge generated-differential-D5896-source into generated-differential-D5896-target

This tries to maximize the use of the visit status to determine the save code now request final status (succeeded or failed). When such data is not yet available, the task is probably not yet scheduled, scheduled or currently running. So, it fallbacks to use the scheduler task/task_run to deduce such non-final status (e.g scheduled/running/not yet scheduled/...).

Computing the save code now status that way will decrease the potential discrepancy [1] between the status displayed and the origin not being browsable yet.

  • [1] Most likely due to some replication lag

Related to T3378

Migrated from D5896 (view on Phabricator)

Merge request reports