Chris White

Thanks for sharing @johnkangw - I'm going to close this issue given there's not much we can do on the Prefect side right now, but if others run into similar...

We might be able to do something like that, but I think that's more of a use-case specific bandaid that I'd probably only want to consider if this problem is...

Yea, the only reason you'd need to do that is because you can't properly clean up the Python process - otherwise the process naturally exits. I suppose you could try...

Hi @tsafacjo if you have an idea for how to solve the issue, then yes please feel free to give it a go!

@cvetelinandreevdreamix point of clarification: are you saying that the bug only happens when you use the `RemoteFileSystem` class ```python @flow(task_runner=DaskTaskRunner(), result_storage=RemoteFileSystem.load('minio-results')) ``` but the bug doesn't occur when you use...

I see, I haven't been able to reproduce yet but one thing that does help prevent errors when using the `.load()` method on Blocks is the `_sync` kwarg: ```python @flow(task_runner=DaskTaskRunner(),...

Could you share the working directory that is being used when the deployment is run? Most likely the module you wrote is not on the path of the execution environment...

Ah I think I see one part of the confusion - @Samreay the `main` branch of the repo is being released as the release candidates for 3.0, so it's different...

Thanks for tagging me in @desertaxle - my opinion is that this feels confusing because these should be two distinct methods that return different types, not one method that returns...

I don't think we can introduce a breaking change to 2.x, especially with 3.0 coming out; if it would unblock your use case, I'd accept a new kwarg on `get`...