Travis Cline

this is still present on k8s 1.4.6 on GKE

I ran into this again on an upgrade.

Thanks for the responses. To clarify, we're generating protos using the java code in the repository but and the things I'm after in terms of go support are the validation...

AFAICT that code doesn't work today with new Go types generated from profiles (e.g. won't be in the list of possible oneofs for ContainedResource). Is that true?

> ContainedResource behavior is governed by the `PackageInfo#contained_resource` oneof: https://github.com/google/fhir/blob/master/proto/profile_config.proto#L26 > If you set `local_contained_resource` to `true`, it will generate a new ContainedResource to use throughout the profile. Make sure...

Is it my imagination or did it not used to be as smart with unused transitive dependencies?

I'd still like to find ways to keep the number of dependencies low and want to explore this more -- we could perhaps analyze what is bringing in the most...

I'm experimenting with what having modules under ./contrib would look like here: https://github.com/tmc/langchaingo/tree/add-contrib

Yeah, I’m thinking we could do some CI automation around go.work files. Another option would be something that would auto-tag pre-release tags or branches so that pushes to branches would...

You could sketch out a proposal if you'd like.