Slackbot
02/21/2024, 6:22 AMMarvin
02/21/2024, 6:22 AMFlow Runsresourceful-eagle Failed Scheduled for 2024/02/21 075959 AM None None Flow Metrics Deployment performance-test Work Pool petko Work Queue default • LogsTask RunsSubflow RunsResultsArtifactsDetailsParameters ```Feb 21st, 2024 INFO Worker 'DockerWorker 55853481-f9f8-4722-80c0-085695d03262' submitting flow run 'cb0b9543-cd33-432c-b8c5-1b0005f26230' 080009 AM prefect.flow_runs.worker INFO Completed submission of flow run 'cb0b954
Marvin
02/21/2024, 6:23 AMAn error occurred while monitoring flow run 'cb0b9543-cd33-432c-b8c5-1b0005f26230'. The flow run will not be marked as failed, but an issue may have occurred.Traceback (most recent call last): File "/usr/local/lib/python3.10/dist-packages/prefect/workers/base.py", line 896, in _submit_run_and_capture_errors result = await self.run( File "/usr/local/lib/python3.10/dist-packages/prefect_docker/worker.py", line 417, in run container = await run_sync_in_worker_thread( File "/usr/local/lib/python3.10/dist-packages/prefect/utilities/asyncutils.py", line 95, in run_sync_in_worker_thread return await anyio.to_thread.run_sync( File "/usr/local/lib/python3.10/dist-packages/anyio/to_thread.py", line 33, in run_sync return await get_asynclib().run_sync_in_worker_thread( File "/usr/local/lib/python3.10/dist-packages/anyio/_backends/_asyncio.py", line 877, in run_sync_in_worker_thread return await future File "/usr/local/lib/python3.10/dist-packages/anyio/_backends/_asyncio.py", line 807, in run result = context
Marvin
02/21/2024, 6:24 AM/opt/prefect/performance_evaluation_entry_point.py
you're trying to access does not exist, or the path specified is incorrect. This error message is a Python FileNotFoundError
, indicating that the program was unable to find the file at the given location. Here's what you can do:
- Check the path to ensure it is correct.
- Ensure the file exists at the specified location.
- If you're running this within a Docker container or a similar environment, make sure the file is included in the build context or is accessible within the container's filesystem.
Unfortunately, a search in the GitHub issues did not yield any relevant results, implying your issue may not have been reported or discussed there. If you believe this is a unique issue or an error specific to your setup, consider reaching out for support directly through Prefect's channels or filing a new issue if necessary.