https://dagster.io/ logo
Title
d

Daniel Mosesson

12/28/2022, 8:26 PM
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?
d

daniel

12/28/2022, 8:27 PM
hey daniel - what version of grpcio do you have installed?
('pip freeze | grep grpcio')
d

Daniel Mosesson

12/28/2022, 8:28 PM
1.48.0 for grpcio, and 1.43 for health checking
d

daniel

12/28/2022, 8:28 PM
ah so they actually yanked that version - it was causing mysterious hangs
:blob_detective: 1
can you downgrade to 1.47.2
We have a pin in place until they fix it upstream: "grpcio>=1.32.0,<1.48.1",
d

Daniel Mosesson

12/28/2022, 8:31 PM
in both venvs or just the one where dagit is running from?
d

daniel

12/28/2022, 8:31 PM
I'd do it in both to be safe
d

Daniel Mosesson

12/28/2022, 8:40 PM
that worked
😛artydagster: 1
I may have spoke too soon 😞 Dagit is up, but only one of the workspaces loaded (no entry at all for the other)
d

daniel

12/28/2022, 8:47 PM
do they have different location names?
d

Daniel Mosesson

12/28/2022, 8:49 PM
I typo'd. I added the same workspace file twice....
been too long today
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."
d

daniel

12/28/2022, 8:49 PM
I haven't seen anybody else report that in dagster
d

Daniel Mosesson

12/28/2022, 8:50 PM
thats good at least
the last comment on that thread is not encouraging
d

daniel

12/28/2022, 8:51 PM
agreed