Backport #20587 to 2.19.x to fix Exec format error when running Pants on Linux
#20651
Labels
Comments
This was referenced Mar 7, 2024
Merged
|
This sounds good, thanks for requesting it! I've prepped #20653 |
huonw
added a commit
that referenced
this issue
Mar 7, 2024
Cherry pick of #20587 , which includes: - #20587 - #20502 - #20496 - #20416 - #20391 - #20149 The upgrade past https://github.com/pex-tool/pex/releases/tag/v2.1.154 is what is acutely driving this cherry-pick, as it resolves the over-long shebang issue (#20651) where the Pants `bin/pants` script can have a `#!...` line that's too long. Closes #20651 Co-authored-by: cburroughs <[email protected]>
|
#20653 is merged, so closing this. This will come out in the release in the 2.19.x series: 2.19.2rc0. |
|
Thanks for the incredibly quick turn around @huonw! |
|
This is now released in 2.19.2 stable. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When running the command
pantsseveral of my coworkers have ran intoExec format error. This is because the shebang in thence/path/.../bin/pantsis longer than the 128 character limit imposed by linux and gets cutoff.The 2.1.154 release of Pex includes a work around for this. However Pants 2.19.x currently uses v2.1.148.
During the
Pants Build Pexstep of the release, Pants packages itself as a pex, however it uses pex v2.1.148. This produces potentially broken Pants Pexs on linux if your home directory is sufficiently long.I believe if we cherry picked the work done in #20587 it would solve the problem.
Pants version
2.19
OS
Both
Additional info
The text was updated successfully, but these errors were encountered: