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

Pants

What is the per-capita (actual total pants users as the basis) clean-all is not enough per week for you all?

we had a problem with `pex` today that required a delete of `~/.cache/pants` to fix

Bug reports are super awesome if you have a few minutes to capture backtraces

it was just failing to find linux versions of 3rd party dependencies, after zapping that it worked fine

ty - any data for things like this is gold

I was chatting with <@U06A03HV1> and it sounds like <@U051221NF> has a script that captures a lot of data from .pants.d, etc.  Does anyone know where that is?  Also would people mind if something like this was optionally invoked with clean-all so we preserve the data and unblock the user?

In general we have no failure / clean-all -&gt; "pill" support

IE a hash that id's the event and can be used post facto to post a bug report

<@U07A47275>: I believe that’s the Reproducer?

<https://github.com/pantsbuild/pants/blob/master/src/python/pants/bin/repro.py>

would someone mind assigning this to me? <https://github.com/pantsbuild/pants/issues/2501>

fwiw, you can control the ~/.pex thing via PEX_ROOT env var

but you could easily set that in the pants script

yeah, I looked at the pants wrapper script we are doing some things with the pex_root env variable.

<@U053H6LQS>: is it a diff script than: <https://github.com/pantsbuild/pants/blob/master/src/python/pants/bin/repro.py>

```[illuminati source (master)]$ grep -i pex_root pants
[illuminati source (master)]$```