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

updating poetry dependencies #64

Merged
merged 4 commits into from
May 24, 2024
Merged

updating poetry dependencies #64

merged 4 commits into from
May 24, 2024

Conversation

scarrazza
Copy link
Member

Updates poetry by including the latest qibo release.

@scarrazza scarrazza added this to the QiboTN 0.0.2 milestone May 23, 2024
pyproject.toml Outdated Show resolved Hide resolved
Co-authored-by: Alessandro Candido <candido.ale@gmail.com>
@liweintu
Copy link
Contributor

If I delete poetry.lock first and then do poetry install, it'll pass.

But if I directly use the poetry.lock file, it will hit the following error, just like those in the CI checks.

pyproject.toml changed significantly since poetry.lock was last generated. Run `poetry lock [--no-update]` to fix the lock file.

Any suggestion on the workaround that we can silence this and let CI checks pass?

@alecandido
Copy link
Member

alecandido commented May 24, 2024

But if I directly use the poetry.lock file, it will hit the following error, just like those in the CI checks.

pyproject.toml changed significantly since poetry.lock was last generated. Run `poetry lock [--no-update]` to fix the lock file.

Any suggestion on the workaround that we can silence this and let CI checks pass?

Just do exactly what the CI (i.e. Poetry) is telling you to do: run poetry lock [--no-update] to fix the lock file :)

@scarrazza scarrazza merged commit abb0e36 into main May 24, 2024
7 checks passed
@scarrazza scarrazza deleted the uppoetry branch May 24, 2024 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants