Hi team, I would like to ask for urgent help, please. Suddenly gRPC doesn't work . I am getting this error and the app is blocked. (I am using windows; I think Dagster hates Windows OS. I have never got these RPC issues using Linux)

are you able to run the command directly from that error message?

Yeah, this error is very common on windows machines. I run the command in a different terminal but it doesn't return anything.

Can you provide any more context about when this error occurs? Is it on initial launch of dagit? On repository reload?

@alex sure, thank you!. This error appears usually when I re run the entire system (Dagit and Daemon). Reload also show the same issue

The

grpc

command should not return immediately if the server starts successfully, I am not surprised the second command fails since the server is no longer running if the process exited. Whatever is going wrong must be cause the server process to exit unexpectedly.

why are you using dynamic port only in windows system

windows does not support using the file system as a socket, so we have to use a network port

Hi @alex we found if we drop the heartbeat flag to start the server, the server works. What is the meaning heartbeat flag?

cc @daniel

dagit periodically calls out to the gRPC server in a background thread - if dagit goes down, the heartbeats stop, and the server stops too

Hi @daniel I am not sure. I just hardcode heartbeat and heartbeat-timeout with FALSE. Now works!