Change the websocket connection timeout log from warning to fine #301
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This log is triggered when the
WebSocketConnectorcannot send a message to a connected fjage.js Gateway within 500ms.This tends to happen when a browser initiates a WebSocket connection, but the user is not focused on the browser window that has the connection open.
Also happens when the connection between the browser and the WebSocketConnector is abruptly broken (like loosing WiFi connection, or unplugging an ethernet cable).
This PR changes that
warningto afine, since it's not that critical as allfjåge.jsclients have retries builtin.