To make it easier for tooling to interact with the Dapr control plane (examples include our own CLI, Dashboard) it's recommended we use labels to identify the control plane pods.

Kubernetes has the concept of recommended labels: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/

The following suggestion is based on the above:

Suggested labels:

app

https://github.com/apple/swift-nio/blob/a0f6a48ec0f52af49cdf8274757a2bd1ec9f3295/Sources/NIO/NonBlockingFileIO.swift#L494

After discussion with @Lukasa on Discord, it's been shown that the function should not return FileRegion as can be seen from the comments in #975. Hence, just a nit to remove FileRegion from the function docs return type.

If you are using gnet in your projects and willing to display the name of your project or corporation on the home page, please feel free to open a PR for it.

This is where I show the user cases: User cases of gnet for English, gnet 用户案例 for Chine

RabbitMQ can have many vhosts (each holding many queues)
a user might be permitted to read just some vhosts.
when one tries to use a user that can access just some vhost - one get the following messages:
error establishing rabbitmq connection: Exception (403) Reason: \"no access to this vhost\""

using url notation like specified here: https://www.rabbitmq.com/uri-spec.html (e.g. amqp://1.1

Currently, you are not able to use middleware per handler in "clean way" (you can still manually wrap the handler function, or have separated router).

It would be nice to be able to add middleware per handler.

As a good reference point, you can use chi router: https://github.com/go-chi/chi

我看到可以通过Prometheus搭建监控环境，如果有图文，更容易理解．

The problem faced currently?

Currently an end user can put any value for meta. Writing security rules to make the enforce a schema for meta is hard.

How can we solve it?

Accept a schema for the meta field. Something similar to what we did for custom events.

If you want this feature to be implemented, give it a thumbs up reaction, so that we can determine which features are important

As a followup to #696 we should deal with Ruby 2.7 deprecation warnings. Most common issue is:
Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call.

Fairly easy to fix, I suppose.

Increase code coverage for knative.dev/eventing/pkg/reconciler/source/crd

Expected Behavior

Stated goal for the V0.2 release is >70% test coverage.

Actual Behavior

Some packages do not meet this goal. See https://testgrid.knative.dev/eventing#coverage&sort-by-failures=

Expands on knative/eventing#591

/good-first-issue

Is your feature request related to a problem? Please describe.
SNS endpoint subscriptions must expose a public facing HTTP server ( unless I missed something ) and therefore make it possible for untrusted sources to post messages to the event bus as long as the message comply with basic message format.

Describe the solution you'd like
The SNS source should verify the signature of the