Fix action button behavior

[jbeisen]

Enable the button even if an action is in progress.

[mwylde]

I don't think this is quite the right change. There are some states that are interruptible, and some that aren't, and all of this (including which action you can take) is meant to be determined by the server and sent back via the action_ properties.

That logic was here:

arroyo/arroyo-api/src/jobs.rs

Line 152 in c58db37

let (action_text, action, in_progress) = match (state.as_ref(), running_desired) {

You can see for example this line:

arroyo/arroyo-api/src/jobs.rs

Line 159 in c58db37

("Scheduling", true) => ("Stop", Some(Checkpoint), InProgress),

which is supposed to allow you to stop a scheduling job. It returns Some(Checkpoint) for the action, so it shouldn't be null.

[jbeisen]

Yeah, I didn't change that logic in the API, just moved it into a function so it could be used by both the rest api and grpc api. But in 9c5de6e I added a condition to the console that disabled the button if an action is in progress, which I shouldn't have done.

[mwylde]

Makes sense!