/area operator

Ops are not loving the idea of giving dapr-operator cluster-admin permissions. Is this really necessary and if so, what is it necessary for (i.e. what operations does it have to do where more restrictive permissions would not suffice)?

Thanks!

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

Use-Case

Support client certificate authentication for Metrics API scaler

Reference

kedacore/keda#929

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?

Right now, we can provide a timeout while calling an endpoint of a remote service. However, this means we need to change the client-side code that is consuming the remote service in order to change this timeout.

How can we solve it?

Let's add the timeout field (time in seconds) in the configuration of each endpoint in remote service. This field s

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

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.

Is your feature request related to a problem? Please describe.
cloneDirectory needs to be specified like https://github.com/argoproj/argo-events/blob/master/examples/sensors/trigger-source-git.yaml#L34, otherwise it will error out.

Describe the solution you'd like
If cloneDirectory is missing, use a temp dir to do it.

Describe alternatives you've considered
A clear and con