event-driven

In what area(s)?

/area runtime

What version of Dapr?

All versions -- tested since 1.4.2.

Expected Behavior

The Dapr sidecar / daprd should not start when dapr-app-port and dapr-http-port are identical and return a meaningful error.

Actual Behavior

Dapr sidecar starts, but upon service invocation returns an error unrelated to the problem.

`{"errorCode":"ERR

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

Proposal

As disscuseed on kedacore/keda#2765 (comment), we should unify the functions for Status & Conditions handling. Referencing controller related stuff here is suboptimal.

There are two locations with similar functions:
https://github.com/kedacore/keda/blob/9f0ee58fc6839d74636e1ec6883fe21d82617ea3/controllers/keda/util/status.go#L30-L63
https://g

This comment says that the message ID is optional,
but for SQL transport it is a mandatory attribute,
in turn it causes misunderstanding?

Is it possible to fix it or did I get something wrong?

https://github.com/ThreeDotsLabs/watermill/blob/b9928e750ba673cf93d442db88efc04706f67388/message/message.go#L20
https://github.com/ThreeDotsLabs/watermill/blob/b9928e750ba673cf93d442db88efc04706f6

In documentation about guard there is no info that if we do not pass 'source' then guard gets data from clock.

Moreover, we can add to Docs more cases like that
https://share.effector.dev/deTs17ML

The problem faced currently?

While adding an ingress route, or a target in ingress route.
If by mistake white space gets added to the route or host. We get the error specified route not found or unable to reach the specified target

How can we solve it?

Mission control should remove the white space if present before saving the config

If you want this feature to be implemented, gi

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

Receive events from MSK with IAM auth config https://docs.aws.amazon.com/msk/latest/developerguide/iam-access-control.html

I know it's not a course about RESTful principles but maybe you'll consider in the future extracting resource id from request body to path parameter ?

https://github.com/aspnetrun/run-aspnetcore-microservices/blob/c30712aa099bc335f5613a3b196ea1e943f800a5/src/Services/Catalog/Catalog.API/Controllers/CatalogController.cs#L85

Problem

I'm getting this warning on k8s 1.23:

Warning: policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget

on

Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.0", GitCommit:"c2b5237ccd9c0f1d600d3072634ca66cefdf272f", GitTreeState:"clean", BuildDate:"2021-08-04T18:03:20Z", GoVersion:"go1.1

Search before asking

• I had searched in the issues and found no similar issues.

Enhancement Request

Clean up some useless constants and classes in the eventmesh-connector-plugin module.

Describe the solution you'd like

located in:eventmesh-connector-plugin/eventmesh-connector-rocketmq/src/main/java/org/apache/eventme

Currently, WebSocket is working for client/server side. However, the browsers do not allow to create tcp connections direclty (which is the current implementation based). Instead, the web-sys must be used.

• Use a different WebSocket implementation if the target is wasm.
• wasm example of a client.