some exception logger Level is too high
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
such as：
WebSocketException: The header of a frame cannot be read from the stream.
SocketException: An existing connection was forcibly closed by the remote host
The exceptions appear when the remote peer(client-side) is closed.
there are well that it ignored,
i'm sorry, i weak at English.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating where WebSocketException and SocketException are logged when a remote peer closes the connection. Reproduce that disconnect scenario and compare the resulting log level with the intended handling; the issue is done when these expected remote-close exceptions no longer appear at an unnecessarily high level.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100