-
Notifications
You must be signed in to change notification settings - Fork 11.7k
[cli] Fix windows faucet wallet issue #24384
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
[cli] Fix windows faucet wallet issue #24384
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feel free to @ me if you want me to to test this locally once you have settled the review.
| .connect() | ||
| .await | ||
| .context("Failed to connect to gRPC endpoint")?; | ||
| let channel = endpoint.connect_lazy(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to connect lazily, as otherwise the grpc server might not be ready and the whole system errors due to being unable to connect to server.
@Scetrov I think the fix is now ready. I am also planning to add some tests. On my Windows machine, I built from source and then ran |
…address to a localhost. This is needed for Windows, for clients to correctly connect to services running on 0.0.0.0:port
087c1f0 to
8e1aef2
Compare
|
@amnn I touched the indexing side in three places and moved from |
amnn
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, tests should have you covered! Couple more clean up questions, but this looks good to go, thanks @stefan-mysten
Description
This PR fixes an issue flagged in #24041. Unfortunately, Windows does not allow clients to connect to 0.0.0.0, which was the case here, and led to an error when the faucet had to make an RPC client to node.
Test plan
Existing tests. Manually tested on Windows!
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.