Repository navigation

Preserve coroutine cancellation through framework cleanup and I/O - #97

Merged

binaryfire merged 40 commits into

0.4from

fix/cancellation-propagation

Nov 2, 2026

Merged

Preserve coroutine cancellation through framework cleanup and I/O#97
binaryfire merged 40 commits into
0.4from
fix/cancellation-propagation

Commits on Nov 2, 2026
- Preserve cancellation precedence across chained failures
  binaryfire
  committed
  319f8d9
- Keep cancellation out of logger serialization fallbacks
  binaryfire
  committed
  63a5a34
- Preserve cancellation through safe-call reporting
  binaryfire
  committed
  71767b7
- Propagate cancellation from string replacements
  binaryfire
  committed
  1376b5f
- Avoid padding canceled timeboxed operations
  binaryfire
  committed
  5ec7de0
- Preserve cancellation while restoring cached objects
  binaryfire
  committed
  9b26c0e
- Preserve cancellation when releasing cache locks
  binaryfire
  committed
  ca5b5ed
- Preserve cancellation when releasing cache concurrency leases
  binaryfire
  committed
  7a6b3b5
- Exclude wrapped cancellation from cache failure events
  binaryfire
  committed
  28baacb
- Stop tagged cache work when cancellation is wrapped
  binaryfire
  committed
  9f9679c
- Preserve cancellation in Redis tagged cache operations
  binaryfire
  committed
  03d915f
- Stop user cache invalidation on cancellation
  binaryfire
  committed
  b3efaa0
- Preserve cancellation during Passport token issuance cleanup
  binaryfire
  committed
  1fa4030
- Stop Passport cache invalidation on wrapped cancellation
  binaryfire
  committed
  dded19b
- Stop feature-cache rotation on wrapped cancellation
  binaryfire
  committed
  b68bbaf
- Add a cancellation-aware PSR stream resource bridge
  binaryfire
  committed
  99a67cf
- Preserve cancellation through HTTP response resources
  binaryfire
  committed
  e27e683
- Preserve filesystem cancellation and stream ownership
  binaryfire
  committed
  97d9c40
- Stop read-through promotion after cancellation
  binaryfire
  committed
  61b8bd2
- Preserve cancellation and decoded-body ownership in S3 reads
  binaryfire
  committed
  3198de7
- Preserve cancellation and decoded-body ownership in GCS reads
  binaryfire
  committed
  85796f7
- Preserve cancellation precedence during pooled database release
  binaryfire
  committed
  9c507dc
- Preserve wrapped cancellation across Redis operations and cleanup
  binaryfire
  committed
  1c43b90
- Preserve cancellation from Redis concurrency lease cleanup
  binaryfire
  committed
  4ebd70d
- Preserve cancellation during process and pool cleanup
  binaryfire
  committed
  b597b4d
- Preserve cancellation in batch callbacks and option restoration
  binaryfire
  committed
  d5d411c
- Clean up canceled batch dispatch without losing its cause
  binaryfire
  committed
  13d7238
- Preserve cancellation while releasing debounce state
  binaryfire
  committed
  0662741
- Preserve cancellation while releasing dispatch locks
  binaryfire
  committed
  1bf97fd
- Keep notification cancellation through failure observers
  binaryfire
  committed
  79e342a
- Stop OAuth account renewal retries after cancellation
  binaryfire
  committed
  fe9e677
- Preserve session deletion cancellation through cleanup errors
  binaryfire
  committed
  0bddc8d
- Propagate cancellation from optional social email lookups
  binaryfire
  committed
  65fd368
- Preserve cancellation during compromised-password checks
  binaryfire
  committed
  a0ea12d
- Preserve cancellation through view rendering observers
  binaryfire
  committed
  e4b7b27
- Merge branch '0.4' into fix/cancellation-propagation
  binaryfire
  committed
  07a645d
- Preserve decorated stream ownership during resource casting
  binaryfire
  committed
  78298c9
- Inspect both Google exception causes for cancellation
  binaryfire
  committed
  768493c
- Propagate cancellation from file lock owner deserialization
  binaryfire
  committed
  c49010f
- Finalize cache serialization policy in custom server processes
  binaryfire
  committed
  9995a29

Commits

Commits on Nov 2, 2026