-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
Configuring exercism on MacOS seems broken #971
Comments
Well I've figured the parts out. TL;DR: you have to set an environment variable called In the end it doesn't matter if you have or not an existing workspace. As said above, to fix this you have to define an environment variable with an appropriate value. Then exercism recognizes your token no matter in which directory you use exercism. If you don't do this, there is a current behavior which seems a bug: it creates a So this leads to DOZENS of replications of the configuration directory, placed on each challenge directory every time you need to interact with the API. Let's see: First we destroy the env variable and configuration dir previously set here
(There is no extraneous '~' directory inside our home directory) Then we "configure" exercism
Now the bad behavior: it created a whole nested duplicated structure inside our home directory
Let's delete this structure, create the environment variable, and resolve
Then we configure exercism exactly like before (above) Then it works!
|
I'm on MacOs Mojave, and things used to work months ago when I was using this cli.
Now, it seems that, when you set an workspace, and execute
exercism troubleshoot
, it only recognizes the token when you are in the directory that you issued theexercism configure
command. See:So token was recognized ok. Now if I cd into a subdir:
Not configured!
The workaround is to call
exercism configure
inside EVERY single challenge directory, so it creates a~/.config
structure and recognizes the token, but this is broken and didn't work like that before.....Thanks for your attention.
The text was updated successfully, but these errors were encountered: