-
Notifications
You must be signed in to change notification settings - Fork 53
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: command not found
fix
#90
poetry: command not found
fix
#90
Conversation
ee50998
to
4e828c1
Compare
In this workflow run v1.2.0 seems to install fine: https://github.com/snok/flake8-type-checking/runs/8122396279?check_suite_focus=true So I understand, what's the difference between this run and yours? |
Given the issue - I could only imagine that your my original project (which was failing)
|
I update to use - uses: snok/install-poetry@v1
with:
virtualenvs-create: true
virtualenvs-in-project: true
version: latest in https://github.com/snok/asgi-correlation-id/runs/8123090043?check_suite_focus=true and that also seems to work fine 🤔 Just to be clear, I don't want to be difficult here, but correcting a mistake is often more costly than delaying a fix in my experience, so just want to understand exactly what we're fixing. Any ideas? Alternatively, do you have time to create a public repo to reproduce the issue? |
@sondrelg I totally understand - and also even though my fix works, I didn't grok it enough to say EXACTLY why specifying the path to poetry worked as it did. It's even possible that some other combination of fiddling fixed it. I do have a public repo that you can observe the issues I was having today -
|
We know that there are breaking changes between v1.1 and v1.2 wrt. lockfile parsing. Is it possible that rebuilding the lockfile with a local version of v1.2.0 fixed your issue? Have you seen any issues since? EDIT: You're making this very easy btw, thanks for being so thorough 👏 |
Certainly possible. Also removing Python 3.6 |
I just ran into this same issue with Python 3.10, so it doesn't seem exclusive to 3.6 after all. Will report back after testing a little. EDIT: nevermind, I specified version |
You need to set VIRTUALENVS_PATH to a path in the project if VIRTUALENVS_IN_PROJECT is true. With your failing spec you were telling it to create a virtualenv in the project and then giving it a path outside the project. So either it was creating the virtualenv in the project and then activating one outside the project that did not have poetry, or vice versa. This should work VERSION: 1.2.0
VIRTUALENVS_PATH: .venv
VIRTUALENVS_CREATE: true
VIRTUALENVS_IN_PROJECT: true
INSTALLER_PARALLEL: true |
@sondrelg - I just swapped back to your plugin, so yea, I think the other fixes I did were the solution, not this. Closing this PR |
Good insights - thank you @miigotu |
Attempting a fix for
poetry: command not found
. #89My logs were: