You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2024-12-06 12:06:12 ModuleNotFoundError: No module named 'common'
It happens when:
I deploy the flow to Minio. Use python deployment.py
I use a function from another module in the task I want to run with dask
If I run the flow from the local file system (python deployment.py) then it works fine
If I deploy and flow and I don't use a function imported from another module, then it works fine
My case is that I have a shared code between multiple flows and it is extracted in a shared module (common).
I can see the common folder is deployed to Minio.
P.S
The deployment of the flow to Minio doesn't work if I define the flow with the RemoteFileSystem class:
Bug summary
Hi, all,
I'm opening a new issue as it seems my comments on the closed one (#15783 ) are ignored.
I'm attaching a project you can use to reproduce the error
test-prefect-migration copy.zip
It happens when:
I deploy the flow to Minio. Use python deployment.py
I use a function from another module in the task I want to run with dask
If I run the flow from the local file system (python deployment.py) then it works fine
If I deploy and flow and I don't use a function imported from another module, then it works fine
My case is that I have a shared code between multiple flows and it is extracted in a shared module (common).
I can see the common folder is deployed to Minio.
P.S
The deployment of the flow to Minio doesn't work if I define the flow with the RemoteFileSystem class:
@flow(task_runner=DaskTaskRunner(), result_storage=RemoteFileSystem.load('minio-results'))
It works if i give just the slug
@flow(task_runner=DaskTaskRunner(), result_storage='remote-file-system/minio-results')
Let me know If you need more information. I need to migrate to prefect 3 and use the automations.
Thank you for your time!
Version info
Additional context
No response
The text was updated successfully, but these errors were encountered: