💬 glozow commented on pull request "[29.x] final changes for v29.1rc1":
(https://github.com/bitcoin/bitcoin/pull/33056#issuecomment-3114741444)
thanks! done
(https://github.com/bitcoin/bitcoin/pull/33056#issuecomment-3114741444)
thanks! done
💬 glozow commented on pull request "refactor: GenTxid type safety followups":
(https://github.com/bitcoin/bitcoin/pull/33005#discussion_r2229453544)
Comment above this declaration needs to be changed
(https://github.com/bitcoin/bitcoin/pull/33005#discussion_r2229453544)
Comment above this declaration needs to be changed
💬 glozow commented on pull request "refactor: GenTxid type safety followups":
(https://github.com/bitcoin/bitcoin/pull/33005#discussion_r2229461893)
Hm, is there a reason why `m_tx_inventory_known_filter` should contain sometimes-txids instead of wtxids?
(https://github.com/bitcoin/bitcoin/pull/33005#discussion_r2229461893)
Hm, is there a reason why `m_tx_inventory_known_filter` should contain sometimes-txids instead of wtxids?
👍 brunoerg approved a pull request: "doc: add note for watch-only wallet migration"
(https://github.com/bitcoin/bitcoin/pull/32866#pullrequestreview-3053110010)
ACK 9d25880bb720bc675a533098268b9e02f86e17ce
Happy to re-ack if you touch it again to address the LLM linter suggestion.
(https://github.com/bitcoin/bitcoin/pull/32866#pullrequestreview-3053110010)
ACK 9d25880bb720bc675a533098268b9e02f86e17ce
Happy to re-ack if you touch it again to address the LLM linter suggestion.
💬 maflcko commented on pull request "test: add assertions to SRD max weight test":
(https://github.com/bitcoin/bitcoin/pull/33058#issuecomment-3114779229)
[18:13:33.790] ./wallet/test/coinselector_tests.cpp(1247): [1;31;49merror: in "coinselector_tests/srd_tests": check EquivalentResult(expected_result, *res) has failed [0;39;49m
https://api.cirrus-ci.com/v1/task/6251945985310720/logs/ci.log
(https://github.com/bitcoin/bitcoin/pull/33058#issuecomment-3114779229)
[18:13:33.790] ./wallet/test/coinselector_tests.cpp(1247): [1;31;49merror: in "coinselector_tests/srd_tests": check EquivalentResult(expected_result, *res) has failed [0;39;49m
https://api.cirrus-ci.com/v1/task/6251945985310720/logs/ci.log
💬 bigshiny90 commented on pull request "test: Add functional tests for blockreconstructionextratxn parameter":
(https://github.com/bitcoin/bitcoin/pull/33023#issuecomment-3114783342)
> I think the description is not clear about what you're trying to cover/achieve with the test. Can you explain it better? Also, corecheck doesn't show any related new coverage.
This tests the -blockreconstructionextratxn parameter extra pool memory used specifically for compact block reconstruction. The "extra transaction pool" stores transactions that were rejected from the mempool for policy reasons (dust, low fees, non-standard scripts). Also, rbf original transactions get stuffed in here
...
(https://github.com/bitcoin/bitcoin/pull/33023#issuecomment-3114783342)
> I think the description is not clear about what you're trying to cover/achieve with the test. Can you explain it better? Also, corecheck doesn't show any related new coverage.
This tests the -blockreconstructionextratxn parameter extra pool memory used specifically for compact block reconstruction. The "extra transaction pool" stores transactions that were rejected from the mempool for policy reasons (dust, low fees, non-standard scripts). Also, rbf original transactions get stuffed in here
...
💬 w0xlt commented on pull request "[POC] wallet: Enable non-electronic (paper-based) wallet backup with codex32":
(https://github.com/bitcoin/bitcoin/pull/33043#issuecomment-3114785492)
The emphasis of this PR is on backup functionality: a backup feature isn’t very useful unless you can also restore the wallet reliably.
By contrast, the other PRs aim only to import a Codex32 secret—presumably from Core Lightning into Bitcoin Core—and each uses a different method.
The approach here creates a fresh wallet and rescans the chain, whereas PR #32652 appears to convert a Codex32 secret into an xpub via the proposed `addhdkey` RPC.
(https://github.com/bitcoin/bitcoin/pull/33043#issuecomment-3114785492)
The emphasis of this PR is on backup functionality: a backup feature isn’t very useful unless you can also restore the wallet reliably.
By contrast, the other PRs aim only to import a Codex32 secret—presumably from Core Lightning into Bitcoin Core—and each uses a different method.
The approach here creates a fresh wallet and rescans the chain, whereas PR #32652 appears to convert a Codex32 secret into an xpub via the proposed `addhdkey` RPC.
💬 martinatime commented on issue "getbestblockhash is sometimes taking a very long time":
(https://github.com/bitcoin/bitcoin/issues/32733#issuecomment-3114802238)
My RPi 4 only has 4GB of RAM and I am only running off of the SSD with no SD card installed.
(https://github.com/bitcoin/bitcoin/issues/32733#issuecomment-3114802238)
My RPi 4 only has 4GB of RAM and I am only running off of the SSD with no SD card installed.
💬 maflcko commented on pull request "multiprocess: Add capnp wrapper for Chain interface":
(https://github.com/bitcoin/bitcoin/pull/29409#issuecomment-3114802810)
For reference, the lint task still fails. Not sure if this is intentional or if you missed it.
(https://github.com/bitcoin/bitcoin/pull/29409#issuecomment-3114802810)
For reference, the lint task still fails. Not sure if this is intentional or if you missed it.
💬 maflcko commented on pull request "Migrate CI to hosted Cirrus Runners":
(https://github.com/bitcoin/bitcoin/pull/32989#discussion_r2229493624)
(tested podman buildx on a vanilla Ubuntu 24.04, fwiw)
(https://github.com/bitcoin/bitcoin/pull/32989#discussion_r2229493624)
(tested podman buildx on a vanilla Ubuntu 24.04, fwiw)
✅ maflcko closed a pull request: "NOMERGE DEBUG WIP ignore"
(https://github.com/bitcoin/bitcoin/pull/33028)
(https://github.com/bitcoin/bitcoin/pull/33028)
💬 maflcko commented on pull request "NOMERGE DEBUG WIP ignore":
(https://github.com/bitcoin/bitcoin/pull/33028#issuecomment-3114821576)
this is just too difficult to reproduce
(https://github.com/bitcoin/bitcoin/pull/33028#issuecomment-3114821576)
this is just too difficult to reproduce
💬 jonatack commented on pull request "cli: return local services in -netinfo":
(https://github.com/bitcoin/bitcoin/pull/31886#discussion_r2229516213)
Review feedback was unfavorable to adding test coverage for -netinfo. I'm not against it and happy to review proposals.
(https://github.com/bitcoin/bitcoin/pull/31886#discussion_r2229516213)
Review feedback was unfavorable to adding test coverage for -netinfo. I'm not against it and happy to review proposals.
💬 pinheadmz commented on issue "getbestblockhash is sometimes taking a very long time":
(https://github.com/bitcoin/bitcoin/issues/32733#issuecomment-3114844144)
Running v29 on my Pi4 has been fine so far. Even with 8 available I rarely ever see it use more than 2, and this is with lnd, LndHub, tor, and a few other services. I will note that I am still running the 32-bit PiOS however.
```
$ free -mh total used free shared buff/cache available Mem: 7.7Gi 1.2Gi 490Mi 41Mi
...
(https://github.com/bitcoin/bitcoin/issues/32733#issuecomment-3114844144)
Running v29 on my Pi4 has been fine so far. Even with 8 available I rarely ever see it use more than 2, and this is with lnd, LndHub, tor, and a few other services. I will note that I am still running the 32-bit PiOS however.
```
$ free -mh total used free shared buff/cache available Mem: 7.7Gi 1.2Gi 490Mi 41Mi
...
💬 maflcko commented on pull request "NOMERGE DEBUG WIP ignore":
(https://github.com/bitcoin/bitcoin/pull/33028#discussion_r2229528575)
It just reproduced. i guess the deadlock happens inside `Popen`, as there are no logs lines after this one:
```
./test/functional/combine_logs.py /ci_container_base/ci/scratch/test_runner/test_runner_₿_🏃_20250724_203021/rpc_signer_0/ | grep -C3 'warning'
test 2025-07-24T20:30:49.464060Z TestFramework.bitcoincli (DEBUG): Running bitcoin-cli ['-datadir=/ci_container_base/ci/scratch/test_runner/test_runner_₿_🏃_20250724_203021/rpc_signer_0/node3', 'enumeratesigners']
node3 2025-07-24T2
...
(https://github.com/bitcoin/bitcoin/pull/33028#discussion_r2229528575)
It just reproduced. i guess the deadlock happens inside `Popen`, as there are no logs lines after this one:
```
./test/functional/combine_logs.py /ci_container_base/ci/scratch/test_runner/test_runner_₿_🏃_20250724_203021/rpc_signer_0/ | grep -C3 'warning'
test 2025-07-24T20:30:49.464060Z TestFramework.bitcoincli (DEBUG): Running bitcoin-cli ['-datadir=/ci_container_base/ci/scratch/test_runner/test_runner_₿_🏃_20250724_203021/rpc_signer_0/node3', 'enumeratesigners']
node3 2025-07-24T2
...
💬 yancyribbens commented on pull request "test: add assertions to SRD max weight test":
(https://github.com/bitcoin/bitcoin/pull/33058#issuecomment-3114861829)
> [18:13:33.790] ./wallet/test/coinselector_tests.cpp(1247): �[1;31;49merror: in "coinselector_tests/srd_tests": check EquivalentResult(expected_result, *res) has failed�[0;39;49m
That is the unit test, right? It passes for me locally. I just re-based and pushed again and now that job is passing. I wonder now if there's a possible random seed that could cause SRD to fail.
(https://github.com/bitcoin/bitcoin/pull/33058#issuecomment-3114861829)
> [18:13:33.790] ./wallet/test/coinselector_tests.cpp(1247): �[1;31;49merror: in "coinselector_tests/srd_tests": check EquivalentResult(expected_result, *res) has failed�[0;39;49m
That is the unit test, right? It passes for me locally. I just re-based and pushed again and now that job is passing. I wonder now if there's a possible random seed that could cause SRD to fail.
💬 maflcko commented on pull request "NOMERGE DEBUG WIP ignore":
(https://github.com/bitcoin/bitcoin/pull/33028#discussion_r2229541626)
Same bt as in https://github.com/bitcoin/bitcoin/issues/32524#issuecomment-2888967608:
```
Thread 33 (Thread 0xf5933b40 (LWP 2485619) "b-httpworker.2"):
#0 0xf7f8e589 in __kernel_vsyscall ()
#1 0xf7aaeac7 in read () from /lib32/libc.so.6
#2 0x57dae8b6 in subprocess::util::read_atmost_n (fp=0x595e06d0, buf=0xf59305e4 "", read_upto=1024) at ./util/subprocess.h:437
#3 0x57dc2e19 in subprocess::Popen::execute_process (this=0xf5930cd8) at ./util/subprocess.h:1247
#4 0x57daf434 in subpro
...
(https://github.com/bitcoin/bitcoin/pull/33028#discussion_r2229541626)
Same bt as in https://github.com/bitcoin/bitcoin/issues/32524#issuecomment-2888967608:
```
Thread 33 (Thread 0xf5933b40 (LWP 2485619) "b-httpworker.2"):
#0 0xf7f8e589 in __kernel_vsyscall ()
#1 0xf7aaeac7 in read () from /lib32/libc.so.6
#2 0x57dae8b6 in subprocess::util::read_atmost_n (fp=0x595e06d0, buf=0xf59305e4 "", read_upto=1024) at ./util/subprocess.h:437
#3 0x57dc2e19 in subprocess::Popen::execute_process (this=0xf5930cd8) at ./util/subprocess.h:1247
#4 0x57daf434 in subpro
...
💬 jonatack commented on pull request "cli: return local services in -netinfo":
(https://github.com/bitcoin/bitcoin/pull/31886#discussion_r2229541731)
I kept the order the same as in getpeerinfo RPC, the GUI, and the -netinfo peers list.
(https://github.com/bitcoin/bitcoin/pull/31886#discussion_r2229541731)
I kept the order the same as in getpeerinfo RPC, the GUI, and the -netinfo peers list.
💬 achow101 commented on pull request "wallet, sqlite: Encapsulate SQLite statements in a RAII class":
(https://github.com/bitcoin/bitcoin/pull/33033#discussion_r2229546952)
I've dropped this commit from this PR and moved it to #33034. Also dropped `value_type` and made the constructor just take `span<const std::byte>` and that seems to work.
(https://github.com/bitcoin/bitcoin/pull/33033#discussion_r2229546952)
I've dropped this commit from this PR and moved it to #33034. Also dropped `value_type` and made the constructor just take `span<const std::byte>` and that seems to work.
💬 achow101 commented on pull request "wallet, sqlite: Encapsulate SQLite statements in a RAII class":
(https://github.com/bitcoin/bitcoin/pull/33033#discussion_r2229549000)
Done
(https://github.com/bitcoin/bitcoin/pull/33033#discussion_r2229549000)
Done