Replies: 1 comment
-
|
Love the idea, I think it makes a lot of sense. Some potential other things to think about. This would be able to work in conjunction with the other timeout options? Basically an action total timeout + the last update timeout. That's what I'm getting from the proposal of it being a different item. Maybe just something that's more common in windows applications due to gui vs. terminal executable differences, but should there also be an option to watch a file for updates? ie. a log file, or theoretically even an output artifact/image? The idea being that the process is still performing work, even if we have less visibility into it outside of stdout. That would be more of a |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Many programs produce steady streams of update messages, while having highly variable total completion time. Timeouts for the whole command don't work well in this case, but a timeout for receiving any message at all from the program would reliably detect if it has stalled.
This idea is to add another timeout option to the
<Action>template schema that plays this role. It would be something like:Then a template could do this:
Beta Was this translation helpful? Give feedback.
All reactions