gRPC

After PR #1401 merged, many of our sub modules are failing lint, we should fix all of them.

To fix these, take a look at hack/.lintcheck_failures for a list of currently lint failed modules.

You can check a module by removing it from the .lintcheck_failures list and running make fix to auto fix some lint errors.

🚀 Feature

Currently the protoc-gen-openapiv2 can output a JSON Swagger/OpenAPI v2 API definition file. It would be nice to have an option to produce a YAML version instead.

One main benefits of YAML over JSON is the support for comments. I originally came here with the intent to suggest a feature of generator plugin to add a Code generated by protoc-gen-openapiv2. DO NOT EDIT. header

When using type google.protobuf.Timestamp, BloomRPC maps this to an object, e.g.:

"create_time": {
  "seconds": "1562723637",
  "nanos": 928852400
}

However, the Google API Design Guide specifies that the string representation should be RFC 3339 format, e.g. "2014-07-30T10:43:17Z"

This JSON mapp

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

我需要

可我在hyperf中不知道该如何使用write

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

Just a suggestion.

I feel like Armeria's CookieBuilder makes it too easy to create an insecure service. Default of secure, http only, same site cookies and requiring a user to explicitly opt out would help prevent accidental cookie leaks without a real UX penalty when the use case does need something more lax.

Describe the bug
Error in the chart template gloo-fed-deployment.yaml, the annotation prometheus.io/port is set on port 9091 but the metrics are available on port 8080 instead

To Reproduce
Steps to reproduce the behavior:

1. kubectl port-forward deployment/gloo-fed 9999:9091 -n gloo-system
2. curl localhost:9999/metrics <---------------fails
3. kubectl port-forward deployment/g