Adeel Shakir
10/14/2024, 7:46 AMMarvin
10/14/2024, 7:46 AMprefect-agent-1 | Agent started! Looking for work from queue(s): default...prefect_2_test_default-1 | 074257.405 | DEBUG | prefect.profiles - Using profile 'default' prefect_2_test_default-1 | 074257.455 | DEBUG | prefect.client - Connecting to API at http://127.0.0.1:4200/api/ prefect_2_test_default-1 | **************** prefect_2_test_default-1 | Deploying AWS BLOCKS prefect_2_test_default-1 | Traceback (most recent call last): prefect_2_test_default-1 | File "/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 72, in map_httpcore_exceptions prefect_2_test_default-1 | yield prefect_2_test_default-1 | File "/.venv/lib/python3.12/site-packages/httpx/_transports/default.py", line 377, in handle_async_request prefect_2_test_default-1 | resp = await self._pool.handle_async_request(req) prefect_2_test_default-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ prefect_2_test_default-1 | File "/.venv/lib/python3.12/site
Marvin
10/14/2024, 7:47 AMhttpx
, which is used for HTTP requests. Ensure that the httpx
and hypercorn
libraries are correctly installed and compatible with your Python version.
4. Prefect and Environment Version: Verify the Prefect version (prefect version
) and check if there are known issues with that version.
5. AWS Credentials/Configuration: When deploying AWS blocks, ensure your AWS credentials and configuration are correctly set up. If there's a discrepancy or incorrect setup, the connection and deployment could fail.
Since I need more specific details about your Prefect version and what AWS blocks you're deploying, please let me know, and I can guide you to more tailored documentation. Additionally, providing the complete error message can help in diagnosing more accurately.Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.
Powered by