Loading page...
Q&A
Q&ARelease owned resources in cleanup and normally propagate cancellation after cleanup.
Cancellation is delivered at an await point. Use finally blocks or async context managers to close resources, then re-raise CancelledError unless there is a deliberate reason to suppress it. A blocking synchronous call may not respond promptly, so keep the event loop cooperative and bound background work.
python
9 minUnderstand task cancellation, timeout scopes, cleanup, and the failure modes that leave background work running.
typescript
5 minKeep request handlers responsive by distinguishing asynchronous waiting from CPU work, bounding concurrency, and propagating stream failures.
python
8 minUnderstand structured task lifetimes, cancellation, and grouped failures in asyncio.
typescript
8 minUse for-await consumption, cancellation, and iterator return semantics without hiding queues.
python
17 minUnderstand event-loop scheduling, CPU versus I/O concurrency, ASGI worker lifecycles, per-request sessions, and cancellation-safe background work.
Q&A
Q&ANo; an adapter can hide an unbounded push queue behind a pull-shaped interface.
A consumer can request one item at a time, but callback-backed sources still need an explicit capacity and overflow policy. Tie early iterator exit and cancellation to resource cleanup.
Q&A
Q&AIt cancels unfinished siblings, waits for cleanup, and surfaces failures as a group.
Child cancellation is cooperative, so cleanup must run and cancellation should normally be re-raised. A task group scopes lifetimes; it does not roll back remote effects or make partial success a business policy.