Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

I'm running into a strange bug. When I run `pants --version`, pants fails silently while running `.pants.bootstrap`. If I `bash .pants.bootstrap`, the file works. But when pants runs it, it silently exits the first time `grep` is called. Other things like `sed` work in it. It's just `grep`. It doesn't do this in every environment. It works locally most of the time but breaks in a container in CI. I'm still trying to find the root cause, but I was hoping maybe someone had some insight that might fix it.

It's something to do with the source call. I can bash out of that script and grep works. But sourcing doesn't seem to work.

maybe related to what PATH is in each case?

What happens if you replace `grep` with `/full/path/to/grep` ?

I don't have the version of code in front of me to reproduce it. I may test it more later. I ended up working around by bashing from that `.<http://pants.to|pants.bootstrap` to> then call grep and just echoed out what I needed. It probably wasn't the PATH since I did check sed and grep. Both were in the same place. But sed worked.