Skip to content

Conversation

gwynne
Copy link
Member

@gwynne gwynne commented Sep 12, 2025

Currently, we unconditionally include .clientClosedConnection errors in the logging for connection closure. Even though this is a debug-level log, this error is unnecessarily noisy and potentially misleading, since nothing has actually gone wrong. This PR no longer includes .clientClosedConnection errors in the log metadata for normal connection termination.

@gwynne gwynne requested a review from fabianfett September 12, 2025 14:04
@gwynne gwynne added the semver-patch No public API change. label Sep 12, 2025
Copy link

codecov bot commented Sep 12, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.45%. Comparing base (ce59628) to head (3179950).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #585      +/-   ##
==========================================
+ Coverage   62.44%   62.45%   +0.01%     
==========================================
  Files         132      132              
  Lines       10472    10476       +4     
==========================================
+ Hits         6539     6543       +4     
  Misses       3933     3933              
Files with missing lines Coverage Δ
...urces/PostgresNIO/New/PostgresChannelHandler.swift 84.49% <100.00%> (+0.10%) ⬆️

... and 2 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@fabianfett fabianfett merged commit 7a3d19d into main Sep 17, 2025
11 checks passed
@fabianfett fabianfett deleted the silence-misleading-logging branch September 17, 2025 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver-patch No public API change.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants