-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix "Response head already sent" #19708
Conversation
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building 0c20b77
Full information is available in the Build summary check run. Test Failures⚙️ JVM Tests - JDK 11 #📦 extensions/vertx-web/deployment✖
✖
⚙️ JVM Tests - JDK 11 Windows #📦 extensions/vertx-web/deployment✖
✖
⚙️ JVM Tests - JDK 16 #📦 extensions/vertx-web/deployment✖
✖
|
The failure is related, but I am not sure if the test is really correct. Should we be writing exception details to a request that is already being written to the client? |
Hm... That does look weird indeed... But I guess it's one for @cescoffier to answer |
No, we should not add the exception to something already written, even only the HEAD. |
@stuartwdouglas any chance you could finalize this one? It looks like a good candidate for 2.2.1 |
Failing Jobs - Building 9c55363
Full information is available in the Build summary check run. Failures⚙️ Gradle Tests - JDK 11 Windows #- Failing:
📦✖
📦 integration-tests/gradle✖
|
Fixes #19621