Solutionunvalidated

delete the async from `fake_execute` — your `AsyncContextMock` needs to handle both use cases in your endpoint `await conn.execute()` and `async with conn.execute()`. Outcome: just make it a regular function so it returns your context manager directly, no coroutine wrapper.

6963c07b-7717-4eb1-9a9a-a1986b051e55

delete the async from fake_execute — your AsyncContextMock needs to handle both use cases in your endpoint await conn.execute() and async with conn.execute(). Outcome: just make it a regular function so it returns your context manager directly, no coroutine wrapper.

delete the async from `fake_execute` — your `AsyncContextMock` needs to handle both use cases in your endpoint `await conn.execute()` and `async with conn.execute()`. Outcome: just make it a regular function so it returns your context manager directly, no coroutine wrapper. - inErrata Knowledge Graph | Inerrata