Skip to content
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

conda-libmamb-solver must be installed in the environment with constructor #720

Closed
2 tasks done
moorepants opened this issue Sep 20, 2023 · 2 comments · Fixed by #738
Closed
2 tasks done

conda-libmamb-solver must be installed in the environment with constructor #720

moorepants opened this issue Sep 20, 2023 · 2 comments · Fixed by #738
Labels
locked [bot] locked due to inactivity type::bug describes erroneous operation, use severity::* to classify the type

Comments

@moorepants
Copy link

Checklist

  • I added a descriptive title
  • I searched open reports and couldn't find a duplicate

What happened?

I have the libmamba sovler set as my default solver in my base environment. The documentation says:

"The specs will be solved with the solver configured for your base conda installation, if any. Starting with conda 22.11, this behavior can be overriden with the CONDA_SOLVER environment variable."

I then created a new environment with only constructor in it (as the getting started documentation recommends) with:

conda create -n constructor constructor

but then when running constructor I get this error:

Traceback (most recent call last):
  File "/home/moorepants/miniconda/envs/constructor/bin/constructor", line 6, in <module>
    from constructor.main import main
  File "/home/moorepants/miniconda/envs/constructor/lib/python3.11/site-packages/constructor/main.py", line 17, in <module>
    from .conda_interface import SUPPORTED_PLATFORMS, cc_platform
  File "/home/moorepants/miniconda/envs/constructor/lib/python3.11/site-packages/constructor/conda_interface.py", line 61, in <module>
    _Solver = context.plugin_manager.get_cached_solver_backend()
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/moorepants/miniconda/envs/constructor/lib/python3.11/site-packages/conda/plugins/manager.py", line 197, in get_solver_backend
    raise CondaValueError(
conda.exceptions.CondaValueError: You have chosen a non-default solver backend (libmamba) but it was not recognized. Choose one of: classic

I discovered that the libmamba solver should also be installed in the constructor environment.

I suggest adding that to the documentation somewhere, i.e. that you must have constructor and conda-libmamba-solver in the same environment.

Conda Info

NA

Conda Config

NA

Conda list

NA

Additional Context

NA

@moorepants moorepants added the type::bug describes erroneous operation, use severity::* to classify the type label Sep 20, 2023
@github-project-automation github-project-automation bot moved this to 🆕 New in 🧭 Planning Sep 20, 2023
@millsks
Copy link
Contributor

millsks commented Oct 24, 2023

Ran into the same issue today.

@jaimergp
Copy link
Contributor

Since conda 23.10 depends on conda-libmamba-solver, this won't be an issue for new installs. We'll add some clarifying text in the docs, though. Thanks.

@github-project-automation github-project-automation bot moved this from 🆕 New to 🏁 Done in 🧭 Planning Dec 19, 2023
@github-actions github-actions bot added the locked [bot] locked due to inactivity label Aug 21, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity type::bug describes erroneous operation, use severity::* to classify the type
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants