What is wrong with dagit failing to start the grpc server? It worked previously. So far, I cannot pinpoint the reason. I am using dagster 1.1.10 on Windows

\dagster\_core\workspace\context.py:584: UserWarning: Error loading repository location data_mundus:Exception: gRPC server exited with return code 0 while starting up with the command: "\envs\data_mundus\python.exe -m dagster api grpc --lazy-load-user-code --port 59824 --heartbeat --heartbeat-timeout 45 --fixed-server-id a0ee3aa0-d6c0-4242-8b96-3b9b635ebe79 --log-level INFO --inject-env-vars-from-instance --instance-ref {"__class__": "InstanceRef", "compute_logs_data": {"__class__": "ConfigurableClassData", "class_name": "LocalComputeLogManager", "config_yaml": "base_dir: C:\\dagster_home\\storage\n", "module_name": "dagster.core.storage.local_compute_log_manager"}, "custom_instance_class_data": null, "event_storage_data": {"__class__": "ConfigurableClassData", "class_name": "SqliteEventLogStorage", "config_yaml": "base_dir: C:\\dagster_home\\history\\runs\\\n", "module_name": "dagster.core.storage.event_log"}, "local_artifact_storage_data": {"__class__": "ConfigurableClassData", "class_name": "LocalArtifactStorage", "config_yaml": "base_dir: C:\\dagster_home\n", "module_name": "dagster.core.storage.root"}, "run_coordinator_data": {"__class__": "ConfigurableClassData", "class_name": "DefaultRunCoordinator", "config_yaml": "{}\n", "module_name": "dagster.core.run_coordinator"}, "run_launcher_data": {"__class__": "ConfigurableClassData", "class_name": "DefaultRunLauncher", "config_yaml": "{}\n", "module_name": "dagster"}, "run_storage_data": {"__class__": "ConfigurableClassData", "class_name": "SqliteRunStorage", "config_yaml": "base_dir: C:\\dagster_home\\history\\\n", "module_name": "dagster.core.storage.runs"}, "schedule_storage_data": {"__class__": "ConfigurableClassData", "class_name": "SqliteScheduleStorage", "config_yaml": "base_dir: C:\\dagster_home\\schedules\n", "module_name": "dagster.core.storage.schedules"}, "scheduler_data": {"__class__": "ConfigurableClassData", "class_name": "DagsterDaemonScheduler", "config_yaml": "{}\n", "module_name": "dagster.core.scheduler"}, "secrets_loader_data": null, "settings": {"telemetry": {"enabled": false}}, "storage_data": {"__class__": "ConfigurableClassData", "class_name": "DagsterSqliteStorage", "config_yaml": "base_dir: C:\\dagster_home\n", "module_name": "dagster.core.storage.sqlite_storage"}} --location-name data_mundus -m data_mundus -d C:\Users\heilerg\development\projects\datascience\data-mundus"

Stack Trace:
  File "\dagster\_core\host_representation\grpc_server_registry.py", line 219, in _get_grpc_endpoint
    server_process = GrpcServerProcess(
  File "\dagster\_grpc\server.py", line 1183, in __init__
    self.server_process, self.port = _open_server_process_on_dynamic_port(
  File "\dagster\_grpc\server.py", line 1119, in _open_server_process_on_dynamic_port
    server_process = open_server_process(
  File "\dagster\_grpc\server.py", line 1091, in open_server_process
    wait_for_grpc_server(server_process, client, subprocess_args, timeout=startup_timeout)
  File "\dagster\_grpc\server.py", line 1025, in wait_for_grpc_server
    raise Exception(

  warnings.warn(
\dagster\_core\execution\compute_logs.py:48: UserWarning: WARNING: Compute log capture is disabled for the current environment. Set the environment variable `PYTHONLEGACYWINDOWSSTDIO` to enable.

Hey Georg - if you run the command it tried to run yourself (without the long instance-ref arg), does the server stay running or does it exit?

It must be this - 1.1.9 is still starting just fine

Let me know if you get a chance to run that command, that might help explain why it’s exiting

you mean >= ? I thought you are enforcing this already. Let me try

No ==

Understood. let me try -- it will take a while as conda is so slow