Hi everyone! I’m currently trying to install pants onto my mac through “brew install pantsbuild/tap/pants” which runs successfully. When I try any pants command after though I’m met with the following response. What could be the reason?

That looks like it could be permissions issues perhaps. 🤔

The SSL error at the top of that screenshot seems relevant.

When I run this code on the same machine and network i receive a 200 response

Are you able to

brew install

other things? And as tdyas asked, can you

curl

it? Normally this would imply some sort of ssl error, which is generally outside the reach of us

Sorry for the delay, yes I am able to brew install other things and I was able to establish connection to that url via curl

Hi Pants team, we were able to make it work by downloading a previous version of pants binary using the formula from here. The giveaway was the part of the documentation where it talks about scie-pants having its own interpreter and the fact that this version was working on my machine under the same corporate setup. Maybe the packed interpreter is not respecting CA certs from the machine or from

pants.toml

? Worth taking a look?

Which "previous version" did you install, and what was the installed version that was problematic?

The version 0.12.0 binary was having a problem (I think that’s the latest) and the “previous version” that we installed is 0.11.0 (linked the homebrew formula file above). Older versions e.g. 0.8.2 that some of the other teammates are using are working fine too. So it’s not about a specific version that works but about a specific version that doesn’t work which, to me, seems to be 0.12.0.

@curved-television-6568 @broad-processor-92400 Anything that might have changed? 2.16 on the latest

pants

works fine for me, but I have an ARM mac

We have a mixture of Apple & Intel Macs and it was failing on both.

https://github.com/pantsbuild/scie-pants/compare/v0.11.0...v0.12.0 🤷 Updated pex and switched to

ureq

- not sure if there is some other TLS stuff we should be doing https://github.com/algesten/ureq

Sorry for the trouble. If you haven’t found these possibilities for workarounds already: • you can install a specific version of the scie-pants builder using

get-pants.sh --version 0.11.0

or similar (script from https://www.pantsbuild.org/2.21/docs/getting-started/installing-pants) • You can override the urls that scie-pants uses to find artefacts, if you have an internal artefact store https://github.com/pantsbuild/scie-pants?tab=readme-ov-file#firewall-support I’ll have to look at the specific problem in more detail later, though.

@broad-processor-92400 thanks for the inputs. We installed a specific version by first downloading the

.rb

file (linked in my message above) and then running

brew install <location-of-downloaded-rb-file>

. That should be ok, right? Can we have a behavior where one could install thru

brew install pants@version

? Regarding overriding URLs for

scie-pants

, that’s very useful to know. Thank you. However, the problem that we were facing was that pants was unable to download the

pex

file to bootstrap. We were able to download the same file on the same computer and network thru

requests.get()

. So, to me it looks like a pants issue and not certs or URL issue. Please correct me if that understanding is not right.

Yes, I'm always on the latest versions. So, on mac, WSL for windows, and my linux box are all running pants 12 right now

Sorry but I asked which Python version did you test it with?

Oh, ha! I transposed the two. I use anywhere from 3.9 to 3.12 depending on the project

However, the problem that we were facing was that pants was unable to download the

pex

file to bootstrap

Given the error message is talking about a self signed certificate and failing, I imagine it’s something about the network setup the blocks the installer from validating the security of the connection when attempting to download the

pex

file for bootstrapping. Overriding these urls may mean that you can sidestep this connection issue by letting you fully control where they come from.

• scie-pants 0.11.0: Pants 2.16 installed from PyPI

• scie-pants 0.12.0: Pants 2.16 installed by downloading from GitHub releases

Wow, good spot. I didn't see that at all.

All good: I reviewed that change (and made the ureq one), so I had more background for guessing what's relevant and what's not 😅

For cert issues this may be relevant: https://github.com/pantsbuild/scie-pants/issues/403

> Given the error message is talking about a self signed certificate and failing, I imagine it’s something about the network setup the blocks the installer from validating the security of the connection when attempting to download the

pex

file for bootstrapping. > Overriding these urls may mean that you can sidestep this connection issue by letting you fully control where they come from. Even though we were able to download the

pex

from the same URL through Python requests from the same terminal window where

pants

was failing? Just trying to understand the details. I am not aware what could be an alternate URL to download

pex

to bootstrap

Yeah, Python on the terminal may be reading different certificates etc, so the terminal Python is using the correct network configuration while the scie-pants one does not.

May I ask for updates on this? Can we expect an update to resolve this? Another teammate had to downgrade from

0.12.0

to

0.11.0

today to bootstrap.

I don’t know of any updates other than what’s in this thread and the issue linked above. Pants is entirely volunteer driven. Are you or your teammates in a position to do any debugging and/or fixing?

Thank you. I’d really love to contribute but: 1. I’d need help in finishing the developer setup for Pants. I had attempted this in the past but other things took priority 😞 2. I’d prefer to do this from my personal computer and there’s no way I could reproduce the issue there since it’s not under the same corporate proxy.

Ah, okay. Re 1, I think this is in the scie-pants repository, which has less fiddle to get running, I think