funded_psbt.txt and final_psbt.txt should only ever have one line in them, since later steps just do $(cat ...) to read them back. but the tutorial uses >> (append) instead of > (overwrite), so if you run the send or walletprocesspsbt step twice without deleting the file, it adds a second line instead of replacing the first one. then $(cat ...) picks up both lines as separate args and the next command fails with too many arguments.
Fixes #35862.
funded_psbt.txt and final_psbt.txt are each expected to hold exactly one
PSBT/hex string, consumed via unquoted $(cat ...) in every later step. Using
append (>>) instead of overwrite (>) means re-running the send or
walletprocesspsbt step without deleting the output file first appends a
second line, which $(cat ...) then word-splits into two arguments, causing
decodepsbt/analyzepsbt/walletprocesspsbt/sendrawtransaction to reject the
call with too many arguments.
Fixes #35862.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/35890.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline and AI policy for information on the review process. A summary of reviews will appear here.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
This PR description and the issue it's linked to were both clearly generated by an LLM. Even if the issue is real and the change here is correct, you need to write your own description.
Please read the AI Policy
oh sorry i did not intended to do it like this. I will edit the description in my own words.
@davidgumberg i have read ai policy. And rewrite the issue and description in my own words. Can you review it again.