Skip to content
This repository has been archived by the owner on Aug 28, 2021. It is now read-only.

Unnecessary alert of closed SocketInputStream upon closing WebSocket. #6

Open
T99 opened this issue Apr 7, 2018 · 0 comments
Open

Unnecessary alert of closed SocketInputStream upon closing WebSocket. #6

T99 opened this issue Apr 7, 2018 · 0 comments
Assignees
@T99
Labels
bug Bugs/errors that need fixing.
Milestone
0.2.0 - Closer to...

Comments

@T99
Copy link
Owner

T99 commented Apr 7, 2018

Even when a WebSocket is gracefully closed, the given WebSocket's WebSocketListener still reports that...

Attempted to read from closed parent WebSocket SocketInputStream.

...even though the user 'knows' that/it just doesn't matter anymore.

For context, the console spits out these lines upon closing a WebSocket:

Received CLOSE frame, queuing closing of parent WebSocket...
Successfully closed the WebSocket.
Attempted to read from closed parent WebSocket SocketInputStream.

Fixing this could possibly be accomplished alongside issue #1, 'Improve the close-frame control flow'.
@T99 T99 added the bug Bugs/errors that need fixing. label Apr 7, 2018
@T99 T99 added this to the 0.2 - Closer to the Real Thing milestone Apr 7, 2018
@T99 T99 self-assigned this Apr 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@T99 T99

Labels
bug Bugs/errors that need fixing.
Projects
None yet
Milestone
0.2.0 - Closer to the Real Thing
Development

No branches or pull requests
1 participant
@T99