Add a performance test that measures the time it takes Dapr to save data into a state store.

The important piece that is being tested is the processing that Dapr does before saving to the state store. This test should not benchmark the component itself.

For that purpose, a baseline test scenario would have an app that saves a 1kb payload to Redis, followed by a test app that uses Dapr to sav

If you want to work with a complete socket address type including port, we have a helper in SocketAddress. However, the moment you want to talk only about an IP address we force you to hold an in_addr or in_addr6 structure: hardly the friendliest versions of these data types.

We should provide a helpful wrapper IPAddress type that can be converted into those types as needed. This would

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

In order to improve code quality, we should enable more linters in the golangci tool:

• gofmt
• golint
• interfacer
• goimports
• ineffassign
• misspell
• scopelint
• structcheck
• bodyclose
• deadcode
• depguard
• dogsled
• errcheck
• funlen
• goconst
• gocritic
• gocyclo
• gosimple
• staticcheck
• [ ]

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 we use the default rolling upgrade strategy for upgrading services. It would be great if we could make it configurable.

How can we solve it?

Add a field in the service object to accept service upgrade strategy

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

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

It would be nice to have favicon for browser to distinguish it from other browser tabs.

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

Would be nice to have a wiki of examples.

When using protobuf - plumber syntax can get pretty unruly. Would be nice to provide some in-depth examples.

Maybe create an EXAMPLES.md or put examples into wiki?