https://pantsbuild.org/ logo
Join Slack
Powered by
I'm getting this error after merging in `main` to ...
# development
f
I'm getting this error after merging in 
main
to a PR of mine: (log excerpts below)
Copy code
10:04:48.13 [INFO] Completed: Building 7 requirements for pants_release.pex from the 3rdparty/python/user_reqs.lock resolve: PyYAML<7.0,>=6.0, ansicolors==1.1.8, packaging==21.3, toml==0.10.2, types-PyYAML==6.0.3, types-toml==0.10... (27 characters truncated)
pants.engine.process.ProcessExecutionFailure: Process 'Building 7 requirements for pants_release.pex from the 3rdparty/python/user_reqs.lock resolve: PyYAML<7.0,>=6.0, ansicolors==1.1.8, packaging==21.3, toml==0.10.2, types-PyYAML==6.0.3, types-toml==0.10.8, typing-extensions~=4.12' failed with exit code 1.
ValueError: '24.2' of type <class 'str'> must be one of '20.3.4-patched', '22.2.2', '22.3', '22.3.1', '23.0', '23.0.1', '23.1', '23.1.1', '23.1.2', '23.2', '23.3.1', '23.3.2', '24.0', '24.1', '24.1.1', '24.1.2'
@happy-kitchen-89482: Any connection to the pex upgrade in https://github.com/pantsbuild/pants/pull/21317?
Reverting that commit fixes the issue.
(I was running 
./pants run src/python/pants_release/generate_github_workflows.py
)
w
is the error coming from scie-pants? Or pants pants
24.2 was added in pex 2.13ish - so I'd be surprised if that broke it
f
How do I tell?
w
Ah, I missed the 'generate-github-workflows' part
f
I have the full traceback. Let me dig.
It's coming from `pex`: Last line of the traceback is:
Copy code
File "/home/tdyas/.cache/pants/named_caches/pex_root/installed_wheels/4ac043f6e398ed2e72f0ef0a0b2623903fd887c349bf0a6a73d87d98dcf63417/pex-2.11.0-py2.py3-none-any.whl/pex/resolve/lockfile/json_codec.py", line 143, in parse_enum_value
w
pex-2.11?
Well, that would be a problem
f
that code is higher up in the call stack and is enforcing pip versions
(3 weeks ago)
maybe we need to upgrade pex again?
w
It looks like we're using 2.16.2 and 24.2 in the 
main
branch though, already - that's the latest
As of 8 hours ago
f
and pex v2.16.2 has the 24.2 pip enum config in it from what I can tell
but Pants is trying to run pex 2.11
w
Your pex_root up there was on 2.11 somehow
f
in the named cache dir
w
Yeah, that's the part I'm confused about - no merge conflicts?
If you wipe the cache, does it still pull that down?
f
no merge conflicts from what I can see. My PR is entirely Rust (tonic v.012 and hyper 1)
I'll wipe my named caches dir
đź‘€ 1
after wiping the directory and confirming it empty. the problem still occurs. Pants writes a new 
pex_root
directory into the named cache dir with pex 2.11.0
One guess is the pex version is not being mixed in to a cache key somewhere.
if I disable local cache, Iet's see if that helps
or do I need to kill pantsd
still fails same way with 
./pants --no-local-cache run src/python/pants_release/generate_github_workflows.py
works now that I have wiped the lmdb_store and killed my days old pantsd
should have tried them one at a time
w
Hmm, that would be crazy if pantsd was the thing
Just checked, fresh build pulls 2.16.2
h
Hmmm, that is disconcerting
but I guess is more likely related to bad caching in pants’s “from source” bootstrapping rather than in a deployed pants binary?
w
That's the vibe I'm getting - I wonder if it's because it was "just" a rust change? But I would have assumed that pantsd would have invalidated itself
f
I don't know what state my system was in exactly but erasing lmdb_store and killing pantsd "solved" the issue.
10 Views
Open in Slack
PreviousNext
Powered by