Solved this myself: It turns out the GitHub CLI is required. After installing it and running gh auth login, I was able to run flox activate without issues
Thank you for your feedback and subsequent updates! Looking into this further, is it possible you were logged into the gh client with an invalid token when you first started using flox? I ask as we support running with no github token, and hence running flox activate shouldn’t have given you that error message. Would you be able to help us reproduce the problem so we can find/address the bug?
Hi there! I tried to reproduce with a fresh install on a Mac VM, but I didn’t get the error:
floxfan@floxfans-Virtual-Machine ~ % flox --version
Version: 0.0.7-r92
floxfan@floxfans-Virtual-Machine ~ % flox activate
Updating /Users/floxfan/.config/flox/nix.conf
Updating /Users/floxfan/.config/flox/gitconfig
flox collects basic usage metrics in order to improve the user experience,
including a record of the subcommand invoked along with a unique token.
It does not collect any personal information.
Do you consent to the collection of basic usage metrics? (Y/n) n
Understood. If you change your mind you can change your election
at any time with the following command: flox config --reset
flox [default] floxfan@floxfans-Virtual-Machine ~ % flox install hello
created generation 1
flox [default] floxfan@floxfans-Virtual-Machine ~ % which hello
/Users/floxfan/.local/share/flox/environments/local/default/bin/hello
Any chance you have some other pre-existing git config that might be messing with authentication?
It is entirely possible! I’m not sure what it would be, though. I don’t do anything super-weird, but I do authenticate to GitHub with SSH instead of HTTPS, so maybe it’s related to that? Here’s the output of git config --list:
hmmmm, as we cannot recreate the issue and this is the only time this issue has been reported so far, I think it best to wrap up this thread but definitely keep it in mind in the event we get a similar report. Would that be ok with you @glassblowerscat ?
We use insteadof to inject credentials, so there’s a chance those could be conflicting. It looks like longest match is respected though, so I’m not sure why the one you have would be taking precedence. I am curious though if removing that from your git config would be another workaround