--monitorflag that makes it so that daprd monitors its parent service and when it detects that it goes down, it effectively restarts and waits again for the parent service to reappear.
ìnvokeAPI). But I guess I'm not the only person who wants to expose streams. Is there a workaround?
while debuging with VS Code extension i am getting
time="2020-08-25T14:22:23.6736781+03:00" level=warning msg="error establishing client to placement service: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp [::1]:50005: connectex: No connection could be made because the target machine actively refused it.\"" app_id=clientcred instance=xxxxxx scope=dapr.runtime.actor type=log ver=0.10.0
Docker hosts the placement at 6050 So i applied "placementAddress": "localhost:6050" in the tasks.json. After that the message disapered.
Hi there, sending a message to a pubsub topic results in the following error in the Dapr sidecar. time="2020-08-26T16:51:45.271826823Z" level=error msg="error from operator stream: rpc error: code = Unavailable desc = transport is closing" app_id=exampleappname instance=exampleinstancename-5bfcd46f9-f6254 scope=dapr.runtime type=log ver=0.10.0
How will I know that the pubsub component is functioning properly?