Closed GitHK closed 1 month ago
Attention: Patch coverage is 46.29630%
with 29 lines
in your changes are missing coverage. Please review.
Project coverage is 70.2%. Comparing base (
cafbf96
) to head (b77c261
). Report is 247 commits behind head on master.
Very nice! I see how we can apply this to many use-cases. Maybe @wvangeit is interested as well.
So @GitHK. the requirements to use this feature are (please correct me if this is wrong):
- a service has to be dynamic
correct both legacy and new style work
- in the DB, we need to set which inputs are required. Could you maybe add a screenshot that shows that to the PR description?
OM will add an UI element for this a PR will follow
One question, I assume that if there is a file from a previous run of the study present, it will pass the test and run the service?
One question, I assume that if there is a file from a previous run of the study present, it will pass the test and run the service?
Correct. this only checks for the port connections and the presence of a file in the port. It cannot do more that this (like inspecting if a file changes) that requires the sidecar to be running (a.k.a. the service to be running)
@GitHK Ok, makes sense. (@elisabettai so for my use case I can't use it yet, because I need to make sure I get 'fresh' files (i.e. with handshakes))
in your PR I see that the error message shows the port key not the port displayed name. Can this not be done otherwise? How as a user will I instantly recognize which port is missing?
So the data is coming from the workbench. I'm not sure exactly how to fetch some more information inside the webserver. I would need to pull the data of all the services that are connecting to my node in order to properly format these messages.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.1% Duplication on New Code
What do these changes do?
Changes
Users warning messages
Case 1 (input link to port is missing)
Case 2 (file in input port not present)
Related issue/s
How to test
Dev-ops checklist