Merge release to main

[bjhham]

No description provided.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: b0ab347d-f466-4e97-b964-2ccc6a1f2716

📥 Commits

Reviewing files that changed from the base of the PR and between 97cc35a and 69ed967.

📒 Files selected for processing (2)

• ktor-server/ktor-server-netty/jvm/src/io/ktor/server/netty/http1/NettyHttp1Handler.kt
• ktor-server/ktor-server-netty/jvm/test/io/ktor/tests/server/netty/NettySpecificTest.kt

✅ Files skipped from review due to trivial changes (1)

• ktor-server/ktor-server-netty/jvm/src/io/ktor/server/netty/http1/NettyHttp1Handler.kt

---

📝 Walkthrough

Walkthrough

Downgrade of logging level for IOException in NettyHttp1Handler.exceptionCaught from DEBUG to TRACE, plus a new unit test that asserts a single "I/O operation failed" message is emitted at TRACE when a client-disconnect-style IOException occurs.

Changes

Cohort / File(s)	Summary
Logging Level Adjustment ktor-server/ktor-server-netty/jvm/src/io/ktor/server/netty/http1/NettyHttp1Handler.kt	Changed logging for IOException in exceptionCaught from debug to trace; existing behavior of cancelling handlerJob and closing the Netty context is preserved.
Test Addition ktor-server/ktor-server-netty/jvm/test/io/ktor/tests/server/netty/NettySpecificTest.kt	Added a unit test that configures a Logback ListAppender, invokes exceptionCaught on an EmbeddedChannel with IOException("Connection reset by peer"), and asserts exactly one "I/O operation failed" event at TRACE level.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• PR #5563: Same change to lower IOException logging to TRACE in NettyHttp1Handler.exceptionCaught and adds an equivalent Netty-specific test verifying trace-level logging.

🚥 Pre-merge checks | ✅ 2 | ❌ 3

❌ Failed checks (2 warnings, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No pull request description was provided by the author, but the template requires subsystem, motivation, and solution sections.	Add a complete description following the template with subsystem, motivation explaining the problem/ticket, and solution describing the changes.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check	❓ Inconclusive	The title 'Merge release to main' is generic and does not convey meaningful information about the actual changes, which involve logging level adjustments and test additions.	Use a more descriptive title that reflects the actual changes, such as 'Change IOException logging level from debug to trace in NettyHttp1Handler' or include specific details about what is being merged.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bjhham/release_merge

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Ship it!