sci pants caching question in CI I think I am caching the co

Question

sci pants caching question in CI I think I am caching the correct folders but I it keeps downloading pants instead of using the local version did directories change am I caching the wrong folders

polite-garden-50641 · Answer

as an anecdote this steps takes 38seconds which as much as it takes to run the check and lint goals in some CI runs since those are populated by the remote cache

enough-analyst-54434 · Answer

Keeps as in a re run does it again Or keeps as in ~frequentlyish Each new scie pants release you apparently update to latest on every CI run will invalidate `~ cache nce`

enough-analyst-54434 · Answer

If you pass ` version` to the script you could be pinning scie pants and not suffering from the latter except when you choose to upgrade scie pants deliberately

enough-analyst-54434 · Answer

If it s the former though that sounds buggy and is unexpected

polite-garden-50641 · Answer

so the cache key is based one the pants version we basically read it from pants toml and use that to generate the CI cache key

enough-analyst-54434 · Answer

I m saying scie pants has its own version

enough-analyst-54434 · Answer

You re always yanking latest

enough-analyst-54434 · Answer

That invalidates the cache chooses a new subdir based on the sha256 of scie pants itself

polite-garden-50641 · Answer

because I am running the `pantsup sh` right so that causes the invalidation of pants itself

polite-garden-50641 · Answer

ok so I can just not run this script if there is a binary in `~ bin`

enough-analyst-54434 · Answer

For a given latest version of scie pants when you invoke `pantsup sh` without specifying a scie pants version that does this + downloads latest scie pants + forms a cache dir at `~ cache nce lt sha256 of the scie pants binary gt ` + looks under that last dir for a cached version of Pants X Y Z and installs it if missing

enough-analyst-54434 · Answer

Thus any scie pants not pants bump invalidates the cache

enough-analyst-54434 · Answer

You can run the script and pass ` version` that would do it

enough-analyst-54434 · Answer

It would keep scie pants its sha256 stable

enough-analyst-54434 · Answer

But again this all presumes frequentlyish vs on a re run Can you confirm which this is Does a re run miss the cache or no

polite-garden-50641 · Answer

so if I ran pantsup sh with the ` version` flag and the binary is already in the `~ bin` directory I expect the script to be a no op but as far as I can tell it downloads the `scie pants` binary regardless

polite-garden-50641 · Answer

is this the intended behavior

polite-garden-50641 · Answer

I don t see anywhere in the script something that checks if the launcher is already there with the correct version and avoids downloading it

polite-garden-50641 · Answer

so I might need to still conditionally run the script

enough-analyst-54434 · Answer

I believe it s intended behavior You might fix it though

polite-garden-50641 · Answer

how would I check the version of the binary in `~ bin` just running it w any flag just passes it to pants so not sure how to detect check for a version of the binary itself

polite-garden-50641 · Answer

in CI I can probably get away w conditionally running the script but it feels like a hack