-
Notifications
You must be signed in to change notification settings - Fork 848
fix(rpc): improve error reporting for socket path issues. #12799
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
fix(rpc): improve error reporting for socket path issues. #12799
Conversation
Replace generic ENAMETOOLONG errno with an error that indicates the rpc socket issue. Also improve startup error message clarity.
|
[approve ci] |
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.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
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.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
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.
Pull request overview
Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
cmcfarlen
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.
Thanks!
Sometimes, when you use autest, you could end up with a large socket pathname.
You only discover this once you try to access the jsonrpc node, but even when
you get an error, it's hard to identify the root cause.
With this change, you'll now find a clearer error in the logs that points you
in the right direction.
Replace generic
ENAMETOOLONGerrno with an error that indicates the RPCsocket issue. Also improve startup error message clarity.
Note: Using
fprintfas it seems the log machinery may not be fully initialized at this point.