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

Repeater started message is shown too early #486

Closed
lsndr opened this issue Oct 24, 2023 · 0 comments
Closed

Repeater started message is shown too early #486

lsndr opened this issue Oct 24, 2023 · 0 comments
Assignees
Labels
Type: bug Something isn't working.

Comments

@lsndr
Copy link
Contributor

lsndr commented Oct 24, 2023

The The Repeater (11.2.0-next.1) started messages is shown before repeater connected and ready to accept requests.

Steps to Reproduce:

Run the following command:

bright-cli repeater --token {invalid token} --id {valid id}

Expected Result:

[2023-10-24T08:00:09.426Z] [NOTICE ] - Starting the Repeater (11.2.0-next.1)...
[2023-10-24T08:00:10.586Z] [ERROR  ] - (!) CRITICAL: Failed to log in with provided credentials.

Actual Result:

[2023-10-24T08:01:31.323Z] [NOTICE ] - Starting the Repeater (11.2.0-next.1)...
[2023-10-24T08:01:31.379Z] [NOTICE ] - The Repeater (11.2.0-next.1) started
[2023-10-24T08:01:32.553Z] [ERROR  ] - (!) CRITICAL: Failed to log in with provided credentials.
@lsndr lsndr added the Type: bug Something isn't working. label Oct 24, 2023
@lsndr lsndr self-assigned this Oct 24, 2023
@lsndr lsndr changed the title Repeater started message is shown too early Repeater started message is shown too early Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: bug Something isn't working.
Projects
None yet
Development

No branches or pull requests

1 participant