Add MyMDC check_connection action
Description
MyMDC now features a check to ensure that the webservice is up and running, before sending a job request.
The motivation for this is to stop littering the job tables with timed-out requests in errors, and to provide nicer feedback to MyMDC users (rather than waiting, seeing the timeout, and exploring a bunch of logs to figure out what the issue might be).
How Has This Been Tested?
This was tested on maxwell17 with the test MyMDC installation, see the screenshots below.
Relevant Documents (optional)
In this screenshot, the webservice process was stopped.
You can see that the job request was not sent, because MyMDC could not establish that the webservice was running.
Here, however, the job request was sent (and running as can be seen at the bottom of the image), after checking that the
webservice is up and running:
Types of changes
- New feature (non-breaking change which adds functionality)
Checklist:
- My code follows the code style of this project.
- My change requires a change to the documentation.
- I have updated the documentation accordingly.
- I added tests where appropriate: as suggestions in !491