Aran Donohue

Summarizing this issue and related issues a bit. 1. There are a couple use cases discussed. Notably: Amending calls (e.g. adding options), amending responses (no concrete example above), adding additional...

Maybe I am missing something. `previous` looks optional in `InheritedProvider` and several others, and in`ProxyProviderBuilder`, which is the underlying issue. For several others, like `StreamProvider`, `FutureProvider`, there is no `update`...

Looks like it may not be easy to do in a clean way without a breaking change, because the `InheritedProvider` supertype would need to make `create` required as well, or...

I'm also trying to understand how `rules_go` is supposed to work with bzlmod + multiple interconnected go modules and I ended up here. (as well as relatedly https://github.com/bazelbuild/bazel-gazelle/issues/1715) Concretely -...

My current state is multiple `go.mod` files with no `go.work`. I'm experimenting with cutting down to one `go.mod` file for the whole repo based on your suggestion. Are you aware...

I don't have a good enough understanding of the project goals and constraints to make great suggestions. But here are a few half-baked ideas: * track which `sources` result in...

This would be really useful. Looks like Docker Engine doesn't support OCI-format multi-arch tarballs out of the box, rules_oci doesn't produce Docker-format multi-arch tarballs, and skaffold doesn't currently support alternative...

I hit a variation on this with a helm chart that had a `setValueTemplates` including: `image.tag: '{{.IMAGE_TAG_my_service}}'` when `git rev-parse --short HEAD` happened to be all-numeric. Resulting error was: `std...

Implementation note, supporting https://yaml.org/type/ might be one way. In my case, I didn't have a chance to prioritize testing if !!str was already supported and would solve this. For the...

We hit a similar-looking panic, with up-to-date toolchains_llvm and rules_go, also with a protoc plugin (`protoc-gen-go-json`), not with `force_pic`, but I think it's a separate issue. We're using Chromium project...