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
{{ message }}
This repository has been archived by the owner on Sep 7, 2023. It is now read-only.
Currently there is no way to test in advance if a UI command is going to reach the processor successfully, without actually performing an action that has some meaning. If Redis runs fine and the UI and Processor connect to it without errors, it's very unlikely that something goes wrong. However, it feels quite uncomfortable that the first command you realistically send from the UI is the "Start" command, and at that moment you really don't want any surprises with Redis or the Processor. A test command button enables testing this long before the start of the run.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently there is no way to test in advance if a UI command is going to reach the processor successfully, without actually performing an action that has some meaning. If Redis runs fine and the UI and Processor connect to it without errors, it's very unlikely that something goes wrong. However, it feels quite uncomfortable that the first command you realistically send from the UI is the "Start" command, and at that moment you really don't want any surprises with Redis or the Processor. A test command button enables testing this long before the start of the run.
The text was updated successfully, but these errors were encountered: