Skip to content

Commit 28412e3

Browse files
Document non-thread-safe loop runtime error handling
Co-authored-by: Shri Sukhani <shrisukhani@users.noreply.github.com>
1 parent 1807995 commit 28412e3

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ Polling callback contracts are also validated:
147147
- Callback contract violations and callback execution failures fail fast with explicit callback-specific errors.
148148
- Reused coroutine callback errors (e.g. `cannot reuse already awaited coroutine`) are treated as non-retryable and surfaced immediately.
149149
- Iterator exhaustion callback errors (`StopIteration` / `StopAsyncIteration`) are treated as non-retryable and surfaced immediately.
150-
- Async loop contract runtime errors (e.g. `Future attached to a different loop`, `Task is bound to a different event loop`, `Event loop is closed`) are treated as non-retryable and surfaced immediately.
150+
- Async loop contract runtime errors (e.g. `Future attached to a different loop`, `Task is bound to a different event loop`, `Non-thread-safe operation invoked on an event loop other than the current one`, `Event loop is closed`) are treated as non-retryable and surfaced immediately.
151151

152152
Example:
153153

0 commit comments

Comments
 (0)