event-driven

In what area(s)?

/area actor runtime

What version of Dapr?

v1.6

Expected Behavior

See this doc issues that was raised dapr/docs#2184

This is to add more detail to the error message when you try to save and actor and the statestore has not been configured for actors. It would be good to provide and indic

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

Azure Functions provides a way to load trigger configuration values from an environment variable using an app setting binding expression (i.e. %syntax%) KEDA currently requires some values to be read from an environment variable / secret (e.g. connection strings), b

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

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.