Akshay Shah

We'll be tagging a release of https://github.com/bufbuild/connect-opentelemetry-go in a few days, so I'm going to close this issue. Sorry for the many, many delays everyone!

And, as a final update: https://buf.build/blog/connect-opentelemetry-go/

I agree that release binaries would be nice, even if they're unnecessary for people using the `buf` CLI. @emcfarlane Can we look into integrating GoReleaser in this repo?

There's nothing that `connect-go` can do to accelerate this, so I'm going to close this issue: * When `net/http` supports HTTP/3, `connect-go` will automatically support the new protocol. * The...

I'm broadly in favor of this. It's unfortunate that interceptors can't solve all these use cases, but it's difficult to make them reasonable for low-level, byte-oriented use cases _and_ high-level,...

Connect returns `INVALID_ARGUMENT` in some cases. `FAILED_PRECONDITION` is only used in a test. I'm _very reluctantly_ okay with changing our use of `INVALID_ARGUMENT` to `INTERNAL` and `UNAVAILABLE`, matching gRPC. It...

Mangled payloads can just as easily come from the _client's_ RPC runtime. I've never seen a REST server treat a mangled JSON request payload as a 5xx - it seems...

@jhump and @mattrobenolt Curious about your thoughts on this one.

Hi @pontaoski! We've discussed this extensively internally. Websockets are definitely better supported in some environments, but they have their own drawbacks too. We'll have a more detailed proposal (with some...

@mattrobenolt - for sure. Middleware is most attractive if we want this to be an optional add-on that's mostly for browser-to-backend communication. Having it built-in is maybe better (if it's...