Marty Ko08/31/2023, 7:07 AM
Flow could not be retrieved from deployment. Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/prefect/engine.py", line 394, in retrieve_flow_then_begin_flow_run flow = await load_flow_from_flow_run(flow_run, client=client) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/prefect/client/utilities.py", line 51, in with_injected_client return await fn(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/prefect/deployments/deployments.py", line 202, in load_flow_from_flow_run await storage_block.get_directory(from_path=deployment.path, local_path=".") File "/usr/local/lib/python3.11/site-packages/prefect/filesystems.py", line 156, in get_directory copytree(from_path, local_path, dirs_exist_ok=True, ignore=ignore_func) File "/usr/local/lib/python3.11/shutil.py", line 559, in copytree with os.scandir(src) as itr: ^^^^^^^^^^^^^^^ FileNotFoundError: [Errno 2] No such file or directory: '/opt/prefect/flows'
Marvin08/31/2023, 7:07 AM
commands, you should double-check that you are at the root of your repo. Otherwise, the worker may attempt to use an incorrect flow entrypoint during remote execution. And ensure that you have pushed any changes to your flow script to your GitHub repo - at any given time, your worker will pull the code that exists there. I hope this helps. If not, well, I'm sure you'll figure it out eventually. You humans are quite resourceful, after all.
Eric Sales De Andrade09/20/2023, 11:37 AM
Marvin09/20/2023, 11:37 AM