Hi I am getting following error while running ` pants packag

Question

Hi I am getting following error while running ` pants package` goal in my CI ```pex result ResultError There were 2 errors downloading required artifacts 1 setuptools 57 5 from lt urlopen error Errno 97 Address family not supported by protocol gt 2 wheel 0 37 1 from lt urlopen error Errno 97 Address family not supported by protocol gt ``` This is most likely due to restricted access but I have `indexes` not `indexes add` configured under ` python repos ` subsystem in my `pants toml` Is there anything else that I can do

fresh-cat-90827 · Answer

I d check the contents of this section This is the format I use locally ``` python repos indexes = ``` in CI we extend an env var ```PANTS PYTHON REPOS INDEXES= + $ secret my company com pypi simple ``` How does the authentication work You could perhaps verify first that you can access the private PyPI by attempting to install an arbitrary package using `pip`

bored-glass-58755 · Answer

Thank you for your response Do we need to extend the environment variable you mentioned even if `indexes` are mentioned in `pants toml` Thanks for the `pip install` suggestion I shall try that

bored-glass-58755 · Answer

Ok so I extended the env variable `PANTS PYTHON REPOS INDEXES` and it is still failing Also I tried pip installing a package and it was downloaded successfully only that it did not install because of permissions in the CI s venv The original error I reported was it was not able to even download the packages because it was trying to download it from `<https files pythonhosted org>` whereas I have mentioned the `indexes` under ` python repo ` subsystem of `pants toml`

fresh-cat-90827 · Answer

gt Do we need to extend the environment variable you mentioned even if `indexes` are mentioned in `pants toml` no you don t have to I mentioned an env var because you wouldn t normally want to store the username password as part of your Pants configuration file hence the secret collection

fresh-cat-90827 · Answer

gt Also I tried pip installing a package and it was downloaded successfully I assume you ve provided the additional index to the `pip install` command that s identical to what you have in your `pants toml`

bored-glass-58755 · Answer

Ok I don t need any username password to access the repository when I am running it thru CI

fresh-cat-90827 · Answer

okay so only need to provide the extra index URL gotcha

bored-glass-58755 · Answer

gt I assume you ve provided the additional index to the `pip install` command that s identical to what you have in your `pants toml` I didn t but I assume CI is configured to check the internal repo only by default

fresh-cat-90827 · Answer

if your CI doesn t have access the public PyPI then I assume you have all the wheels required hosted in a private one right e g `setuptools` and `wheel`

bored-glass-58755 · Answer

gt okay so only need to provide the extra index URL gotcha Yes and I have done that in `pants toml` Is there a way to see what options are in effect from `pants toml` for a particular run of pants

bored-glass-58755 · Answer

gt if your CI doesn t have access the public PyPI then I assume you have all the wheels required hosted in a private one right e g `setuptools` and `wheel` That s right

bored-glass-58755 · Answer

I am just surprised why is it going to `<https files pythonhosted org>` to download those packages

fresh-cat-90827 · Answer

indeed it shouldn t go there Do you have only a single index configured your private one

bored-glass-58755 · Answer

Yes using the `indexes` option and not `indexes add`

fresh-cat-90827 · Answer

well running with ` ldebug` would give you more information

bored-glass-58755 · Answer

Ok I just ran with ` print stacktrace` to find out which module is it fetching the public repo from I will try with ` ldebug`

fresh-cat-90827 · Answer

gt Also I tried pip installing a package and it was downloaded successfully did pip download the package from your private PyPI

bored-glass-58755 · Answer

It didn t give such info but I d assume it will download from there only The basis of my assumption is I have another CI which uses conda setup and there it provides such information as to where the package is being downloaded from I do not want to setup conda in my Pants CI

fresh-cat-90827 · Answer

you don t need conda slightly smiling face

bored-glass-58755 · Answer

Yeah

fresh-cat-90827 · Answer

gt It didn t give such info well `pip` itself needs to be configured to go to other PyPI directory e g using `pip conf` file or by passing extra command line arguments

fresh-cat-90827 · Answer

any useful information found when you run with ` ldebug`

bored-glass-58755 · Answer

Here s the stack trace ```Engine traceback in select in pants core goals package package asset in pants backend python goals setup py package python dist client ts client in pants backend python util rules dists run pep517 build in pants backend python util rules pex create venv pex build backend pex in pants backend python util rules pex build pex build backend pex in pants engine process fallible to exec result or raise Traceback most recent call last File $XDG CACHE HOME pants setup bootstrap Linux x86 64 2 12 0 py37 lib python3 7 site packages pants engine process py line 277 in fallible to exec result or raise process cleanup=process cleanup val pants engine process ProcessExecutionFailure Process Building build backend pex from setuptools default lock failed with exit code 1 ``` And a part snapshot redacted of the debug ```09 40 31 51 DEBUG Running Building build backend pex from setuptools default lock under semaphore with concurrency id 2 and concurrency 8 09 40 31 51 INFO Starting Building build backend pex from setuptools default lock 09 40 31 51 DEBUG Starting setup sandbox 09 40 31 53 DEBUG Completed setup sandbox 09 40 31 57 DEBUG spawned local process as Some 122689 for Process argv usr local python 3 7 6 bin python3 7 pex tmpdir tmp jobs 8 python path protoc 3 20 1 bin redis 6 2 5 bin bazel 4 0 0 bin golang 1 15 bin venv bin nodejs v12 bin usr local java openjdk 8u302 x64 bin root usr bin usr local ext cmake 3 17 1 bin maven 3 6 3 bin usr local ext git 2 24 0 bin usr local ext git 2 24 0 libexec git core usr local perl 5 26 1 bin sonar wrapper 6 32 bin sonar scanner 4 7 0 bin helm 3 6 1 dotnet 3 1 usr local sybase bin etc bin etc bin usr bin bin output file build backend pex no emit warnings manylinux manylinux2014 venv seed verbose venv site packages copies python usr local python 3 7 6 bin python3 7 sources directory=source files lock setuptools default lock no pypi index= index= layout packed env CPPFLAGS LANG en US UTF 8 LC ALL en US UTF 8 LDFLAGS PATH protoc 3 20 1 bin redis 6 2 5 bin bazel 4 0 0 bin golang 1 15 bin venv bin nodejs v12 bin usr local java openjdk 8u302 x64 bin root usr bin usr local ext cmake 3 17 1 bin maven 3 6 3 bin usr local ext git 2 24 0 bin usr local ext git 2 24 0 libexec git core usr local perl 5 26 1 bin sonar wrapper 6 32 bin sonar scanner 4 7 0 bin helm 3 6 1 dotnet 3 1 usr local sybase bin etc bin etc bin usr bin bin PEX IGNORE RCFILES true PEX ROOT cache pex root working directory None input digests InputDigests complete DirectoryDigest digest Digest hash Fingerprint lt 0fe2393a7ac8d77f0c987b7edd9962b1c7c9e23264ca982596b13a0c7f446830 gt size bytes 340 tree Some nailgun DirectoryDigest digest Digest hash Fingerprint lt e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 gt size bytes 0 tree Some input files DirectoryDigest digest Digest hash Fingerprint lt 0fe2393a7ac8d77f0c987b7edd9962b1c7c9e23264ca982596b13a0c7f446830 gt size bytes 340 tree Some immutable inputs use nailgun output files output directories RelativePath build backend pex timeout None execution slot variable None concurrency available 10 description Building build backend pex from setuptools default lock level Info append only caches CacheName pex root RelativePath cache pex root jdk home None platform constraint Some Linux x86 64 cache scope Successful 09 40 33 88 INFO Completed Building build backend pex from setuptools default lock 09 40 33 88 DEBUG Completed Scheduling Building build backend pex from setuptools default lock 09 40 33 90 DEBUG Completed pants backend python util rules pex build pex 09 40 33 90 DEBUG Completed `package` goal 09 40 33 90 DEBUG computed 1 nodes in 25 237837 seconds there are 945 total nodes 09 40 33 90 ERROR 1 Exception encountered ProcessExecutionFailure Process Building build backend pex from setuptools default lock failed with exit code 1 ``` One thing that concerns me in debug output is why `PEX ROOT` is set as ` cache pex root` where as I set it as `$XDG CACHE HOME pants named caches pex root` at the beginning of the CI Also the 4th line from last in debug output suggests that package goal is complete whereas according to the stack trace its not

fresh-cat-90827 · Answer

gt ``` index= index= ``` so `pex` got these arguments that s good

fresh-cat-90827 · Answer

also forgot to ask are you able to run the goal locally at all

bored-glass-58755 · Answer

Yes I was able to run the goal locally Also I have got a way to proceed from this thread here <https pantsbuild slack com archives C046T6T9U p1661957446116169 thread ts=1661952554 253599 amp cid=C046T6T9U>

fresh-cat-90827 · Answer

oh yes the lock files

bored-glass-58755 · Answer

Thank you for your help < fresh cat 90827> slightly smiling face

fresh-cat-90827 · Answer

well couldn t help much but learned a few things along the way smile good luck with the further work I ll keep an eye on your future posts