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
There's /backend/pending-actions/ route (#1007) now, but looking at frontend routes - it isn't easy to tell which actions are running and which are just pending for worker.
So having a new state "running" would allow us to enhance /backend/pending-actions/ to provide the state as well. More info about the executed/pending action can be obtained by /backend/action/<ID>/ route (which is OK IMO).
The text was updated successfully, but these errors were encountered:
Triage time: Some actions (forking e.g.) may take a longer time, and it is painful to not recognize what actions are actually running (e.g. after executing the rawhide-to-release command). OTOH, this is going to be a big revamp of the action logic and thus expensive change.
Original issue: https://pagure.io/copr/copr/issue/1018
Opened: 2019-09-20 09:39:29
Opened by: praiskup
There's
/backend/pending-actions/
route (#1007) now, but looking at frontend routes - it isn't easy to tell which actions are running and which are just pending for worker.So having a new state "running" would allow us to enhance
/backend/pending-actions/
to provide the state as well. More info about the executed/pending action can be obtained by/backend/action/<ID>/
route (which is OK IMO).The text was updated successfully, but these errors were encountered: