-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
On expired NEIL_GITHUB_TOKEN
, neil dep upgrade
does nothing, then terminates with exit code 0
#237
Comments
sounds good |
Perhaps a better alternative could be to print a warning, then retry without authentication. Preference, @borkdude? |
sounds good as well! |
NEIL_GITHUB_TOKEN
NEIL_GITHUB_TOKEN
, neil dep upgrade
does nothing, then terminates with exit code 0
It appears this won't work. From local testing, invalid Github token works from Github's API. The HTTP request only starts returning non-success HTTP responses after the free usage has been consumed. In other words, retrying won't help, we'll just trigger a different error; not helpful for the user. I thought of something else that further complicates the issue. With the following {:deps {babashka/pods {#_#_:local/root "/Users/borkdude/Dropbox/dev/clojure/babashka/babashka.pods"
:git/url "https://github.com/babashka/babashka.pods"
:git/sha "47e55fe5e728578ff4dbf7d2a2caf00efea87b1e"}
io.github.nextjournal/clerk {:mvn/version "0.10.560"}}
:aliases {}} Current I don't think changing this behavior to "Neil refuses to do anything because one request to Github failed" is helpful for the user. Proposed new scope:
|
Observation
When I run
neil dep upgrade
either from the command line with an expiredNEIL_GITHUB_TOKEN
, Neil prints error messages, but returns with exit code 0.Expected behavior
I would expect
neil dep upgrade
to terminate with a nonzero exit code when nothing happened due to an expired Github token.Perhaps also give a more helpful description than printing
twice, informing the user that their
NEIL_GITHUB_TOKEN
didn't appear to work.Extra details
The text was updated successfully, but these errors were encountered: