Stu Hood

This issue has a lot of history on it, which masks the remaining work to be done. I'm going to close it in favor of #19860, which has a more...

Yea, it would be a lot less confusing.

FWIW: it looks like this issue prevents https://github.com/python/mypy/pull/10125 from being usable.

FWIW: [Pants](https://www.pantsbuild.org/docs/jvm-overview#third-party-dependencies-and-lockfiles) uses `cs fetch --json-report-file` followed by digesting the resulting artifacts to generate a lockfile. At consume time, it uses a `cs fetch` call and a digest validation step...

Have updated the TODO list in the description with some of the (unordered) next steps. In particular: we are not yet actually using the facility introduced by #19755 to drive...

I've updated the description to include two new tasks: * Auditing the `@rule` function names that we see are widely used in plugins/our-backends to ensure that they are self-explanatory, and...

.@sureshjoshi took a huge step on this one via #20572. Huzzah! I've updated the description.

It looks like the reason that this will happen is that our first step when using a docker image is to get an expanded image ID, including its sha256: https://github.com/pantsbuild/pants/blob/4a0af5e875f2fa53dea63415b50dbcb33be96a50/src/python/pants/core/util_rules/environments.py#L848-L877...

I think that there is some missing context here: the error that you've included is for building a `docker_image` target, and `docker_image` targets don't necessarily use / rely-on `docker_environment`s. Can...

This issue is related to #1086, which discusses the differences between a constraints file and a lockfile as well. Consuming an unchanged lockfile implementation would allow for a zero-resolve "fetch...