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
no such option: --root-user-action #853
Comments
+1 seeing similar issue on v2 and v4 |
+1 same |
Try to change to Python versions older than 12h ago in actions - https://github.com/actions/python-versions/releases |
Good eye @KodiaqQ , looks like this is the breaking PR for those versions actions/python-versions#259 |
Yeah. We've found this PR earlier than a solution with a version switch. |
Same on v5 |
Does anyone know if there will be a new release or something similar to fix? Using a different python version isn't an option for most production builds without going through an upgrade process. 🤔 thinking through alternatives here. the pinned version should prevent this fwiw. |
@HKongCC had a quick look and doesn't seem like that's the case unfortunately - I don't see any parameter here that would allow to override it. I temporarily switched my affected projects to use |
Hello @HKongCC |
i can confirm what @Rjevski already stated: upgrading from my old version of |
Do we have an ETA on this? Moving Production builds to a newer version is not quite as straightforward! |
@goharShoukat you could look into using PyEnv in the meantime? A bit of manual work but should be doable if it's time-critical. |
How do you mean? PyEnv would only let me switch versions of Python but the code and other packages need to be appropriately adjusted if I switch over to a different python version. |
@goharShoukat I meant use PyEnv to install 3.9.13 instead of using the GH Actions' broken build. Effectively remove your "setup-python" action and just install & call pyenv like you would on any other Linux machine. |
Hello @HKongCC , |
+1, facing same issue and looks like this actions/python-versions@29394d0 PR break it :( |
Looks like the I'm seeing this failure on ubuntu-20.04:
So, this build of python 3.8.10 has pip 21.1.1, but the Where is the version of pip embedded in the python-version build defined? Either the python build needs a newer version of pip, or the linux script needs to use the env var similar to the macos fix. |
I only expected missing macOS arm64 versions to be added when opening actions/python-versions#259 It seems that rather than adding the missing platform, every platform was rebuilt and published...
The initial version comes from the python sources/binaries (built or fetched depending on OS/platform). It's tightly coupled to the version of python.
I do have a PR on the way to fix that on every platform, it will need the maintainers to approve it & rebuild everything once again. |
+1 |
With the latest build of python 3.8.10, I'm no longer seeing this issue. Thanks for fixing it @mayeut. |
Hello Everyone, New artifacts have been generated. Please rerun the actions and let us know if you still see any issues. |
Works for me! Thanks for the quick fix! |
Description:
Unable to setup-python@v4. Fails on downloading pip packages, was working yesterday, but the same workflow fails today.
Update: Also appears that yesterday it successfully upgraded pip to 24.0 so it had the --root-user-action argument available, but today the upgrade isn't happening and stays on 22.0.4 properly so the --root-user-action argument is throwing an error.
Action version:
setup-python@v4
Platform:
Runner type:
Tools version:
Python 3.9.13
Repro steps:
Use actions/setup-python@v4, with python version 3.9.13, and x64 architecture
Expected behavior:
Setup python successfully
Actual behavior:
Fails on pip install with the following message
no such option: --root-user-action
The text was updated successfully, but these errors were encountered: