Commit title

fix: avoid incrementing readErrCount for temporary errors and reset on successful read

Description

• Do not incrementreadErrCount for temporary errors such as timeouts, as they do not indicate actual connection failures.
• ResetreadErrCount after successful read operations to reflect the true health status of the connection.
• This preventsreadErrCount from growing due to normal timeout logic and provides a more accurate error state.

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update
• Go Version Update
• Dependency Update

Description

This PR addresses an issue wherereadErrCount was incremented on all errors, including temporary errors such as timeouts. Since timeouts often occur as part of normal connection management, especially when read deadlines are used, counting them as errors could lead to misleading high error counts and unnecessary connection termination or misreporting.

Now, only permanent errors causereadErrCount to increase, and a successful read resets this counter, better reflecting the real stability of the connection.

Related Tickets & Documents

• Related Issue #
• Closes #

Added/updated tests?

• Yes
• No, and this is why:Please add details if you do not include tests (if the repo policy requires, plan test additions)
• I need help with writing tests

Run verifications and test

• make verify is passing
• make test is passing

Checklist (before submitting):

• Read theContributing guide
• Read theCode of Conduct
• Provided clear commit messages and code comments.
• Added/updated documentation as needed.
• Requested review from gorilla/pull-request-reviewers.