✅ waketraindev closed a pull request: "Add reset button and console commands for clearing output/history"
(https://github.com/bitcoin-core/gui/pull/882)
(https://github.com/bitcoin-core/gui/pull/882)
👍 rkrux approved a pull request: "cli: Handle arguments that can be either JSON or string"
(https://github.com/bitcoin/bitcoin/pull/33230#pullrequestreview-3263007651)
lgtm ACK df67bb6fd84c393eaf00f19074085ee080546bd3
Adds conveniences in CLI, cleans up tests too slightly.
(https://github.com/bitcoin/bitcoin/pull/33230#pullrequestreview-3263007651)
lgtm ACK df67bb6fd84c393eaf00f19074085ee080546bd3
Adds conveniences in CLI, cleans up tests too slightly.
✅ waketraindev closed a pull request: "rpc: add optional peer_ids param to filter getpeerinfo"
(https://github.com/bitcoin/bitcoin/pull/32741)
(https://github.com/bitcoin/bitcoin/pull/32741)
💬 zaidmstrr commented on pull request "rpc: Handle -named argument parsing where '=' character is used":
(https://github.com/bitcoin/bitcoin/pull/32821#discussion_r2375876150)
Thanks, I implemented the suggested changes.
(https://github.com/bitcoin/bitcoin/pull/32821#discussion_r2375876150)
Thanks, I implemented the suggested changes.
💬 zaidmstrr commented on pull request "rpc: Handle -named argument parsing where '=' character is used":
(https://github.com/bitcoin/bitcoin/pull/32821#discussion_r2375886327)
Seems reasonable.
(https://github.com/bitcoin/bitcoin/pull/32821#discussion_r2375886327)
Seems reasonable.
💬 theStack commented on pull request "Fix #25980: Validate transactions in combinerawtransaction":
(https://github.com/bitcoin/bitcoin/pull/33361#issuecomment-3328612816)
I'm currently favoring the fix in #31298, as it avoids comparing all the involved transaction fields (and input/output counts) by using the txid instead and is thus much simpler. One potential advantage of the approach of this PR though is that the error messages are more detailed, pointing out where exactly the txs differ -- personally I think just pointing out that the txs are not compatible is sufficient.
(https://github.com/bitcoin/bitcoin/pull/33361#issuecomment-3328612816)
I'm currently favoring the fix in #31298, as it avoids comparing all the involved transaction fields (and input/output counts) by using the txid instead and is thus much simpler. One potential advantage of the approach of this PR though is that the error messages are more detailed, pointing out where exactly the txs differ -- personally I think just pointing out that the txs are not compatible is sufficient.
💬 zaidmstrr commented on pull request "rpc: Handle -named argument parsing where '=' character is used":
(https://github.com/bitcoin/bitcoin/pull/32821#discussion_r2375898072)
I think using namespace is better here, as it provides clear intent of both the functions and how they are related. Also I find more readability using this approach.
(https://github.com/bitcoin/bitcoin/pull/32821#discussion_r2375898072)
I think using namespace is better here, as it provides clear intent of both the functions and how they are related. Also I find more readability using this approach.
🚀 fanquake merged a pull request: "macdeploy: avoid use of `Bitcoin Core` in Linux cross build"
(https://github.com/bitcoin/bitcoin/pull/33158)
(https://github.com/bitcoin/bitcoin/pull/33158)
💬 ryanofsky commented on pull request "multiprocess: Add capnp wrapper for Chain interface":
(https://github.com/bitcoin/bitcoin/pull/29409#issuecomment-3328660664)
<!-- begin push-17 -->
Rebased b372063241fbd34d27d062f3e438a3e425a9dfc5 -> 7ba7ec9d08927f244da8d5c1a7a1d7ced3239465 ([`pr/ipc-chain.16`](https://github.com/ryanofsky/bitcoin/commits/pr/ipc-chain.16) -> [`pr/ipc-chain.17`](https://github.com/ryanofsky/bitcoin/commits/pr/ipc-chain.17), [compare](https://github.com/ryanofsky/bitcoin/compare/pr/ipc-chain.16-rebase..pr/ipc-chain.17))<!-- end --> due to conflicts with #33169 and #32345
(https://github.com/bitcoin/bitcoin/pull/29409#issuecomment-3328660664)
<!-- begin push-17 -->
Rebased b372063241fbd34d27d062f3e438a3e425a9dfc5 -> 7ba7ec9d08927f244da8d5c1a7a1d7ced3239465 ([`pr/ipc-chain.16`](https://github.com/ryanofsky/bitcoin/commits/pr/ipc-chain.16) -> [`pr/ipc-chain.17`](https://github.com/ryanofsky/bitcoin/commits/pr/ipc-chain.17), [compare](https://github.com/ryanofsky/bitcoin/compare/pr/ipc-chain.16-rebase..pr/ipc-chain.17))<!-- end --> due to conflicts with #33169 and #32345
✅ fanquake closed an issue: "RPC: getblock(header) returns the same target for every block"
(https://github.com/bitcoin/bitcoin/issues/33440)
(https://github.com/bitcoin/bitcoin/issues/33440)
💬 ajtowns commented on pull request "net/rpc: Report inv information for debugging":
(https://github.com/bitcoin/bitcoin/pull/33448#discussion_r2375935187)
It's not needed the way we use it (passing in a fresh Stats argument each call), but arguably both should be zeroed out in case a previously-used object were reused.
(https://github.com/bitcoin/bitcoin/pull/33448#discussion_r2375935187)
It's not needed the way we use it (passing in a fresh Stats argument each call), but arguably both should be zeroed out in case a previously-used object were reused.
🚀 fanquake merged a pull request: "rpc: fix getblock(header) returns target for tip"
(https://github.com/bitcoin/bitcoin/pull/33446)
(https://github.com/bitcoin/bitcoin/pull/33446)
💬 maflcko commented on pull request "contrib: Add zsh completion scripts":
(https://github.com/bitcoin/bitcoin/pull/33402#issuecomment-3328705784)
Please squash your commits according to https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#squashing-commits
(https://github.com/bitcoin/bitcoin/pull/33402#issuecomment-3328705784)
Please squash your commits according to https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#squashing-commits
📝 fanquake opened a pull request: "[30.x] Backports & rc3"
(https://github.com/bitcoin/bitcoin/pull/33473)
Backports:
* #33446
(https://github.com/bitcoin/bitcoin/pull/33473)
Backports:
* #33446
💬 fanquake commented on pull request "rpc: fix getblock(header) returns target for tip":
(https://github.com/bitcoin/bitcoin/pull/33446#issuecomment-3328714993)
Backported to `30.x` in #33473.
(https://github.com/bitcoin/bitcoin/pull/33446#issuecomment-3328714993)
Backported to `30.x` in #33473.
💬 Sjors commented on pull request "guix: documented shasum gathering command":
(https://github.com/bitcoin/bitcoin/pull/33472#issuecomment-3328735722)
ACK d29ab9946f3c1916032f41e7a365dfcb26af2c46
(https://github.com/bitcoin/bitcoin/pull/33472#issuecomment-3328735722)
ACK d29ab9946f3c1916032f41e7a365dfcb26af2c46
💬 RandyMcMillan commented on pull request "Feature: Use different datadirs for different signets":
(https://github.com/bitcoin/bitcoin/pull/29838#issuecomment-3328754279)
note: i already tested
https://github.com/bitcoin-core/gui/pull/896/files
on top of this PR 🔥
(https://github.com/bitcoin/bitcoin/pull/29838#issuecomment-3328754279)
note: i already tested
https://github.com/bitcoin-core/gui/pull/896/files
on top of this PR 🔥
🚀 fanquake merged a pull request: "Backport Cirrus runners to 29.x"
(https://github.com/bitcoin/bitcoin/pull/33403)
(https://github.com/bitcoin/bitcoin/pull/33403)
💬 ryanofsky commented on pull request "cli: Handle arguments that can be either JSON or string":
(https://github.com/bitcoin/bitcoin/pull/33230#issuecomment-3328865138)
Code review ACK df67bb6fd84c393eaf00f19074085ee080546bd3, just rebased since last review. I do still think it would be good to improve the test (https://github.com/bitcoin/bitcoin/pull/33230#discussion_r2369570345)
(https://github.com/bitcoin/bitcoin/pull/33230#issuecomment-3328865138)
Code review ACK df67bb6fd84c393eaf00f19074085ee080546bd3, just rebased since last review. I do still think it would be good to improve the test (https://github.com/bitcoin/bitcoin/pull/33230#discussion_r2369570345)
📝 fanquake opened a pull request: "[29.x] Backports"
(https://github.com/bitcoin/bitcoin/pull/33474)
Backports:
* #33446
(https://github.com/bitcoin/bitcoin/pull/33474)
Backports:
* #33446