Alex Eagle
Alex Eagle
Rolled into #24115 at protobuf team's request.
Note that this is probably low severity, since the workaround is simply to combine the requirements with something like `all.in` containing ``` -r test.in -r runtime.txt ``` and then when...
I hit this last week also. But the error message does provide a string you can copy-paste for the package@version key in that dict. I guess a very small improvement...
This is a Bazel limitation. Nothing ever deletes from `bazel-bin`. Only `bazel clean` will remove stale output files which no rule produces anymore. However, no Bazel actions should be reading...
@gauntface thanks for posting the workaround, I'll try upstreaming that fix!
I think the resolution is just to help people discover those two flags if they don't mean to include those files in the package?
Adding some `print` debugging shows that the module extension isn't executed the way we thought. We call `npm_translate_lock` but it is non-blocking, the `module_ctx.read(attr.pnpm_lock)` later in `extensions.bzl` is already evaluated...
Got some design feedback from the Bazel team: https://bazelbuild.slack.com/archives/C014RARENH0/p1705451482052209
@thesayyn added this coverage support so probably knows it best, but is already quite overcommitted so I don't think we have someone to look into it. Based on your research...
This does seem unexpected, and it would be good for us to understand why it happens.