Fatal WebSocketException
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
2022-08-17 오후 3:56:54|Fatal|WebSocket.b__170_2|WebSocketSharp.WebSocketException: An unsupported opcode.
위치: WebSocketSharp.WebSocketFrame.processHeader(Byte[] header)
위치: WebSocketSharp.WebSocketFrame.<>c__DisplayClass73_0.b__0(Byte[] bytes)
위치: WebSocketSharp.Ext.<>c__DisplayClass54_0.b__0(IAsyncResult ar)
2022-08-17 오후 3:56:54|Trace|WebSocket.close|Begin closing the connection.
2022-08-17 오후 3:56:54|Debug|WebSocket.closeHandshake|Was clean?: False
sent: True
received: False
2022-08-17 오후 3:56:54|Trace|WebSocket.close|End closing the connection.
2022-08-17 오후 3:56:54|Error|WebSocketSessionManager.tryGetSession|A session with the specified ID isn't found:
ID: aaf167377a844dc8bf45a3a555f8d22e
2022-08-17 오후 3:56:54|Error|WebSocketSessionManager.tryGetSession|A session with the specified ID isn't found:
ID: aaf167377a844dc8bf45a3a555f8d22e
websocket-sharp.dll version 1.0.4.0
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 reading WebSocketFrame.processHeader and the WebSocket.startReceiving stack-trace entries. The report contains only logs and does not provide reproduction steps, expected behavior, or a defined fix, so clarify those details before determining what completion should mean.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100