The "Browse save requests" panel shows various statuses for submitted save code now requests, and that great.
The gap between the last two—"scheduled" and then "succeeded"—is a bit too large and can be very puzzling for requests that takes a lot to complete.
It would be nice to have an intermediate "ongoing" status while the loader serving the given request is running.
(I've no idea if swh-web has access to the needed info, so this might need cascading to other components…)
Description
Description
Revisions and Commits
Revisions and Commits
Event Timeline
Comment Actions
In fact, the "ongoing" task state was captured by swh-web and the save request status was displayed as "running" prior to the model migration towards origin visit statuses.
Now when creating an origin visit, the first visit status is set as "created" and not "ongoing", which is why the webapp does not report the "running" status anymore.
Hopefully, the fix is on the webapp side and is easy.