Repository navigation
no such option: --root-user-action #853
Description
Activity
+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
(found it spontaneously)
upd. For example, switch from broken 3.8.10 to 3.8.18 solves the issue.Reacted by argbrandonGood eye @KodiaqQ , looks like this is the breaking PR for those versions actions/python-versions#259
Reacted by Nikita MalininGood 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.
Reacted by Hyeok Kong, Jose Sanchez, argbrandon, PIrojahPerbak, Brendan Murphy, Toby, Gohar Shoukat and Daria Kolodkina@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
3.9.19version which seems unaffected. Obviously hoping that upstream will yank the broken3.9.13build so I can roll back my workaround.Reacted by Hyeok Kong, argbrandon, Mackenzie Salisbury, Anton Shutik, PIrojahPerbak and aram-eskandariHello @HKongCC
Thank you for creating this issue. We will investigate it and get back to you as soon as we have some feedback.Reacted by PIrojahPerbaki can confirm what @Rjevski already stated: upgrading from my old version of
3.9.13to3.9.19worked. Whenever this issue is resolved i will revert my project back to3.9.13.Reacted by XIE XuanDo 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.
@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.
Reacted by Gohar ShoukatHello @HKongCC ,
Could you please provide a link to a minimal reproduction of the issue/workflow steps? It would be very helpful in addressing your problem. Thank you!+1, facing same issue and looks like this actions/python-versions@29394d0 PR break it :(
Looks like the
--root-user-actionarg was added in actions/python-versions#223 (actions/python-versions@b539ede), and then it was removed for macos runners in actions/python-versions#259 (actions/python-versions@29394d0), but it is still present for the linux runners.I'm seeing this failure on ubuntu-20.04:
Version 3.8.10 was not found in the local cache Version 3.8.10 is available for downloading Download from "https://github.com/actions/python-versions/releases/download/3.8.10-8833490298/python-3.8.10-linux-20.04-x64.tar.gz" Extract downloaded archive /usr/bin/tar xz --warning=no-unknown-keyword --overwrite -C /home/runner/work/_temp/2f150651-7ec7-4a06-b868-a38da9fd2828 -f /home/runner/work/_temp/9035f184-4c44-46b2-bda5-30215c62bd33 Execute installation script Check if Python hostedtoolcache folder exist... Create Python 3.8.10 folder Copy Python binaries to hostedtoolcache folder Create additional symlinks (Required for the UsePythonVersion Azure Pipelines task and the setup-python GitHub Action) Upgrading pip... Looking in links: /tmp/tmp1b6088ml Requirement already satisfied: setuptools in /opt/hostedtoolcache/Python/3.8.10/x64/lib/python3.8/site-packages (56.0.0) Requirement already satisfied: pip in /opt/hostedtoolcache/Python/3.8.10/x64/lib/python3.8/site-packages (21.1.1) Error: Usage: /opt/hostedtoolcache/Python/3.8.10/x64/bin/python -m pip install [options] <requirement specifier> [package-index-options] ... /opt/hostedtoolcache/Python/3.8.10/x64/bin/python -m pip install [options] -r <requirements file> [package-index-options] ... /opt/hostedtoolcache/Python/3.8.10/x64/bin/python -m pip install [options] [-e] <vcs project url> ... /opt/hostedtoolcache/Python/3.8.10/x64/bin/python -m pip install [options] [-e] <local project path> ... /opt/hostedtoolcache/Python/3.8.10/x64/bin/python -m pip install [options] <archive url/path> ... no such option: --root-user-action Error: The process '/usr/bin/bash' failed with exit code 2So, this build of python 3.8.10 has pip 21.1.1, but the
--root-user-actionoption was added in pypa/pip#11035 (pypa/pip@2e1112a) which was only released in pip 22.1 and greater.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...
Where is the version of pip embedded in the python-version build defined?
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.
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 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.
Reacted by Jacob Floyd+1
With the latest build of python 3.8.10, I'm no longer seeing this issue. Thanks for fixing it @mayeut.
Reacted by Andre Borie and Pranav PatilHello Everyone, New artifacts have been generated. Please rerun the actions and let us know if you still see any issues.
Thank you @mayeut for your contribution with the PR.Reacted by Andre BorieHello Everyone, New artifacts have been generated. Please rerun the actions and let us know if you still see any issues. Thank you @mayeut for your contribution with the PR.
Works for me! Thanks for the quick fix!
Hello @HKongCC, We are closing this issue as it is fixed and confirmed by everyone.
Please feel free to reach us if you are still facing the same issue.
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