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
Starting a batch job (POST /jobs/{}/results request) can take some time. E.g on VITO backend it can sometimes take tens of seconds sometimes even more, depending on the load of our cluster/scheduler. While we should improve this response time, we will probably not be able to reduce this drastically to below 1 second for example.
In this context, the "start batch job" button in the web editor does not seem to work: you press it an nothing seems to happen. There is a progress indicator in the lower left that is spinning, but it's not obvious that this is related with pressing the start button.
I think it would be good that the "start button" (and maybe other buttons too) change state in some way to better indicate that a (a potentially long) request is ongoing: e.g change color, change icon to a progress indicator, ...
The text was updated successfully, but these errors were encountered:
Yes, I saw this issue with the VITO backend, too. That made me implement the spinner that you have mentioned.
We may improve the Button behavior at some point, but this has low priority right now.
Starting a batch job (
POST /jobs/{}/results
request) can take some time. E.g on VITO backend it can sometimes take tens of seconds sometimes even more, depending on the load of our cluster/scheduler. While we should improve this response time, we will probably not be able to reduce this drastically to below 1 second for example.In this context, the "start batch job" button in the web editor does not seem to work: you press it an nothing seems to happen. There is a progress indicator in the lower left that is spinning, but it's not obvious that this is related with pressing the start button.
I think it would be good that the "start button" (and maybe other buttons too) change state in some way to better indicate that a (a potentially long) request is ongoing: e.g change color, change icon to a progress indicator, ...
The text was updated successfully, but these errors were encountered: