Quinn Klassen

Hm I don't think just attaching `ActivityContext` and `WorkflowContext` fields is sufficient since you may also want to have additional information on the client trace calls as well. I guess...

I would support generic span tag customization over adding just task queue. I am not sure any approach will really fufill the ask of this issue >allows us to infer...

The linked issue refers to `grpc_gateway` not `go-grpc-middleware` so I am not sure how this PR is related

No since the keys of the map cannot be sorted. Likely we would just copy what `Cadence` did to resolve this problem https://github.com/uber-go/cadence-client/commit/dcaec7737070ebe0889f1c9bb57c2552c8bd7d86

Hi @F1bonacc1 , There is no update on this issue. The best way to achieve similar behaviour is to create a task queue per worker. Then you assign consistent task...

I am not super familiar with bazel, but is the problem really with `github.com/grpc-ecosystem/grpc-gateway` does the same issue exist with `github.com/grpc-ecosystem/grpc-gateway/v2`? Since that is what the head of the repo...

@SpencerC I am not sure how your PR is related to this issue. Note: `grpc-gateway` is already updated to v2 on the head of the repo

Closing since the Go SDK now uses `grpc-gateway v2`

see also: https://github.com/temporalio/features/issues/261

I wonder if we should consider it an error to have unfinished workflow goroutines once the main workflow function returns?