i also don't know how to cache the result of a process execution (e.g. a generated image) in a persistent way. since this already involves pulling in

PathGlobsAndRoot

to

hackily_snapshot()

the graal

NativeTool

(which still can't be done from an

@console_rule

because it requires a

context._scheduler

) i feel like an "inverse" (ish) which writes a specific file or directory to a specified subdir of

get_pants_cachedir()

and then checks if it exists on successive runs could also be a fantastic and easy and fun way to bridge v1 and v2 tasks. i just thought of this and i think it's a great idea that will make all of this a very small amount of code. looking into that now

Does https://github.com/pantsbuild/pants/issues/6898 solve your problem?

you mentioned this to me before!!!! thank you

FWIW that ticket is less than a day’s work 🙂

i fought the borrow checker bitterly and relentlessly while in bed for two months while working on glob matching after that i became unstoppable