-
Notifications
You must be signed in to change notification settings - Fork 37.7k
test: Check that decoderawtransaction heuristic may fail #19831
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
Concept ACK Would it make sense to be more explicit about what could go wrong (since it'll always be the case that the heuristic matches either For example:
|
fadb4ea
to
fa0a43c
Compare
The amount doesn't have to be negative. I've modified the tx, so that the amount is positive. |
I'm a bit confused by this. Is this something that should be able to fail, or a bug that needs to be corrected in the heuristic? |
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. 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. |
@MarcoFalke mind addressing laanwj's question? |
🐙 This pull request conflicts with the target branch and needs rebase. Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft". |
There hasn't been much activity lately and the patch still needs rebase. What is the status here?
|
fa0a43c
to
57c0363
Compare
Fixed by #20595 |
Adds an example where the heuristic fails