Mike Dame

@RonFed yeah, that's what I'm saying is that gRPC should always return the error's concrete type as a [`Status`](https://github.com/grpc/grpc-go/blob/2da976983bbb33feb3e25b7daaa8f60b9769adb5/internal/status/status.go#L43) struct. Because I think it's expected that you can use the...

Awesome, thanks! I'll try to follow that and implement it for grpc

@oxeye-gal thanks for looking into it, the fact that gorilla has its own span on top of the net/http is weird to me too. I believe it uses net/http under...

reviving this topic, is there any opposition to a proposal for how to address this? I am willing to put something together for the spec

If I update my go version, I could just re-run offsets-tracker right? Or if I'm building for a container I could make the generator part of my build pipeline so...

If I am generating the offsets, won't I need to recompile the automatic instrumentation anyway? Or does the automatic instrumentation just read from the file at runtime? (sorry if this...

Hi @sr185436, thanks for opening this. We do plan to add a .NET sample, so this is on our radar.

This is still open to anyone who wants to add it, but triaged as p3

(note for reference: I based this on the cloudbuild.yaml from https://codelabs.developers.google.com/codelabs/cloud-builder-gke-continuous-deploy in https://github.com/GoogleCloudPlatform/software-delivery-workshop/blob/main/labs/gke-progression/build/branch-cloudbuild.yaml.tmpl)

Update: figured out permissions/IAM issues from earlier runs. But I don't think Cloud Build has the functionality to do this the way I was thinking, specifically: 1. Step to install...