Zanie Blue
Zanie Blue
Maybe we should use the same pattern as the ECS block where wait until the task starts and do not report the task as `started` until that occurs: - https://github.com/PrefectHQ/prefect-aws/blob/8f704436c64858d7e43254ab5f8b6249eea984e3/prefect_aws/ecs.py#L465-L469...
I thought I'd have time to work on this but did not. This is open for contribution.
Failing with ```python File "/usr/local/lib/python3.7/site-packages/prefect/engine.py", line 244, in retrieve_flow_then_begin_flow_run flow_run = await client.read_flow_run(flow_run_id) File "/usr/local/lib/python3.7/site-packages/prefect/client.py", line 1483, in read_flow_run return schemas.core.FlowRun.parse_obj(response.json()) File "pydantic/main.py", line 521, in pydantic.main.BaseModel.parse_obj File "pydantic/main.py", line...
Requires #6647 or #6650 to allow extra fields from the API
Now failing with ```python 18:33:49.651 | ERROR | Flow run 'gabby-buffalo' - Flow could not be retrieved from deployment. Traceback (most recent call last): File "/usr/local/lib/python3.8/site-packages/prefect/engine.py", line 246, in retrieve_flow_then_begin_flow_run...
I'd like to add some brief tests for this as well.
Looks related to or duplicate of https://github.com/PrefectHQ/prefect/issues/6425
Can you please share the output of `pip show httpx httpcore anyio` where this flow is running?
Thanks! Does this require use of the `DaskTaskRunner` to reproduce?
Hm the healthcheck could probably be updated to remove the `fail_after` and then it'd just respect the `PREFECT_API_REQUEST_TIMEOUT` setting.