Skip to content

Improve node error message #207

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

Closed

Conversation

jamillambert
Copy link
Collaborator

Include the upstream error message in the NoBitcoindInstance error to aid in debugging.

Include the upstream error message in the NoBitcoindInstance error to
aid in debugging.
@tcharding
Copy link
Member

tcharding commented May 29, 2025

That retry loop is horrible - it does two totally different things. We could split it up or in the first part of the loop we don't need to cache the last error, just check for > 10 and return the error after logging it.

This suggestion is just from looking, I could be wrong. What ever you do I don't think the error variant should have an option in it but I'm not 100% sure without changing the code.

@jamillambert
Copy link
Collaborator Author

That retry loop is horrible - it does two totally different things.

The intention of this PR was just to add more info to the error message to help debug the integration test errors we are getting, not to refactor any code. But in the meantime I have rewritten Node::with_conf to fix the whole issue, which makes this PR redundant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants