halspang

@tructran91 - This most likely means that the actor isn't hosted in your runtime. Is this the app that hosts the actor? 1.8 is quite old though, and no longer...

I would still recommend updating the Dapr.Actors.AspNetCore version. Generally though, this error simply means there isn't a host available for that actor. Do you see any instances of your apps...

Thanks for opening this PR, but I'm not really sure what the point of this change is. Can you provide some more background on it?

@maliming - Thanks. However, it seems like `WithTopic` would do this, right? And any additional integrations would need to come from the runtime since this is a json that we...

@DaleyKD - I believe the consumerID defaults to your app ID, but I think that's all we really have. If all you want to do is filter messages, we do...

I actually ended up doing this in https://github.com/dapr/dotnet-sdk/pull/1005.

@SoucianceEqdamRashti - You can also check to see if everything is getting loaded correctly. Dapr supports a metadata API which will give you information on the components and actors hosted...

@sicoyle - Do any other SDKs have this diagram? This feels like something better suited to the main Dapr Docs repo as all of our interactions are defined by the...

@umerkle - Generally the metadata API is only called on the local sidecar. Have you been able to call it from a remote app via the `DaprClient`?

As far as I'm aware, there is no direct reason for it not working. We just parse the attributes and add them to an endpoint collection. I'm not super familiar...