#22691 Could the sandboxer socket path be shorter? Issue created by ferdinandyb Is your feature request related to a problem? Please describe. I often run into the

IntrinsicError: materialize_directory() request to sandboxer process failed: transport error

error. As far as I understand this is on OS limitation, that the socket path must fit into 108 bytes or something like this. But the thing is, I have a long username and I like using worktrees with jira ticket names, so it's very easy to fill this up. Describe the solution you'd like So this is what we have now:

/Users/bence.ferdinandy/signifyd_github/data-science-CML-668-fix-unit-test-generation-for-generate-matched/.pants.d/workdir/sandboxer/sandboxer.sock

One thing pants could do is keep it in

.pants.d

but make it shorter, like much shorter, maybe

.pants.d/sb.sock

. Another (imho even better) solution would be to have the socket in

/tmp/pants/[someshorthashpantsknows]/sandboxer.sock

which would make the issue agnostic from how deeply nested one's development library is. Describe alternatives you've considered I generally end up using

--no-sandboxer

. pantsbuild/pants