Sam Brannen
a4720ccf77
Prior to this commit, only the very first AsynchronousFileChannel#write call in DataBufferUtils$WriteCompletionHandler#hookOnNext(DataBuffer) was guarded against exceptions escaping synchronously, and even then only via `catch (RuntimeException ex)`, per the original fix for gh-36184. While widening that guard to match the read side's `catch (Throwable ex)` combined with `Exceptions.throwIfFatal(ex)` (see gh-37143), we discovered that completed(Integer, Attachment) contains two more direct `this.channel.write(...)` calls -- for continuing a partial write and for advancing to the next ByteBuffer within the same DataBuffer's iterator -- neither of which was guarded at all. Since completed() is invoked by the channel's own completion callback, typically on a different thread than the one that issued the original write, a synchronous exception escaping either of those calls has no path back to the FluxSink, and the resulting Flux hangs indefinitely, exactly as described in gh-37143, for any write that receives a partial OS write or spans multiple ByteBuffers. To address that, this commit extracts a private write(ByteBuffer, long, Attachment) helper that wraps the channel.write(...) call with a try/catch block, routing any non-fatal Throwable -- via Exceptions.throwIfFatal() -- to the existing failed(Throwable, Attachment) handler. All three call sites (hookOnNext() and both branches in completed()) now go through this helper, ensuring the Flux always terminates with a proper error signal instead of hanging silently, regardless of which write attempt fails or which thread it fails on. See gh-36184 See gh-37143 Closes gh-37145
Spring Framework 
This is the home of the Spring Framework: the foundation for all Spring projects. Collectively the Spring Framework and the family of Spring projects are often referred to simply as "Spring".
Spring provides everything required beyond the Java programming language for creating enterprise applications for a wide range of scenarios and architectures. Please read the Overview section of the reference documentation for a more complete introduction.
Code of Conduct
This project is governed by the Spring Code of Conduct. By participating, you are expected to uphold this code of conduct. Please report unacceptable behavior to spring-code-of-conduct@spring.io.
Access to Binaries
For access to artifacts or a distribution zip, see the Spring Framework Artifacts wiki page.
Documentation
The Spring Framework maintains reference documentation (published and source), GitHub wiki pages, and an API reference. There are also guides and tutorials across Spring projects.
Micro-Benchmarks
See the Micro-Benchmarks wiki page.
Build from Source
See the Build from Source wiki page and the CONTRIBUTING.md file.
Continuous Integration Builds
CI builds are defined with GitHub Actions workflows.
Stay in Touch
Follow @SpringCentral, @SpringFramework, and its team members on 𝕏. In-depth articles can be found at The Spring Blog, and releases are announced via our releases feed.
License
The Spring Framework is released under version 2.0 of the Apache License.