💬 darosior commented on pull request "descriptors: Be able to specify change and receiving in a single descriptor string":
(https://github.com/bitcoin/bitcoin/pull/22838#discussion_r1226687559)
nit: s/subscripts/derivation paths/

I guess "subscripts" is a copy pasta from the `tr()` error?

💬 darosior commented on pull request "descriptors: Be able to specify change and receiving in a single descriptor string":
(https://github.com/bitcoin/bitcoin/pull/22838#discussion_r1226859880)
This could be a `CHECKNONFATAL` that it's never empty, as any sane Miniscript must contain at least one key check.

💬 darosior commented on pull request "descriptors: Be able to specify change and receiving in a single descriptor string":
(https://github.com/bitcoin/bitcoin/pull/22838#discussion_r1227924512)
nit: the docstring could be updated with the new meaning and parameter.

💬 0xB10C commented on pull request "Use `int32_t` type for most transaction size/weight values":
(https://github.com/bitcoin/bitcoin/pull/23962#issuecomment-1589403896)
ACK 3ef756a5b558a1dd2fcb93bc0d4237707aa04f3f. I've focused my testing and code review on the tracepoint related changes. The docs, the test, and the mempool_monitor.py demo script are updated. I ran the `interface_usdt_mempool.py` test and the `mempool_monitor.py` script. The `mempool_monitor.py` output looks correct.

>> Something that just occurred to me: do/should we consider tracepoints to be a stable api?
>
> No, we shouldn't. I think that classes like CTxMemPoolEntry and their public a
...

🤔 darosior reviewed a pull request: "wallet: Give deprecation warning when loading a legacy wallet"
(https://github.com/bitcoin/bitcoin/pull/27869#pullrequestreview-1477293036)
Concept ACK. How about also logging for wallets that are loaded on startup?

💬 darosior commented on pull request "wallet: Give deprecation warning when loading a legacy wallet":
(https://github.com/bitcoin/bitcoin/pull/27869#discussion_r1228204662)
Maybe hint at how to migrate?

💬 achow101 commented on pull request "build: suppress external warnings by default":
(https://github.com/bitcoin/bitcoin/pull/27872#issuecomment-1589417552)
> so someone compiling bitcoind with sqlite shouldn't have to suppress warnings, no?

I get a large number of warnings from boost.

👍 dergoegge approved a pull request: "build: make sure we can overwrite config.{guess,sub} before doing so"
(https://github.com/bitcoin/bitcoin/pull/27875#pullrequestreview-1477330163)
tACK fc6c17b83887ef193f2b97264b1843c94dcb915d

💬 fanquake commented on pull request "build: make sure we can overwrite config.{guess,sub} before doing so":
(https://github.com/bitcoin/bitcoin/pull/27875#issuecomment-1589442718)
Concept ACK

🚀 achow101 merged a pull request: "Use `int32_t` type for most transaction size/weight values"
(https://github.com/bitcoin/bitcoin/pull/23962)

💬 hebasto commented on pull request "test: (refactor) Use datadir from options in chainstatemanager test":
(https://github.com/bitcoin/bitcoin/pull/27876#issuecomment-1589446124)
Concept ACK.

💬 pinheadmz commented on pull request "test: Add unit & functional test coverage for blockstore":
(https://github.com/bitcoin/bitcoin/pull/27850#discussion_r1228244278)
Yeah... CI fails because opening file in write mode is "OK" for read only file... what ??

```
[0;36m test 2023-06-13T14:33:55.813000Z TestFramework (DEBUG): Make the first block file read-only [0m
[0;36m test 2023-06-13T14:33:55.813000Z TestFramework (DEBUG): /tmp/cirrus-ci-build/ci/scratch/test_runner/test_runner_₿_🏃_20230613_143230/feature_reindex_205/node1/regtest/blocks/blk00000.dat stat: os.stat_result(st_mode=33024, st_ino=3929479, st_dev=2049, st_nlink=1, st_uid=0, st_gid=0, st
...

💬 MarcoFalke commented on pull request "test: handle failed `assert_equal()` assertions in bcc callback functions":
(https://github.com/bitcoin/bitcoin/pull/27831#issuecomment-1589476815)
@willcl-ark If you want to "ack" a pull, and want the merge-script and bot to recognize it, you'll have to do it in all-upper-case

💬 MarcoFalke commented on issue "Intermittent failures in interface_usdt_mempool.py":
(https://github.com/bitcoin/bitcoin/issues/27380#issuecomment-1589480337)
https://github.com/bitcoin/bitcoin/pull/27831 improves the logging, probably.

⚠️ MarcoFalke reopened an issue: "Intermittent failures in interface_usdt_mempool.py"
(https://github.com/bitcoin/bitcoin/issues/27380)
https://cirrus-ci.com/task/5779522121891840

```
[0;34m node0 2023-03-31T11:45:58.812384Z (mocktime: 2023-04-14T11:46:01Z) [http] [httpserver.cpp:257] [http_request_cb] [http] Received a POST request for / from 127.0.0.1:38238 [0m
[0;34m node0 2023-03-31T11:45:58.812543Z (mocktime: 2023-04-14T11:46:01Z) [httpworker.2] [rpc/request.cpp:179] [parse] [rpc] ThreadRPCServer method=getpeerinfo user=__cookie__ [0m
[0;36m test 2023-03-31T11:45:58.814000Z TestFramework (INFO): Hooking into mem
...

👍 dergoegge approved a pull request: "fuzz: Fix mini_miner_selection running out of coin"
(https://github.com/bitcoin/bitcoin/pull/27806#pullrequestreview-1477452630)
reACK 76c5ea703e77d580b6962e60398f4988cbd9b58b

💬 achow101 commented on pull request "descriptors: Be able to specify change and receiving in a single descriptor string":
(https://github.com/bitcoin/bitcoin/pull/22838#discussion_r1228321267)
Since the main point of this entire proposal is to make it easier to import receiving and change as a single item, I think it makes sense to special case these.

💬 fanquake commented on pull request "build: suppress external warnings by default":
(https://github.com/bitcoin/bitcoin/pull/27872#discussion_r1228330245)
Fixed.

💬 ryanofsky commented on pull request "wallet, tests: Expand and test when the blank wallet flag should be un/set":
(https://github.com/bitcoin/bitcoin/pull/25634#issuecomment-1589584105)
This PR has a lot of review (6 stale acks), and adds some very good test coverage. So maybe with an update and few reacks it could be merged.

I had a question about 2 test functions that didn't appear to be called in: https://github.com/bitcoin/bitcoin/pull/25634#discussion_r1224295479

I also don't think the change setting BLANK flank when DISABLE_PRIVATE_KEYS flag is set is a good one. BLANK seems like a confusing flag would be good to use less frequently rather than more frequently. Sett
...

💬 ryanofsky commented on pull request "index: improve initialization and pruning violation check":
(https://github.com/bitcoin/bitcoin/pull/27607#issuecomment-1589588481)
This can be rebased now that #27708 is merged