Open mjlbach opened 10 months ago
Also happens with other git repos, e.g. git+https://github.com/luca-medeiros/lang-segment-anything.git
Of note, this and https://github.com/conda/conda-lock/issues/395 are the only blockers for using conda-lock for my project.
@maresb This is an old issue so hoping to bring it up, I ran into the same issue. It seems that when parsing environment.yml
, the #
is not handled correctly and gets treated as part of the repository name.
Thanks @anuraaga for the info, and I'm sorry you're having problems with conda-lock.
It seems that when parsing
environment.yml
, the#
is not handled correctly and gets treated as part of the repository name.
Would you be able to explain in more detail exactly what you mean by this comment? Thanks!
Ah sorry it wasn't clear. PIP supports parameters for vcs dependencies past #
https://pip.pypa.io/en/stable/cli/pip_install/#vcs-support
For example
python -m pip install -e 'git+https://git.repo/some_repo.git#egg=subdir&subdirectory=subdir_path' # install a python package from a repo subdirectory
But we are from the error message that it seems git clone is being executed with the contents of #
which should not be part of the clone command, the final line of the original post
File "/home/michael/.local/pipx/venvs/conda-lock/lib/python3.10/site-packages/conda_lock/_vendor/poetry/utils/_compat.py", line 217, in run
raise CalledProcessError(
conda_lock._vendor.poetry.utils._compat.CalledProcessError: Command '['git', 'clone', '--recurse-submodules', '--', 'https://github.com/NVlabs/tiny-cuda-nn/#subdirectory=bindings/torch', '/tmp/pypoetry-git-torchc39fhmwj']' returned non-zero exit status 128
I can confirm having similar behavior when trying to use #subdirectory
with a similar dependency
Thanks a lot @anuraaga for the detailed explanation!
The error seems to be occurring within the old version of Poetry that I vendored into conda-lock. I suspect that upgrading this vendored Poetry would resolve the issue. I have been meaning to tackle this for some time now. I hope to be able to finally get to it in early 2024, but there are no promises.
Checklist
What happened?
If you try to
conda-lock
the following environment:environment.yml
conda-lock --mamba -p linux-64
You will receive the following error:
Conda Info
Conda Config
Conda list