-
Notifications
You must be signed in to change notification settings - Fork 38.7k
rpc: Return errors in loadtxoutset that currently go to logs #30497
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 CoverageFor detailed information about the code coverage, see the test coverage report. ReviewsSee the guideline for information on the review process.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update. 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. |
|
🚧 At least one of the CI tasks failed. HintsMake sure to run all tests locally, according to the documentation. The failure may happen due to a number of reasons, for example:
Leave a comment here, if you need help tracking down a confusing failure. |
|
Concept ACK I think the title is a bit confusing here. It sounds like the error message content changes but they are just moved from logs to RPC. I think the title of the the issue that is fixed is a better description. |
Good point, fixed! |
danielabrozzoni
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.
ACK fa5c253b4e9e416a6ff729365cb66e13ac0f66e7 - code looks good to me, tests are passing locally, but I didn't do any manual testing.
|
Concept ACK |
The message is not exposed in the GUI or another translated context, so translating it is useless for now. Also, fix a nit from bitcoin#30395 (comment)
fa5c253 to
fa91404
Compare
|
Rebased. Should be trivial to re-ACK with |
|
re-ACK fa91404c68b4d503e6568f49aaf74a5746887185 |
ryanofsky
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.
Code review ACK fa91404c68b4d503e6568f49aaf74a5746887185. Nice change which should make RPC errors easier to understand.
The error messages should never happen in normal operation. However, if they do, they are helpful to return to the user to debug the issue. For example, to notice a truncated file.
fa91404 to
fa530ec
Compare
|
Force pushed to adjust three error messages slightly. Should be easy to re-ACK |
ryanofsky
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.
Code review ACK fa530ec, just adjusting error messages a little since last review. (Thanks!)
|
Code review ACK fa530ec |
|
rfm, or does it need more review? |
Looks good to me. I'd tend to wait for 3 current acks on a change to validation.cpp, but in this case there are two current acks and only string changes since that last stale ack so this seem close enough. Will merge soon. |
The error messages should never happen in normal operation. However, if
they do, they are helpful to return to the user to debug the issue. For
example, to notice a truncated file.
This fixes #28621
Also includes a minor refactor commit.