-
-
Notifications
You must be signed in to change notification settings - Fork 292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected distribution hash #1683
Comments
Confirmed this works on pants 2.11.0.dev1 / PEX 2.1.67, prior to #1630 |
Ok, so this is the case of new Pex trying to add requirements from an old PEX. That old PEX is coming from the Pants local LMDB cache; so the problem can be worked around by either clearing that - a very heavy hammer, or tweaking something about the My fix on the Pex end will make this new / old combination work, but if you need to move on with your life before this gets rolled out through to a Pants release; those workarounds are available. |
Hrm, diagnosis and workarounds above are untrue. I think this is a pure new Pex / new PEX issue. |
The switch from sha1 to sha256 hashes in pex-tool#1661 did not cover this feature. Simplify and use the existing machinery to get at a PEX's distributions. Fixes pex-tool#1683
I expect this to be a pex issue, if not I'll re-open in pants.
When running
./pants package
for apex_binary
target with a dependency on apython_distribution
(i.e. a local dist scenario) I get this error:Running with verbose pex output, I see it's using a cached install for the wheel:
The
local_dists.pex
has one distribution in it:Looking at the cached wheel vs the unzipped
.whl
from the sandbox, there's one file difference:This
.layout.json
file:Where
x
andy
are redacted data.This is for a fresh repo, so there's practically no code in it, yet, so if a reproduction repo is desirable it shouldn't be too difficult to setup.
I suspect it is the
.layout.json
that trips up the dist hash, but I'm not sure of what the fix needs to be.Any details I've left out that would be helpful, let me know :)
The text was updated successfully, but these errors were encountered: