-
Notifications
You must be signed in to change notification settings - Fork 1
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
poetry lock takes forever #46
Comments
Which version of Poetry are you using? And which branch?
❯ : poetry --version
Poetry (version 1.7.1)
❯ : poetry lock
Updating dependencies
Resolving dependencies... (13.3s)
Writing lock file EDIT: an old version of |
I'm on Poetry (version 1.8.5) The branch I am working on is not up yet -- it's still local. 45 [tool.poetry.group.docs.dependencies]
46 sphinx = "^7.2.6"
47 recommonmark = "^0.7.1"
48 sphinx-copybutton = "^0.5.2"
49 nbsphinx = "^0.9.3"
50 furo = "^2023.9.10"
51 qiskit_ibm_runtime = "^0.17"
52 qiskit_ibm_provider = "^0.11"
53 + amazon-braket-sdk = "^1.83.0" |
Apparently the problem is generated here: qibo-cloud-backends/pyproject.toml Lines 26 to 28 in d9def90
if you comment either the two Qiskit-related deps, or the Braket one, then it will lock blazing fast. I believe that the problem is (somehow) related to the (somehow) huge version space that Poetry has to take into account. Specifically, the problem seems to be fully related to ❯ : poetry --version
Poetry (version 1.8.5)
❯ : poetry lock
Updating dependencies
Resolving dependencies... (5.2)
Writing lock file What Even replacing with just |
Thank you @alecandido , let me investigate and give it a try! Appreciate your time and advice! ;) |
On my end
won't bring me through the lock generation. |
Uhm... ❯ : git diff -- pyproject.toml
pyproject.toml --- TOML
28 amazon-braket-sdk = { version = "^1.83.0", optional = true } 28 amazon-braket-sdk = { version = "^1.88.3", optional = true }
❯ : poetry lock
Updating dependencies
Resolving dependencies... (31.1s)
Writing lock file
❯ : poetry --version
Poetry (version 1.7.1)
❯ : git restore poetry.lock
❯ : poetry lock
Updating dependencies
Resolving dependencies... (7.9s)
Writing lock file
❯ : poetry --version
Poetry (version 1.8.5) Just tried, not sure what is different in your case. Maybe you could try even uncommenting those lines (but I would not expect improvements). P.S.: the apparent improvement with the Poetry version switch is almost for sure due to caching - the purpose was just to show that the timing is reasonable with both |
Ok apparently I had to run |
It seems like you're already using Poetry v2.0.0, P.S.: most likely, since it was already demanding-enough without the suitable version constraints, the |
I'm attempting to update the dependencies using
poetry lock
. However, it still doesn't write the lock file after more than 20 thousand seconds. I stopped it because it was using an increasing amount of swap memory.Then I tried
poetry cache clear --all pypi
before runningpoetry lock
again, but it still doesn't update.Is there anything we can do?
Hoping @alecandido and @scarrazza can provide some suggestions. Thank you!
The text was updated successfully, but these errors were encountered: