Hi <@U04S45AHA>, with `Upgrade to Pex 2.1.4 (#8881...
# pex
c
Hi @enough-analyst-54434, with
Upgrade to Pex 2.1.4 (#8881)
, we got this error
ERROR: Could not find plugin: future==0.17.1
or
ERROR: Could not find plugin: future==0.16.0
and we need to nuke
~/.cache/pants/plugins
to make it work. Is there a setting/flag for the workaround?
h
Does it continue to work when you nuke the cache?
(John is mostly OOO this week btw)
w
Does it continue to work when you nuke the cache?
It does appear so, but if we want to go back, the cache will stop working again. so basically the cache is neither forward nor backwards compatible.
which may be fine, if there is a workaround for us to configure ~/.cache/pants/plugins to somewhere else
c
Hi @hundreds-father-404, if it doesn’t have a workaround to configure ~/.cache/pants/plugins to somewhere else, we would like to have pants 1.26.x to use previous version of pex (2.0.3) so that it doesn’t block 1.26.x release internally, what do you think?
e
I'm looking at all this now and will report back shortly. If a fix is required, but only in Pants, is a fix-forward to be released in 1.26.0.dev2 this Friday or earlier if needed OK?
👍 1
I expect Pex 2.0.3 will have the same issue - the cache structure changed with Pex 2.x.
@wide-energy-11069
It does appear so, but if we want to go back, the cache will stop working again. so basically the cache is neither forward nor backwards compatible.
That option is
[GLOBAL] plugin_cache_dir
Copy code
$ ./pants --help-advanced 2>/dev/null | grep -A1 plugin-cache
  --plugin-cache-dir=<str> (default: '/home/jsirois/.cache/pants/plugins')
      Cache resolved plugin requirements here.
👍 1
@wide-energy-11069 & @careful-area-84205 - So an upgrade that includes that option changed can roll forward and back safely IIUC. I'd still like to fix the underlying issue for 1.26.0.dev2 but please confirm that option change fix unblocks you all.
w
That'll do the trick. Thanks John!
e
OK - great. You're welcome.