gRPC

Steps you follow to reproduce the error:

rpc GetArticle (GetArticleRequest) returns (GetArticleResponse) {
    option (google.api.http) = {
        get: "/v2/articles/{slug}"
        additional_bindings: {
            get: "/v2/articles/{id.hex}"
        }
     };
}

message GetArticleRequest {
    oneof article_id {
        insider.protobuf.ObjectID id = 1;
        string 

Allow to close tabs by hovering over a tab and clicking the middle mouse button.
Just like in web browsers. :)

On contexts with many APIs and APIs calling other APIs in chains, having too many spans in the zipkin/jaeger dashboards may lead to a too complex usage of such dashboards and of not necessary big data volumes.

For Tyk's admin team, the steps representing the time spent in each Tyk middleware are much valuable.

But the upstream APIs teams just want to know the global time spent in Tyk interna

Before you submit this issue, you has been search all existed issues and search the documentation

• [] I've been search all existed issues
• [] I've been read all documentation

Describe your question

How should I use alicloud MNS?

As we all know golang has give us the feature that convert proto to json with https://github.com/golang/protobuf/blob/master/jsonpb/encode.go ,and with encode.go ,we can define diffrent style like casesensitive , emit empty , json indent and so on , we can see [Customizing Protobuf JSON Serialization in Go](https://seb-nyberg.medi

Users need a shutdown hook to close a server. The pattern is fairly often used in the Armeria examples.
https://github.com/line/armeria/blob/10f1d3c1e5d3cac6402bc7d1dc9f8d86a96e5857/examples/static-files/src/main/java/example/armeria/server/files/Main.java#L20-L23
We can add a shortcut method for automatically closing a server or a client.

server.closeOnShutDown()
server.closeOnShutDo

Version

1.10.x (beta)

Is your feature request related to a problem? Please describe.

We have customer requests to expose the following HCM properties:

• headers_with_underscores_action
• max_requests_per_connection

It sounds like they are now available on the go-control-plane version we use.

EDIT: additional note: https://www.envoyproxy.io/docs/envoy/latest/api-v3/ex