When starting a basic Dapr app, there is a lot of noise about actors in the log that potentially could scare the user, whether user is using actors or not. Allow me to illustrate with some way to sarcastic narration ;)

There is the "hey, I'm not sure if you wanted to do anything with actors, but just in case, you got none configured... well, it could that you have more than one configured so we

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

KEDA uses golint to ensure code quality. However, some files still need adjusting:

• pkg/util/gvkr.go
• pkg/util/k8sversion.go
• pkg/util/normalize_string.go
• hack/tools.go
• version/version.go

How

1. Create a new branch from v2branch
2. Remove the files from list in [.pre-commit-config.yaml](https://github.com/kedacore/ke

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搭建监控环境，如果有图文，更容易理解．

Describe the bug

Tried to setup Space Cloud with docker-compose. Ended up with an old version.
Latest version on docker hub seems to be v0.15.x

Expected behaviour

Have the newest version available

Actual behaviour

Steps to reproduce

Here is my docker-compose.yaml:

services:
  space-cloud:
    image: spaceuptech/space-cloud
    container_name: spacecl

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