Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

can anyone point me in the right place in the engine code to look for where the actual decision to memoize or not memoize a rust `Task` happens?

i would love to know the answer to this and might try to investigate for 5 minutes

would be around this method: <https://github.com/pantsbuild/pants/blob/49e6bb805fa59807d171fc576bbf9780c92d6f74/src/rust/engine/graph/src/entry.rs#L275-L388>

but <https://github.com/pantsbuild/pants/issues/6598> is relevant. just marking a Node !cacheable isn't quite sufficient currently, because any dependents of that Node will still be cached, so that would look like a an uncacheable "hole" in the middle of the graph

dirtying to the root would be a strategy to basically say "this node is not cacheable, so everything above it needs to be considered to be dirty continuously"

right, I just wanted to get a rough idea of where in the code was the right place to look