The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

I'm running into an issue where:

• `dagit -w workspace.yaml` works
• `dagit -w ../other/folder/workspace.yaml` works
but `dagit -w worspace.yaml -w ../other/folder/workspace.yaml`hangs after starting the code server for the first package

Doesn't matter which order I put them in, both workspaces have only one python package specified (with attendant executable paths). Same issue if I try putting the workspaces together. No additional logs show up when I add `--log-level trace`

Any idea what could be going on?

hey daniel - what version of grpcio do you have installed?

1.48.0 for grpcio, and 1.43 for health checking

ah so they actually yanked that version - it was causing mysterious hangs

We have a pin in place until they fix it upstream: "grpcio&gt;=1.32.0,&lt;1.48.1",

<https://github.com/grpc/grpc/issues/30843>

in both venvs or just the one where dagit is running from?

I may have spoke too soon :disappointed:
Dagit is up, but only one of the workspaces loaded (no entry at all for the other)

I typo'd. I added the same workspace file twice....

how concerned should I be about "EDIT I'm seeing this issue as far back as 1.46.0+, <https://github.com/grpc/grpc/releases/tag/v1.46.0>."

I haven't seen anybody else report that in dagster

the last comment on that thread is not encouraging