-
Notifications
You must be signed in to change notification settings - Fork 38.7k
init: Changing the rpcbind argument being ignored to a pop up warning #33813
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
Conversation
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. Code Coverage & BenchmarksFor details see: https://corecheck.dev/bitcoin/bitcoin/pulls/33813. ReviewsSee the guideline for information on the review process. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
|
https://github.com/bitcoin/bitcoin/actions/runs/19159736145/job/54788142845?pr=33813#step:5:171: Duplicate include(s) in src/httpserver.cpp:
#include <node/interface_ui.h>Can you also shorten the length of the commit title, and add a proper |
|
🚧 At least one of the CI tasks failed. HintsTry to run the tests locally, according to the documentation. However, a CI failure may still
Leave a comment here, if you need help tracking down a confusing failure. |
…ead of a debug log Github-Pull: bitcoin#33813 Rebased-From: 0cca5b772a9a76edc2f15e2f476ea138046c9cb8
| @@ -375,7 +376,7 @@ static bool HTTPBindAddresses(struct evhttp* http) | |||
| LogPrintf("WARNING: option -rpcallowip was specified without -rpcbind; this doesn't usually make sense\n"); | |||
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.
Do we want to change this one to a warning as well? It even say "WARNING".
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.
Not necessary since its a weird case imo? Why would you ever hit it?
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.
Why would you ever hit it?
the warning can be hit when -rpcallowip was specified without -rpcbind?
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.
right but is there an actual case where people do that? The only reason you would need to -rpcallowip is if you are exposing the rpc server with -rpcbind?
…ead of a debug log
0cca5b7 to
335a05c
Compare
|
🐙 This pull request conflicts with the target branch and needs rebase. |
|
closing this, this is resolved by: fa45a15 |
Github-Pull: bitcoin#33813 Rebased-From: 335a05c
When we ignore a users explicit request to an
rpcbind, i think it warrants for a warning instead of a debug log.