Skip to content

Conversation

@chrisnovakovic
Copy link
Contributor

argv[0] might look like a relative path without actually existing relative to the current working directory - this is the case if (e.g.) the .pex file has been copied into a directory in PATH and the shell's PATH search behaviour is being relied upon to locate the .pex file. Get the canonical path to argv[0] before attempting to open it and read the preamble configuration within it.

`argv[0]` might look like a relative path without actually existing
relative to the current working directory - this is the case if (e.g.)
the .pex file has been copied into a directory in `PATH` and the shell's
`PATH` search behaviour is being relied upon to locate the .pex file.
Get the canonical path to `argv[0]` before attempting to open it and
read the preamble configuration within it.
@chrisnovakovic chrisnovakovic merged commit fe6ff98 into please-build:master Dec 4, 2025
155 of 158 checks passed
@chrisnovakovic chrisnovakovic deleted the preamble-no-argv0 branch December 4, 2025 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants