George BarnettandGitHub cda536de37 Dont hold lock over continuation in NIOThrowingAsyncSequenceProducer (#3454) ...

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 the NIOThrowingAsyncSequenceProducer.
- Merge 'next()' and 'next(for:)' methods in the state machine into a
single func; this reduces the amount of duplicated logic across the two
functions.

Result:

Lower chance of deadlock

2025-11-25 09:39:54 +00:00

..

NIOAsyncSequenceProducer.swift

Make _NIOFileSystem strict concurrency compatible (#3098)

2025-02-03 17:56:57 +00:00

NIOAsyncSequenceProducerStrategies.swift

Fixes all warnings when -require-explicit-sendable flag is enabled (#3320)

2025-07-30 11:50:28 +01:00

NIOAsyncWriter.swift

Handle cancellation between dropping and reaquiring lock (#3453)

2025-11-25 09:16:35 +00:00

NIOThrowingAsyncSequenceProducer.swift

Dont hold lock over continuation in NIOThrowingAsyncSequenceProducer (#3454)

2025-11-25 09:39:54 +00:00