Emil Christensen

Just wanted to chime in with a simple reproduction. Run the script below, kick off a run, and then cancel that run. You'll see that the parent flow goes to...

@zhen0 I suspect these are different since in #14013 the keyboard error is in fact handled (though incorrectly) but in this case nothing happens.

@seanpwlms I can't reproduce this with the latest version, but it does look like nothing actually happens which is what's documented in #15647. ``` Version: 3.0.10 API version: 0.8.4 Python...

This error is resolved in https://github.com/encode/httpcore/pull/899 as of version 1.0.5.

Also discovered that `ecs:TagResource` is necessary.

@tetracionist There's more context in #15740, but for now, making your function `async` will achieve the desired behavior: ```py import asyncio from prefect import flow from prefect_dbt.cli.commands import run_dbt_build @flow(name="dbt...

In cases where the flow author does not have direct access to the infrastructure, this becomes a point of friction. For example, the flow author might be a data scientist...

My understanding is that these are errors that happen in the Runner. Errors that happen while provisioning infrastructure are captured in worker logs, and errors that happen in the context...

In addition to import errors I believe this would also happen with syntax errors. Suppose you create a deployment using git storage. After creating the deployment, you commit and push...

Another example that reproduces this (I believe): ```py import multiprocessing as mp from prefect import flow def _task(i): pass @flow def main(): with mp.Pool(5) as pool: pool.map(_task, range(5)) if __name__...