Can't use adhoc_tool with workspace

[mnowotnik]

Describe the bug
Attempts to run a target with adhoc_tool with environment="__local_workspace__" crash.

Error:

python3.9: can't open file '/Users/michalnowotnik/Projects/pants-poc/./pex': [Errno 2] No such file or directory

Pants version
2.24.0.rc0

OS
Just checked MacOS.

Additional info
Minimal example: https://github.com/mnowotnik/pants-poc

[cburroughs]

Thanks for the detailed bug report and example repo! Is there prior version of Pants this example does work with?

[mnowotnik]

From 2.22.0 (when workspace was introduced) to 2.23.1 it gives error:

and for 2.24.0.rc0 and 2.25.0.dev3 it gives error:

python3.9: can't open file '/Users/michalnowotnik/Projects/pants-poc/./pex': [Errno 2] No such file or directory

So effectively no regression, just different error.

[mnowotnik]

find_interpreter from pex.py appears to be running in non-sandboxed environment for some reason. Strange, because it's not actually running the code, but only calculating python exec hash.
Without __local_environment__ it runs in sandbox with the following files:

❯ ls -a  /private/var/folders/tf/7pgqpxt9281gc29h16pt78380000gp/T/pants-sandbox-VSk5zW
.				..				.cache				.python-build-standalone	.tmp				__run.sh			pex

[tdyas]

I confirmed that the bug still exists with Pants v2.25.0a1.

[tdyas]

Also, the bug probably occurs because the workspace environment breaks the assumption that the materialized inputs and the working directory for the execution are the same. So any relative paths will break unless prefixed by the {chroot} marker.