Users get confused by spinning status

[chrisvanrun]

An observation form the case study: 'A workshop dry-run'. They seem to call it a problem on GC, and refreshing sometimes helps.

Perhaps we should remove the spinner, or actually make it auto-update?

[amickan]

Which spinner are you referring to here?

[jmsmkn]

Refreshing always helps as you get the correct state when the page loads, but only when the page loads as the page not button does not auto-refresh.

We have a way of doing this now - make the component job status button a HTMX component. Would need the correct permissions etc. @koopmant I think this would be a nice thing for you to do for Algorithm and Evaluation tasks after you are done with the new page edit views.

[chrisvanrun]

Which spinner are you referring to here?

Several. Non-exhaustive list on the top of my head (Edit: also from the top of my hat🎩 ):

• Several job states
• Container Image states

User in this case was referring to the job states.

[amickan]

That would be very nice to get before the workshop on November 7.