cachekit 0.21.0__tar.gz → 0.22.0__tar.gz

{cachekit-0.21.0 → cachekit-0.22.0}/Cargo.lock

@@ -280,7 +280,7 @@ dependencies = [
 
 [[package]]
 name = "cachekit-rs"
-version = "0.21.0"
+version = "0.22.0"
 dependencies = [
  "cachekit-core",
  "criterion 0.8.2",

{cachekit-0.21.0 → cachekit-0.22.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cachekit
-Version: 0.21.0
+Version: 0.22.0
 Classifier: Development Status :: 4 - Beta
 Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: MIT License
@@ -28,9 +28,7 @@ Requires-Dist: psutil>=7.0.0
 Requires-Dist: blake3>=1.0.5
 Requires-Dist: msgpack>=1.2.1
 Requires-Dist: xxhash>=3.5.0
-Requires-Dist: httpx[http2]>=0.28.1
-Requires-Dist: anyio>=4.14.2
-Requires-Dist: h2>=4.4.1
+Requires-Dist: urllib3>=2.8.0
 Requires-Dist: numpy>=2.0.2 ; extra == 'data'
 Requires-Dist: pandas>=1.3.0 ; extra == 'data'
 Requires-Dist: pyarrow>=21.0.0 ; extra == 'data'
@@ -226,7 +224,6 @@ Setting `CACHEKIT_MASTER_KEY` instead of passing `master_key=` means every prese
 | Integrity Checking | - | ✅ | - | ✅ | ✅ 🔒 |
 | Encryption | - | - | - | - | ✅ Required |
 | L1 SWR (L1-only mode) | - | ✅ | - | ✅ | - |
-| L1 Invalidation | - | - | - | ✅ | ✅ |
 | Prometheus Metrics | - | -¹ | - | ✅ | ✅ |
 | Tracing | - | ✅ | - | ✅ | ✅ |
 | Structured Logging | - | ✅ | - | ✅ | ✅ |
@@ -238,6 +235,8 @@ Setting `CACHEKIT_MASTER_KEY` instead of passing `master_key=` means every prese
 >
 > **Default TTL** follows the cross-SDK [intent-preset spec](https://github.com/cachekit-io/protocol/blob/main/spec/intent-presets.md#default-ttl) (`@cache.io` 3600 s) — the same numbers as cachekit-rs and cachekit-ts. `ttl=` overrides it; `ttl=None` is the explicit never-expire opt-in ([details](docs/configuration.md#intent-presets)).
 >
+> **Cross-process L1 eviction** is not a preset feature: every preset's `invalidate_cache()` deletes from L1 and L2 alike, and evicting other processes' L1 copies is one process-wide opt-in, `CACHEKIT_INVALIDATION_LISTENER_ENABLED` ([L1 invalidation](docs/features/l1-invalidation.md#cross-process-l1-eviction)).
+>
 > **L1 SWR** (within-TTL background refresh) runs only in L1-only mode (`backend=None`) — with a backend configured it has no effect. `@cache.io` additionally ships past-TTL SWR via `stale_ttl` ([docs](docs/configuration.md#stale-while-revalidate-stale_ttl)).
 >
 > **`@cache.io()`** mirrors `@cache.production` (full reliability + observability) but routes to the managed CachekitIO SaaS backend instead of Redis. **`@cache.local()`** is a separate in-process path backed by `ObjectCache` (raw object references, entry-count LRU, no serialization) — the reliability and encryption features listed above do not apply to it.
@@ -298,6 +297,7 @@ def test_cached_function():
 
 - Circuit breaker with graceful degradation
 - Connection pooling with thread affinity (+28% throughput)
+- CachekitIO keeps idle connections pooled until the server closes them, with TCP keepalive probes, so a request after a pause skips a new TLS handshake
 - Distributed locking prevents cache stampedes
 - Pluggable backend abstraction (Redis, CachekitIO, File, Memcached, custom)
 - Untrusted-decode bounds: nesting depth and header-declared allocation are capped on every cache read (a forged entry is a bounded cache miss), verified against the protocol's shared [`decode-bounds.json`](https://github.com/cachekit-io/protocol/blob/2736a81f2f853cf08c5563c0fe7c8361331fa3ad/test-vectors/decode-bounds.json) vectors
@@ -312,7 +312,7 @@ def test_cached_function():
 | **StandardSerializer** | ★★★★☆ | General Python types, NumPy, Pandas |
 | **OrjsonSerializer** | ★★★★★ | JSON APIs (2-5x faster than stdlib) — requires `cachekit[json]` |
 | **ArrowSerializer** | ★★★★★ | Large DataFrames (6-23x faster for 10K+ rows) |
-| **EncryptionWrapper** | ★★★★☆ | Wraps any serializer with AES-256-GCM |
+| **+ Encryption** | ★★★★☆ | Any serializer above, AES-256-GCM encrypted: `@cache.secure(master_key=..., serializer=...)` |
 
 <details>
 <summary><strong>Serializer Examples</strong></summary>
@@ -451,7 +451,9 @@ free-threaded 3.14 with the GIL verified disabled (CI job
 `test-freethreaded`), and the Rust extension declares free-threaded safety
 (`gil_used = false`). Free-threaded wheels are **not yet published** and
 free-threaded builds are not officially supported — blocked upstream on
-orjson (no free-threaded wheels) and hiredis (re-enables the GIL on import). See
+orjson (no free-threaded wheels) and hiredis (re-enables the GIL on import;
+cachekit loads redis-py only for its Redis backend, and keeps hiredis out there,
+so redis-py uses its pure-Python parser). See
 [measured performance results](docs/free-threading.md#measured-performance) and the
 full concurrency audit: [docs/free-threading.md](docs/free-threading.md).
 
@@ -502,7 +504,7 @@ info = expensive_func.cache_info()
 | [Prometheus Metrics][prometheus-url] | Built-in observability |
 | [Zero-Knowledge Encryption][encryption-url] | Client-side security |
 | [Interop Mode][interop-url] | Cross-SDK cache sharing with cachekit-ts/rs |
-| [L1 Invalidation & SWR][l1-invalidation-url] | Invalidation scope (incl. cross-process whole-function on tenant-scoped Redis from the environment or `RedisBackendProvider`), stale-while-revalidate |
+| [L1 Invalidation & SWR][l1-invalidation-url] | Invalidation scope (incl. cross-process whole-function on tenant-scoped Redis from the environment or `RedisBackendProvider`), opt-in cross-process L1 eviction, stale-while-revalidate |
 | [Reference Caching][reference-caching-url] | `@cache.local()` for non-serializable objects |
 | [Rust Serialization][rust-serialization-url] | ByteStorage layer: LZ4, xxHash3, AES-256-GCM |
 | [SSRF Protection][ssrf-url] | URL allowlisting for the CachekitIO backend |

{cachekit-0.21.0 → cachekit-0.22.0}/README.md

@@ -170,7 +170,6 @@ Setting `CACHEKIT_MASTER_KEY` instead of passing `master_key=` means every prese
 | Integrity Checking | - | ✅ | - | ✅ | ✅ 🔒 |
 | Encryption | - | - | - | - | ✅ Required |
 | L1 SWR (L1-only mode) | - | ✅ | - | ✅ | - |
-| L1 Invalidation | - | - | - | ✅ | ✅ |
 | Prometheus Metrics | - | -¹ | - | ✅ | ✅ |
 | Tracing | - | ✅ | - | ✅ | ✅ |
 | Structured Logging | - | ✅ | - | ✅ | ✅ |
@@ -182,6 +181,8 @@ Setting `CACHEKIT_MASTER_KEY` instead of passing `master_key=` means every prese
 >
 > **Default TTL** follows the cross-SDK [intent-preset spec](https://github.com/cachekit-io/protocol/blob/main/spec/intent-presets.md#default-ttl) (`@cache.io` 3600 s) — the same numbers as cachekit-rs and cachekit-ts. `ttl=` overrides it; `ttl=None` is the explicit never-expire opt-in ([details](docs/configuration.md#intent-presets)).
 >
+> **Cross-process L1 eviction** is not a preset feature: every preset's `invalidate_cache()` deletes from L1 and L2 alike, and evicting other processes' L1 copies is one process-wide opt-in, `CACHEKIT_INVALIDATION_LISTENER_ENABLED` ([L1 invalidation](docs/features/l1-invalidation.md#cross-process-l1-eviction)).
+>
 > **L1 SWR** (within-TTL background refresh) runs only in L1-only mode (`backend=None`) — with a backend configured it has no effect. `@cache.io` additionally ships past-TTL SWR via `stale_ttl` ([docs](docs/configuration.md#stale-while-revalidate-stale_ttl)).
 >
 > **`@cache.io()`** mirrors `@cache.production` (full reliability + observability) but routes to the managed CachekitIO SaaS backend instead of Redis. **`@cache.local()`** is a separate in-process path backed by `ObjectCache` (raw object references, entry-count LRU, no serialization) — the reliability and encryption features listed above do not apply to it.
@@ -242,6 +243,7 @@ def test_cached_function():
 
 - Circuit breaker with graceful degradation
 - Connection pooling with thread affinity (+28% throughput)
+- CachekitIO keeps idle connections pooled until the server closes them, with TCP keepalive probes, so a request after a pause skips a new TLS handshake
 - Distributed locking prevents cache stampedes
 - Pluggable backend abstraction (Redis, CachekitIO, File, Memcached, custom)
 - Untrusted-decode bounds: nesting depth and header-declared allocation are capped on every cache read (a forged entry is a bounded cache miss), verified against the protocol's shared [`decode-bounds.json`](https://github.com/cachekit-io/protocol/blob/2736a81f2f853cf08c5563c0fe7c8361331fa3ad/test-vectors/decode-bounds.json) vectors
@@ -256,7 +258,7 @@ def test_cached_function():
 | **StandardSerializer** | ★★★★☆ | General Python types, NumPy, Pandas |
 | **OrjsonSerializer** | ★★★★★ | JSON APIs (2-5x faster than stdlib) — requires `cachekit[json]` |
 | **ArrowSerializer** | ★★★★★ | Large DataFrames (6-23x faster for 10K+ rows) |
-| **EncryptionWrapper** | ★★★★☆ | Wraps any serializer with AES-256-GCM |
+| **+ Encryption** | ★★★★☆ | Any serializer above, AES-256-GCM encrypted: `@cache.secure(master_key=..., serializer=...)` |
 
 <details>
 <summary><strong>Serializer Examples</strong></summary>
@@ -395,7 +397,9 @@ free-threaded 3.14 with the GIL verified disabled (CI job
 `test-freethreaded`), and the Rust extension declares free-threaded safety
 (`gil_used = false`). Free-threaded wheels are **not yet published** and
 free-threaded builds are not officially supported — blocked upstream on
-orjson (no free-threaded wheels) and hiredis (re-enables the GIL on import). See
+orjson (no free-threaded wheels) and hiredis (re-enables the GIL on import;
+cachekit loads redis-py only for its Redis backend, and keeps hiredis out there,
+so redis-py uses its pure-Python parser). See
 [measured performance results](docs/free-threading.md#measured-performance) and the
 full concurrency audit: [docs/free-threading.md](docs/free-threading.md).
 
@@ -446,7 +450,7 @@ info = expensive_func.cache_info()
 | [Prometheus Metrics][prometheus-url] | Built-in observability |
 | [Zero-Knowledge Encryption][encryption-url] | Client-side security |
 | [Interop Mode][interop-url] | Cross-SDK cache sharing with cachekit-ts/rs |
-| [L1 Invalidation & SWR][l1-invalidation-url] | Invalidation scope (incl. cross-process whole-function on tenant-scoped Redis from the environment or `RedisBackendProvider`), stale-while-revalidate |
+| [L1 Invalidation & SWR][l1-invalidation-url] | Invalidation scope (incl. cross-process whole-function on tenant-scoped Redis from the environment or `RedisBackendProvider`), opt-in cross-process L1 eviction, stale-while-revalidate |
 | [Reference Caching][reference-caching-url] | `@cache.local()` for non-serializable objects |
 | [Rust Serialization][rust-serialization-url] | ByteStorage layer: LZ4, xxHash3, AES-256-GCM |
 | [SSRF Protection][ssrf-url] | URL allowlisting for the CachekitIO backend |

{cachekit-0.21.0 → cachekit-0.22.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "maturin"
 
 [project]
 name = "cachekit"
-version = "0.21.0"
+version = "0.22.0"
 description = "Backend-agnostic caching for Python — intent-based decorators with circuit breaker, distributed locking, Prometheus metrics, and optional zero-knowledge AES-256-GCM encryption, on a Rust-powered core. Zero-config L1 in-memory; scales to Redis, Memcached, File, or CachekitIO."
 readme = "README.md"
 license = {text = "MIT"}
@@ -71,24 +71,10 @@ dependencies = [
     "blake3>=1.0.5",
     "msgpack>=1.2.1",
     "xxhash>=3.5.0",
-    # HTTP client for SaaS backend (cachekit.io)
-    "httpx[http2]>=0.28.1",
-    # anyio is transitive via the mandatory httpx dependency above, so it ships
-    # to EVERY install, not just dev. Declared here rather than as a
-    # [tool.uv] constraint because that table is uv-local: it never reaches
-    # requires-dist, so `pip install cachekit` would ignore it. 4.14.2 fixes
-    # GHSA-82r6-8w77-94w6 / CVE-2026-63374 (IDNA-2003 hostname encoding lets a
-    # hijacked connection to an internationalised domain pass TLS certificate
-    # validation; CVSS 9.3), GHSA-5p39-cfhj-2xmp / CVE-2026-64847 (undrained
-    # process-pool stderr pipe deadlocks the worker) and GHSA-3w57-8xmc-8v26 /
-    # CVE-2026-63349 (extra_groups ignored, parent supplementary groups kept).
-    "anyio>=4.14.2",
-    # h2 arrives via the http2 extra on that same mandatory httpx dependency, so
-    # it ships to every install too, and was declared as a [tool.uv] constraint
-    # with the same no-op effect. 4.4.1 fixes GHSA-6hr6-w5qg-qmwg (duplicate Host
-    # headers forwarded across an HTTP/2 -> HTTP/1.1 downgrade — a request
-    # smuggling primitive).
-    "h2>=4.4.1",
+    # HTTP client for the SaaS backend (cachekit.io). It has no dependencies of its own. 2.8.0 fixes
+    # GHSA-8988-9cw3-xx77 (HTTPS proxy TLS config ignored), GHSA-gh4c-6fx4-qh6g (chunked deflate
+    # infinite loop) and GHSA-vxq7-64xx-v4gw (unbounded chunk-size line buffering).
+    "urllib3>=2.8.0",
 ]
 
 [project.optional-dependencies]
@@ -238,7 +224,6 @@ test = [
     "pymemcache>=4.0.0",
     # Utilities
     "faker>=20.0.0",
-    "httpx>=0.28.1",
     "hypothesis>=6.0.0",
     "requests>=2.33.0; python_version >= '3.10'",
     "psutil>=5.9.0",
@@ -246,6 +231,7 @@ test = [
     "pyyaml>=6.0.3",
     "pytest-xdist>=3.8.0",
     "time-machine>=2.19.0",
+    "h11>=0.16.0",
 ]
 dev = [
     { include-group = "test" },
@@ -275,15 +261,9 @@ fuzz = [
 # This table is uv-local: it constrains resolution of this repo's lockfile and
 # never reaches requires-dist, so a floor placed here does NOT protect anyone who
 # runs `pip install cachekit`. A transitive that reaches users belongs in
-# [project] dependencies instead — see the anyio/h2 entries above.
+# [project] dependencies instead — see the urllib3 entry above.
 [tool.uv]
 constraint-dependencies = [
-    # urllib3 is a dev-only transitive dep (requests -> urllib3; requests is a
-    # dev dependency and also arrives via pip-audit).
-    # 2.8.0 fixes GHSA-8988-9cw3-xx77 (HTTPS proxy TLS config ignored),
-    # GHSA-gh4c-6fx4-qh6g (chunked deflate infinite loop) and
-    # GHSA-vxq7-64xx-v4gw (unbounded chunk-size line buffering).
-    "urllib3>=2.8.0",
     "fonttools>=4.60.2",
     "werkzeug>=3.1.4",
     # pip is a dev-only transitive dep (pip-audit -> pip-api -> pip). 26.1.2 fixes

{cachekit-0.21.0 → cachekit-0.22.0}/rust/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "cachekit-rs"
-version = "0.21.0"
+version = "0.22.0"
 edition = "2021"
 authors = ["cachekit Contributors"]
 description = "High-performance storage engine for caching with compression and encryption"

{cachekit-0.21.0 → cachekit-0.22.0}/rust/README.md

@@ -170,7 +170,6 @@ Setting `CACHEKIT_MASTER_KEY` instead of passing `master_key=` means every prese
 | Integrity Checking | - | ✅ | - | ✅ | ✅ 🔒 |
 | Encryption | - | - | - | - | ✅ Required |
 | L1 SWR (L1-only mode) | - | ✅ | - | ✅ | - |
-| L1 Invalidation | - | - | - | ✅ | ✅ |
 | Prometheus Metrics | - | -¹ | - | ✅ | ✅ |
 | Tracing | - | ✅ | - | ✅ | ✅ |
 | Structured Logging | - | ✅ | - | ✅ | ✅ |
@@ -182,6 +181,8 @@ Setting `CACHEKIT_MASTER_KEY` instead of passing `master_key=` means every prese
 >
 > **Default TTL** follows the cross-SDK [intent-preset spec](https://github.com/cachekit-io/protocol/blob/main/spec/intent-presets.md#default-ttl) (`@cache.io` 3600 s) — the same numbers as cachekit-rs and cachekit-ts. `ttl=` overrides it; `ttl=None` is the explicit never-expire opt-in ([details](docs/configuration.md#intent-presets)).
 >
+> **Cross-process L1 eviction** is not a preset feature: every preset's `invalidate_cache()` deletes from L1 and L2 alike, and evicting other processes' L1 copies is one process-wide opt-in, `CACHEKIT_INVALIDATION_LISTENER_ENABLED` ([L1 invalidation](docs/features/l1-invalidation.md#cross-process-l1-eviction)).
+>
 > **L1 SWR** (within-TTL background refresh) runs only in L1-only mode (`backend=None`) — with a backend configured it has no effect. `@cache.io` additionally ships past-TTL SWR via `stale_ttl` ([docs](docs/configuration.md#stale-while-revalidate-stale_ttl)).
 >
 > **`@cache.io()`** mirrors `@cache.production` (full reliability + observability) but routes to the managed CachekitIO SaaS backend instead of Redis. **`@cache.local()`** is a separate in-process path backed by `ObjectCache` (raw object references, entry-count LRU, no serialization) — the reliability and encryption features listed above do not apply to it.
@@ -242,6 +243,7 @@ def test_cached_function():
 
 - Circuit breaker with graceful degradation
 - Connection pooling with thread affinity (+28% throughput)
+- CachekitIO keeps idle connections pooled until the server closes them, with TCP keepalive probes, so a request after a pause skips a new TLS handshake
 - Distributed locking prevents cache stampedes
 - Pluggable backend abstraction (Redis, CachekitIO, File, Memcached, custom)
 - Untrusted-decode bounds: nesting depth and header-declared allocation are capped on every cache read (a forged entry is a bounded cache miss), verified against the protocol's shared [`decode-bounds.json`](https://github.com/cachekit-io/protocol/blob/2736a81f2f853cf08c5563c0fe7c8361331fa3ad/test-vectors/decode-bounds.json) vectors
@@ -256,7 +258,7 @@ def test_cached_function():
 | **StandardSerializer** | ★★★★☆ | General Python types, NumPy, Pandas |
 | **OrjsonSerializer** | ★★★★★ | JSON APIs (2-5x faster than stdlib) — requires `cachekit[json]` |
 | **ArrowSerializer** | ★★★★★ | Large DataFrames (6-23x faster for 10K+ rows) |
-| **EncryptionWrapper** | ★★★★☆ | Wraps any serializer with AES-256-GCM |
+| **+ Encryption** | ★★★★☆ | Any serializer above, AES-256-GCM encrypted: `@cache.secure(master_key=..., serializer=...)` |
 
 <details>
 <summary><strong>Serializer Examples</strong></summary>
@@ -395,7 +397,9 @@ free-threaded 3.14 with the GIL verified disabled (CI job
 `test-freethreaded`), and the Rust extension declares free-threaded safety
 (`gil_used = false`). Free-threaded wheels are **not yet published** and
 free-threaded builds are not officially supported — blocked upstream on
-orjson (no free-threaded wheels) and hiredis (re-enables the GIL on import). See
+orjson (no free-threaded wheels) and hiredis (re-enables the GIL on import;
+cachekit loads redis-py only for its Redis backend, and keeps hiredis out there,
+so redis-py uses its pure-Python parser). See
 [measured performance results](docs/free-threading.md#measured-performance) and the
 full concurrency audit: [docs/free-threading.md](docs/free-threading.md).
 
@@ -446,7 +450,7 @@ info = expensive_func.cache_info()
 | [Prometheus Metrics][prometheus-url] | Built-in observability |
 | [Zero-Knowledge Encryption][encryption-url] | Client-side security |
 | [Interop Mode][interop-url] | Cross-SDK cache sharing with cachekit-ts/rs |
-| [L1 Invalidation & SWR][l1-invalidation-url] | Invalidation scope (incl. cross-process whole-function on tenant-scoped Redis from the environment or `RedisBackendProvider`), stale-while-revalidate |
+| [L1 Invalidation & SWR][l1-invalidation-url] | Invalidation scope (incl. cross-process whole-function on tenant-scoped Redis from the environment or `RedisBackendProvider`), opt-in cross-process L1 eviction, stale-while-revalidate |
 | [Reference Caching][reference-caching-url] | `@cache.local()` for non-serializable objects |
 | [Rust Serialization][rust-serialization-url] | ByteStorage layer: LZ4, xxHash3, AES-256-GCM |
 | [SSRF Protection][ssrf-url] | URL allowlisting for the CachekitIO backend |

{cachekit-0.21.0 → cachekit-0.22.0}/src/cachekit/__init__.py

@@ -68,17 +68,14 @@ Example Usage:
     ```
 """
 
-__version__ = "0.21.0"
+__version__ = "0.22.0"
 
 from collections.abc import Callable
 from typing import Any, TypeVar
 
-# Configure hiredis compatibility BEFORE any Redis imports
-# This prevents GIL warnings in Python 3.13+ free-threading mode
-try:
-    from . import hiredis_compat
-except ImportError:
-    pass
+# Must run BEFORE any redis import: CACHEKIT_DISABLE_HIREDIS=true keeps hiredis out from here on.
+# The free-threaded default runs later, when cachekit.backends.redis loads (see cachekit.hiredis_compat).
+from . import hiredis_compat  # noqa: F401
 
 # Import the configuration classes
 # Redis client is automatically fast - no special import needed

{cachekit-0.21.0 → cachekit-0.22.0}/src/cachekit/backends/__init__.py

@@ -30,7 +30,7 @@ Dependency injection pattern:
 
 from __future__ import annotations
 
-from typing import Protocol
+from typing import TYPE_CHECKING, Protocol
 
 from cachekit.backends.base import (
     BaseBackend,
@@ -45,7 +45,10 @@ from cachekit.backends.errors import (
     BackendErrorType,
     CapabilityNotAvailableError,
 )
-from cachekit.backends.redis import RedisBackend
+
+if TYPE_CHECKING:
+    from cachekit.backends.memcached import MemcachedBackend
+    from cachekit.backends.redis import RedisBackend
 
 __all__ = [
     "BaseBackend",
@@ -106,7 +109,15 @@ class BackendProvider(Protocol):
 
 
 def __getattr__(name: str):
-    """Lazy import for optional backends (pymemcache may not be installed)."""
+    """Lazy imports: pymemcache may not be installed, and redis-py loads only for a program that uses Redis.
+
+    Loading redis-py loads hiredis, which re-enables the GIL on a free-threaded build, so
+    ``import cachekit`` must not load it (see cachekit.hiredis_compat).
+    """
+    if name == "RedisBackend":
+        from cachekit.backends.redis import RedisBackend
+
+        return RedisBackend
     if name == "MemcachedBackend":
         from cachekit.backends.memcached import MemcachedBackend
 

cachekit-0.22.0/src/cachekit/backends/_uninterrupted.py

@@ -0,0 +1,38 @@
+"""Await an executor or HTTP round-trip to completion through cancellation.
+
+Shared by the Redis provider and the CachekitIO backend. It lives here, not in the Redis provider,
+because importing that module loads redis-py, and a CachekitIO-only program must not.
+"""
+
+from __future__ import annotations
+
+import asyncio
+from typing import Optional, TypeVar
+
+T = TypeVar("T")
+
+
+async def _await_uninterrupted(fut: asyncio.Future[T]) -> T:
+    """Await ``fut`` to completion even if the current task is cancelled meanwhile.
+
+    ``asyncio.to_thread`` work is uninterruptible once an executor thread picks it up, and a
+    still-queued work item is dropped if its future is cancelled first — so a cancelled awaiter
+    either loses the outcome of a round-trip that still completes, or loses the round-trip
+    itself. ``asyncio.wait`` never cancels its inputs and never unwraps their result, so keep
+    waiting on ``fut`` until it is really done, absorbing every cancellation, then re-raise the
+    last one: callers read ``fut`` for the real outcome before letting it propagate.
+
+    Prefer a plain future (``loop.run_in_executor``): ``all_tasks()`` sweeps such as ``asyncio.run``
+    teardown cancel Tasks out from under the drain, and the outcome is lost again. A Task
+    (``asyncio.ensure_future``) is the route for native coroutines such as an async HTTP request;
+    it gives up only that sweep, so the caller must treat a cancelled ``fut`` as having no outcome.
+    """
+    cancelled: Optional[asyncio.CancelledError] = None
+    while not fut.done():
+        try:
+            await asyncio.wait({fut})
+        except asyncio.CancelledError as exc:
+            cancelled = exc
+    if cancelled is not None:
+        raise cancelled
+    return fut.result()