Ejemplo
Configuring abandon_on_cancel=False on anyio.to_thread.run_sync shields worker execution and blocks scope cancellation until the worker thread finishes, while abandon_on_cancel=True exits immediately but releases the CapacityLimiter slot before the background worker thread completes.
sha256:a14bcf1e15305a5701519193880ecabc0aab24fe04d053c597a482f66f869313
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Evidencia de ejecución
Separamos el entorno declarado de las ejecuciones firmadas para mostrar qué se demostró.
Base de evidenciaContrato firmado aprobado
Recibos de verificación1
Nivel de verificaciónL3_CONTRACT_PASS
Entorno declarado
- Contexto de ejecución
- python
- Sistema operativo
- linux
- Arquitectura
- x64
- Runtime
- python
- Lenguaje
- python
- Gestor de paquetes
- pip
Entornos de las ejecuciones de verificación
- Contexto de ejecución
- python 3.12
- Sistema operativo
- linux alpine · musl
- Arquitectura
- x64
- Runtime
- python 3.12
- Lenguaje
- python
- Gestor de paquetes
- pip
- Ejecución
- container · docker
CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · python@1 · 2026-08-17
Caso
- Objetivo
- Configuring abandon_on_cancel=False on anyio.to_thread.run_sync shields worker execution and blocks scope cancellation until the worker thread finishes, while abandon_on_cancel=True exits immediately but releases the CapacityLimiter slot before the background worker thread completes. HOW
- Paquetes
-
anyio 4.13.0
- Entorno
- python
- Creado
- 2026-08-17T11:44:01Z
Lo que suele suponerse
Cancelling a task waiting on anyio.to_thread.run_sync cancels immediately without waiting for the synchronous thread, and setting abandon_on_cancel=True keeps worker thread concurrency strictly bounded by the CapacityLimiter.
El autor de la muestra anotó aquí lo que un desarrollador o un modelo esperaría. El contrato de abajo es lo que realmente se ejecutó.
Contrato
- With abandon_on_cancel=False, cancelling the calling scope blocks until the worker thread finishes running, whereas abandon_on_cancel=True exits the scope immediately while releasing the CapacityLimiter before the synchronous thread finishes.
- assert cancel_scope.cancel_called and sync_finished, 'With abandon_on_cancel=False, cancellation must be shielded until worker thread finishes'
- assert elapsed >= 0.18, 'Scope exit was blocked waiting for synchronous thread duration'
- assert elapsed < 0.15 and not sync_finished, 'With abandon_on_cancel=True, scope exits immediately while worker thread runs in background'
- assert limiter.available_tokens == 1 and limiter.borrowed_tokens == 0, 'CapacityLimiter token is immediately released upon cancellation despite worker thread running'
- assert acquired_concurrently, 'Second task acquires limiter token concurrently with abandoned background thread'
- assert collision_caught, 'Calling run_sync while holding default limiter raises RuntimeError'
Archivos
- NOTES.md
- csx.json
- requirements.txt
- test/contract.py
Descargar el artefacto de código fuente (tar.gz)
Seeder de origen
csx-seed
Recibos de verificación
- python 3.12 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · python@1 · 2026-08-17 · ed25519:d91480838ac982c9