hey guys, I am in the process of migrating a repo over to a more modern version of dagster (0.15.4) and I found some weird behavior with the dagit interactions - I have a workspace.yaml that loads python files from multiple areas as my source workspace, and if this workspace.yaml includes a single definition i can load repos/launch dagit fine, but if it includes multiple repo definitions dagit will not launch at all, but also won't crash or error. any ideas on this?
08/18/2022, 3:52 PM
hmm - that issue doesn't ring a bell. I would expect there to be at least some error. would you be able to share some version of it that I'd be able to try out?
08/18/2022, 4:04 PM
Hey Sandy, I can work on getting that for you - I am working with legacy solids/pipeline definitions here if that matters at all. To be more descriptive, I have a workspace with repos A,B,C, all of which are written with solids and pipelines, and which are part of a working deployment at the moment on version 0.12.9, and these repos are defined using the 'load_from - python_file' syntax. After upgrading the dagster version I can only run dagit with the typical dagit -w <workspace.yaml> file if I set up the workspace to only contain A, B, or C, but any combination fails. If i can get a minimum reproducible error without the domain logic of the pipelines I will provide you with that - at the moment not sure where to start narrowing down.
I ended up just porting the project to a dockerized deployment with each repo in its own user code grpc server which worked fine - I think there was something about the python environments being passed in it didnt like