v0.1.4 includes several performance improvements, bug fixes, and feature refinements. Check out the release notes here for more details, and upgrade via your preferred package manager here.
I have a theory about why this is occurring, and I am going to file a ticket for our engineers.
I think in the short term you could use a more explicit invocation : . <( flox activate -e default; ); which should tell flox that you are trying to activate the default environment “global” to the user, as opposed to a project.
I suspect this crash occurs when you open a shell inside of a git repository, so it’s trying to locate a “project environment” in that tree.
Gotcha. This sounds like a bug to me, I think what we ought to do is get flox to fall back to globally defined envs if a project doesn’t contain an environment.
I am confused about whyits attempting to search for project environments when you aren’t in a git repo but our engineers will look into it