George Barnett 663ddc80f2 Dont hold lock over continuation in TokenBucket (#3455) ...

Motivation:

The various 'withMumbleContinuation' APIs are supposed to be invoked
synchronously with the caller. This assumption allows a lock to be
acquired before the call and released from the body of the
'withMumbleContinuation' after e.g. storing the continuation. However
this isn't the case and the job may be re-enqueued on the executor
meaning that this is pattern is vulnerable to deadlocks.

Modifications:

- Drop and reacquire the lock in TokenBucket.
- Switch to NIOLockedValueBox

Result:

Lower chance of deadlock

2025-12-01 15:46:46 +00:00

..

advanced-performance-analysis.md

Fix broken link to swift-server performance documentation (#2907)

2024-10-07 13:37:58 +00:00

debugging-allocations.md

Add bpftrace allocations script (#3113)

2025-07-11 11:58:05 +00:00

io_uring.md

Added second implementation of liburing as discussed in #1761. (#1804)

2021-04-29 10:40:27 +01:00

migration-guide-NIO1-to-NIO2.md

Minor rewording to clarify the location of the NIO1 to NIO2 migration guide (#1945)

2021-08-24 10:43:49 +01:00

optimization-tips.md

We use main as our development branch now. (#1651)

2020-09-24 18:02:44 +01:00

public-api.md

Point docs to Swift Package Index (#2353)

2023-01-23 06:09:43 -08:00

public-async-nio-apis.md

Use Swift 6.0 docs pipeline (#2966)

2024-11-07 13:03:47 +00:00

workarounds.md

Dont hold lock over continuation in TokenBucket (#3455)

2025-12-01 15:46:46 +00:00