phlax

i have a ~hacky workaround for this problem here https://github.com/envoyproxy/envoy/pull/19450/files#diff-41e9a812f4081144b27bc30f768b83820451109ca362e1b1ad125a04a9ffcd0bR76

also worth mentioning that we have `-e` deps in the mix, so not sure if that is relevant

from further testing this doesnt seem to be restricted to entry_points and -e doesnt seem to be a factor, so ive updated the title

cc @kfaseela who reported the issue to me

we are testing this locally, altho may take a day or two (no macs here im afraid) when i raised the bug it was failing pretty reliably on every cython...

there doesnt appear to be any difference in the `os.environ` in/outside the executor so it doesnt appear to be TTY detection

i think it may be this https://github.com/libfuse/libfuse/issues/382 altho im somewhat confused as im using a `ProcessPoolExecutor` which should theoretically banish thread problems - either way i think it has something...

possibly related https://groups.google.com/g/comp.lang.python/c/tkS3VvyLD1M

another ~related discussion https://groups.google.com/g/python-tulip/c/91NCCqV4SFs this seems to resolve, altho im not clear at all of the implications: ```python import multiprocessing multiprocessing.set_start_method('forkserver') ```

actually i think it didnt work - it instead throws an error about `A process in the process pool was terminated abruptly while the future was running or pending.`