Skip to content
This repository was archived by the owner on Apr 13, 2025. It is now read-only.

Conversation

@hlxid
Copy link
Member

@hlxid hlxid commented Dec 22, 2021

Fixes #365.

If automatic login fails and nodecg-io is not loaded afterwards this will still display a error. This happens when e.g. the password set in the automatic login config is wrong.
However if automatic login fails and nodecg-io is loaded afterwards just a warning will be logged with this PR. This is the case when the dashboard reconnects after a restart and loggs back in.

…ady loaded

Fixes #365.
If automatic login fails and nodecg-io is not loaded afterwards this will still display a error. This happens when e.g. the password set in the automatic login config is wrong.
However if automatic login fails and nodecg-io is loaded afterwards just a warning will be logged with this PR. This is the case when the dashboard reconnects after a restart and loggs back in.
@hlxid hlxid merged commit 4993c8c into main Dec 25, 2021
@hlxid hlxid deleted the fix/365-already-logged-in-warning branch December 25, 2021 18:45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use of error in nodecg-io-core where warning is appropriate

2 participants