Closed BartNetJS closed 1 year ago
Apologies for being late looking at this. I've just tried Dapr Sidekick with the latest Dapr runtime 1.10,2 and it does look to me CheckHealthAsync()
is working. To test this I started with the standard Service Invocation Sample and made the following changes:
Dapr.AspNetCore 1.10.0
packageStartup.cs
changed services.AddControllers()
to services.AddControllers.AddDapr()
WeatherForecastController
:
[HttpGet("daprHealth")]
public async Task<bool> CheckDaprHealth([FromServices] DaprClient daprClient, CancellationToken cancellationToken) =>
await daprClient.CheckHealthAsync(cancellationToken);
With only those changes in place, and Dapr 1.10.2 runtime installed, running that project in Visual Studio 2022 and navigating to http://localhost:5000/weatherforecast/daprHealth returns true
while daprd
is running, and false
temporarily if I kill daprd
manually until Sidekick restarts it. Can you please try this out and let me know if you still have the problem?
As for this item:
The same issue with dashboard that is able to discover dapr services started with
daprd
? That is due to the dashboard looking for Dapr CLI processes (i.e.dapr.exe
) which is typically used to launchdaprd
. As Sidekick does not use the CLI, its manageddaprd
instances do not show up in the dashboard.
I figured it out when working on the sample for this question https://github.com/man-group/dapr-sidekick-dotnet/issues/51 Thanks!
Closing as completed
When execute client.CheckHealthAsync() it return false when running with dapr sidekick When i run it with dapr run ... it returns true.
Also the same with WaitForSidecarAsync, it works with dapr run, but not with the dapr sidekick.
Any idea why? Is it because daprd is not discovered? The same issue with dashboard that is able to discover dapr services started with daprd?