-
Notifications
You must be signed in to change notification settings - Fork 24
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
Fix/ghtoken #394
Fix/ghtoken #394
Conversation
Hi! Thanks for your contribution! Do you mind elaborating on your scenario a bit? Why would the environment contain a not valid
|
Hi! Sure: The scenario I ran into was that my It took me some time to figure that out, so added this check. I think catching this case is a good idea not to confuse users. |
Thanks for the details! In this case, I think adding an error for it is beneficial, but I wouldn't proceed with the installation. I would just return the new |
Sounds good to me 👍 |
Do you mind implementing the required changes, or you want me to supersede this PR? |
I'll take care of it in the next couple of days :) |
Awesome, thanks! There is no hurry, so do it at your own pace. |
Just a gentle ping @leongross, do you intend to work further on this PR, or should we take over? |
Currently, I am swamped with other work, so feel free to take that PR over :) |
Just created #464 based on your work, thanks! |
When the environment contains a github token (that is read automatically) which is not valid anymore, the github API request will fail, leaving the CLI with an unclear error about the version.
This PR introduces a new error type for failure when logging into the API and will use a hardcoded fallback version of a known good toolchain.
This version should be bumped regularly (Idea: maybe use dpendabot for that?)