Open aaymeloglu opened 3 months ago
I see this as well with just:
name: my_env
channels:
- conda-forge
dependencies:
- python
- pip
- pip:
- poetry
Running with --log-level DEBUG
, the last line it prints before hanging is always DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): pypi.org:443
. I am guessing that no timeout is being set, as described in this issue; if a lot of requests are made, one is bound to fail, and it will just wait forever.
This was fixed upstream in Poetry here: https://github.com/python-poetry/poetry/pull/5881
conda-lock
solves after adding an explicit specifier for google-api-core[grpc]
(dsub 0.4.8 specifies google-api-core>=2.7.3,<=2.11.0
):
name: myenv
channels:
- conda-forge
dependencies:
- pip=24.0
- python=3.11.8
- pip:
- dsub==0.4.8
- google-api-core[grpc]>=2.7.3,<=2.11.0
It appears that the vendored Poetry has issues handling pip package extras, and the Poetry solver infinitely loops if both google-api-core
and google-api-core[grpc]
are sub-dependencies in the dependency tree.
I haven't tested, but #613 may help.
Checklist
What happened?
When I run
conda-lock -p osx-arm64 -f environment.yml -k env
with the following environment.yml file, it hangs indefinitely.If I change the python version to 3.10.13, it completes. If I change the dsub version to 0.4.7 or earlier, it completes. 0.4.8 or later fails. If I run
conda env update -f environment.yml
(conda version24.1.2
) it builds the environment successfully.Conda Info
Conda Config
Conda list
Additional Context
No response