Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DevServer logs WebSocketException when app is closed creating unnecessary noise #18337

Open
Takoooooo opened this issue Sep 30, 2024 · 0 comments
Labels
difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification

Comments

@Takoooooo
Copy link

Takoooooo commented Sep 30, 2024

Current behavior

I assume we shouldn't log it because that's to be expected that when app will be closed WebSocket connection would be shut down ungracefully. Here how it looks in Rider logs.
image

Expected behavior

Shorter message is sent instead marking that the connection is closed and user app is probably closed too.

How to reproduce it (as minimally and precisely as possible)

Try to close the app connected to the DevServer.

@Takoooooo Takoooooo added kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. labels Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification
Projects
None yet
Development

No branches or pull requests

1 participant