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

Don't fail to start up if can't subscribe to existing peer channels. #179

Merged
merged 1 commit into from
Aug 2, 2022

Conversation

theflyingcodr
Copy link
Contributor

Currently if there is an error subscribing to an existing peer channel we will fail with a fatal error and stop the server.

We don't want that as then the server won't start up, now we log an error and move on.

This could occur if the token has been removed from the peerchannel server, perhaps as part of a db cleanup, or the peerchannel server has moved host or has since been taken down.

…l we will fail with a fatal error and stop the server. We don't want that as then the server wonb't start up, now we log an error and move on
@theflyingcodr theflyingcodr added the bug Something isn't working label Aug 1, 2022
@theflyingcodr theflyingcodr merged commit 0ae0e3c into master Aug 2, 2022
@theflyingcodr theflyingcodr deleted the update/no_fatal_err_subscribe branch August 2, 2022 07:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant