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

Reconnect to BTCD, LTCD or LNDs if request fails #48

Closed
michael1011 opened this issue Jan 6, 2019 · 0 comments · Fixed by #59
Closed

Reconnect to BTCD, LTCD or LNDs if request fails #48

michael1011 opened this issue Jan 6, 2019 · 0 comments · Fixed by #59
Assignees
Labels
enhancement New feature or request

Comments

@michael1011
Copy link
Member

Right now we are just trying to reconnect BTCD, LTCD or one of the LNDs if the initial connection on startup fails. We should also implement a reconnect logic if request or streaming call in the case of LND fails while Boltz is running.

The Boltz gRPC client of the middleware could be used as reference.

@michael1011 michael1011 added the enhancement New feature or request label Jan 6, 2019
@ImmanuelSegol ImmanuelSegol self-assigned this Jan 8, 2019
@ghost ghost added the in progress label Jan 8, 2019
ImmanuelSegol added a commit that referenced this issue Feb 5, 2019
* feat: reconnect to lnd if streaming calls are disconnected
@ghost ghost removed the in progress label Feb 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants