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

Status command should better handle the edge case before xud starts #389

Closed
peartobear opened this issue Apr 9, 2020 · 3 comments · Fixed by #452
Closed

Status command should better handle the edge case before xud starts #389

peartobear opened this issue Apr 9, 2020 · 3 comments · Fixed by #452
Assignees
Labels
enhancement New feature or request P2 mid priority

Comments

@peartobear
Copy link

Before

xud is starting... try again in a few seconds

the status command throws

│ xud │ could not connect to xud at localhost:8886, is │

It could be better handled with hardcoding the xud status to waiting.. for 4 seconds.

@kilrau
Copy link
Contributor

kilrau commented Apr 9, 2020

  • let's print Waiting for xud... when xucli returns could not connect to xud at localhost:8886, give it 5s sleep and then hit the same xucli command again. If it still returns ``could not connect to xud at localhost:8886` after 5s sleep, then that's what we'll return
  • let's replace all Container running with Waiting for <bitcoind/litecoind/geth/lndbtc/lndltc/connext/xud> to come up...

@kilrau kilrau added P2 mid priority enhancement New feature or request labels Apr 9, 2020
@kilrau
Copy link
Contributor

kilrau commented May 5, 2020

Interested? @hatmer

@hatmer
Copy link
Collaborator

hatmer commented May 9, 2020

I wasn't able to reproduce @peartobear's "could not connect to xud" error but I think I fixed it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P2 mid priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants