-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Container warns if permission is denied #2270
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
Codecov Report
@@ Coverage Diff @@
## dev #2270 +/- ##
=======================================
Coverage 73.11% 73.11%
=======================================
Files 77 77
Lines 8432 8432
=======================================
Hits 6165 6165
Misses 2267 2267
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why wouldn't you want it to fail? If it is not reachable it will not work, so linting should fail IMO
Currently, all these linting tests are failing because of 403: nf-core/modules#3344 |
Alternatively, rather than just a blanket
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks :)
We were just talking with @ewels and he had more opinions about warning vs failing, this test should fail even if it's due to permissions, but maybe he wants to add something else :) |
I'm not sure about making auth errors a warning instead of failure. This tool is primarily for use with public nf-core pipelines and as such, all modules in nf-core/modules should not require authentication. Granted, people outside nf-core use our tools, but typically we say that the default behaviour should be matched to what we want and users can then disabled tests or set a config option to change that behaviour. Looking through the failing tests we now have here, all failing tests seem to be real errors, all to do with using |
ok, got it. |
Interesting, |
Yup! After a bit of googling I finally dug that out. Full URL is actually |
We should at least improve the error message - I'll update to be an error. Perhaps having a way of changing an error to warning via config be valuable. |
When we add |
I sneaked these changes into this PR 🙂 |
Thanks @adamrtalbot 👍🏻 Yes if you would like the extra config it definitely wouldn't be a bad thing. There is precedent for how this can work in the config yaml etc. elsewhere, happy to dig it out if you'd like. Totally agree that the error message needs improving 👍🏻 (just printing the container name is a good start!) |
I've reset to just an error plus an fstring for better error messages. |
Replace container failed with a warning if error code indicates the container is unauthorised rather than doesn't exist etc. We could extend this in future for relevant codes.
PR checklist
CHANGELOG.md
is updateddocs
is updated