👍 john-moffett approved a pull request: "wallet: be able to specify a wallet name and passphrase to migratewallet"
(https://github.com/bitcoin/bitcoin/pull/26595)
reACK 9486509be65f09174a0cb50a337cac58a0c09de4
(https://github.com/bitcoin/bitcoin/pull/26595)
reACK 9486509be65f09174a0cb50a337cac58a0c09de4
💬 instagibbs commented on pull request "test: Replace 0xC0 constant":
(https://github.com/bitcoin/bitcoin/pull/27143#issuecomment-1440153890)
here and `script_lists` a few lines below it https://github.com/bitcoin/bitcoin/blob/master/test/functional/feature_taproot.py#L1548
(https://github.com/bitcoin/bitcoin/pull/27143#issuecomment-1440153890)
here and `script_lists` a few lines below it https://github.com/bitcoin/bitcoin/blob/master/test/functional/feature_taproot.py#L1548
💬 pinheadmz commented on issue "Bech32 address generation in regtest does not have the prefix `tb`":
(https://github.com/bitcoin/bitcoin/issues/12314#issuecomment-1440185562)
also bcoin: https://github.com/bcoin-org/bcoin/blob/57f59569116a1dede3d7d97b595a34809aaace5a/lib/protocol/networks.js#L867
(https://github.com/bitcoin/bitcoin/issues/12314#issuecomment-1440185562)
also bcoin: https://github.com/bcoin-org/bcoin/blob/57f59569116a1dede3d7d97b595a34809aaace5a/lib/protocol/networks.js#L867
💬 roconnor-blockstream commented on pull request "test: Replace 0xC0 constant":
(https://github.com/bitcoin/bitcoin/pull/27143#issuecomment-1440187848)
*lol* I'm embarrassed to say, I was only looking at Elements code.
(https://github.com/bitcoin/bitcoin/pull/27143#issuecomment-1440187848)
*lol* I'm embarrassed to say, I was only looking at Elements code.
💬 hebasto commented on pull request "clang-tidy: Add more `performance-*` checks and related fixes":
(https://github.com/bitcoin/bitcoin/pull/26642#issuecomment-1440196497)
Updated 2cdb84ca4c96cef03946b14ec46a7720f3ece098 -> 7db868b49b60de371d01cda1f8e5faaa0e18f822 ([pr26642.09](https://github.com/hebasto/bitcoin/commits/pr26642.09) -> [pr26642.10](https://github.com/hebasto/bitcoin/commits/pr26642.10)):
- rebased
- addressed @martinus's https://github.com/bitcoin/bitcoin/pull/26642#discussion_r1108879800
---
@martinus [wrote](https://github.com/bitcoin/bitcoin/pull/26642#discussion_r1108879800):
> I ran clang-tidy on this PR, and found a few more warnin
...
(https://github.com/bitcoin/bitcoin/pull/26642#issuecomment-1440196497)
Updated 2cdb84ca4c96cef03946b14ec46a7720f3ece098 -> 7db868b49b60de371d01cda1f8e5faaa0e18f822 ([pr26642.09](https://github.com/hebasto/bitcoin/commits/pr26642.09) -> [pr26642.10](https://github.com/hebasto/bitcoin/commits/pr26642.10)):
- rebased
- addressed @martinus's https://github.com/bitcoin/bitcoin/pull/26642#discussion_r1108879800
---
@martinus [wrote](https://github.com/bitcoin/bitcoin/pull/26642#discussion_r1108879800):
> I ran clang-tidy on this PR, and found a few more warnin
...
💬 Sjors commented on pull request "bumpfee: Allow the user to choose which output is change":
(https://github.com/bitcoin/bitcoin/pull/26467#issuecomment-1440197785)
utACK 4167843e0729994954317e2a4ac8a96a453bad79. The latest rebase takes the new `outputs` argument into account from #25344. It ensures they can't be combined, so that's good.
(https://github.com/bitcoin/bitcoin/pull/26467#issuecomment-1440197785)
utACK 4167843e0729994954317e2a4ac8a96a453bad79. The latest rebase takes the new `outputs` argument into account from #25344. It ensures they can't be combined, so that's good.
💬 hebasto commented on pull request "clang-tidy: Add more `performance-*` checks and related fixes":
(https://github.com/bitcoin/bitcoin/pull/26642#discussion_r1114448106)
Thanks! [Fixed](https://github.com/bitcoin/bitcoin/pull/26642#issuecomment-1440196497).
(https://github.com/bitcoin/bitcoin/pull/26642#discussion_r1114448106)
Thanks! [Fixed](https://github.com/bitcoin/bitcoin/pull/26642#issuecomment-1440196497).
💬 hebasto commented on pull request "clang-tidy: Add more `performance-*` checks and related fixes":
(https://github.com/bitcoin/bitcoin/pull/26642#discussion_r1114449588)
> I wonder why clang-tidy doesn't see these
So do I :)
(https://github.com/bitcoin/bitcoin/pull/26642#discussion_r1114449588)
> I wonder why clang-tidy doesn't see these
So do I :)
👍 pinheadmz approved a pull request: "wallet: be able to specify a wallet name and passphrase to migratewallet"
(https://github.com/bitcoin/bitcoin/pull/26595)
ACK 9486509be65f09174a0cb50a337cac58a0c09de4
reviewed code, ran tests, tested on regtest with cli commands
<details><summary>Show Signature</summary>
```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
ACK 9486509be65f09174a0cb50a337cac58a0c09de4
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEE5hdzzW4BBA4vG9eM5+KYS2KJyToFAmP2L3gACgkQ5+KYS2KJ
yToaJA/9GCc9Y84y5GfTPsmAUUYV/jFKr5Z9lDIATQca+Ou323CQ76CF00IQiyBB
ECtPlFJSPxaaKac4k5QmwT4BA4EgzcTKKVhjCVlorHyJQYk5yYBD5xOk2G0fPthS
VA3Ckmi
...
(https://github.com/bitcoin/bitcoin/pull/26595)
ACK 9486509be65f09174a0cb50a337cac58a0c09de4
reviewed code, ran tests, tested on regtest with cli commands
<details><summary>Show Signature</summary>
```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
ACK 9486509be65f09174a0cb50a337cac58a0c09de4
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEE5hdzzW4BBA4vG9eM5+KYS2KJyToFAmP2L3gACgkQ5+KYS2KJ
yToaJA/9GCc9Y84y5GfTPsmAUUYV/jFKr5Z9lDIATQca+Ou323CQ76CF00IQiyBB
ECtPlFJSPxaaKac4k5QmwT4BA4EgzcTKKVhjCVlorHyJQYk5yYBD5xOk2G0fPthS
VA3Ckmi
...
💬 pinheadmz commented on pull request "docs: add ramdisk guide for running tests on OSX":
(https://github.com/bitcoin/bitcoin/pull/27124#discussion_r1114482913)
sure, updated
(https://github.com/bitcoin/bitcoin/pull/27124#discussion_r1114482913)
sure, updated
💬 martinus commented on pull request "clang-tidy: Add more `performance-*` checks and related fixes":
(https://github.com/bitcoin/bitcoin/pull/26642#issuecomment-1440230390)
I don't know much about how the CI works, maybe it's possible to install a newer clang version? I'm using 15.0.7
(https://github.com/bitcoin/bitcoin/pull/26642#issuecomment-1440230390)
I don't know much about how the CI works, maybe it's possible to install a newer clang version? I'm using 15.0.7
👍 stickies-v approved a pull request: "docs: add ramdisk guide for running tests on OSX"
(https://github.com/bitcoin/bitcoin/pull/27124)
re-ACK cb7be3a
(https://github.com/bitcoin/bitcoin/pull/27124)
re-ACK cb7be3a
✅ MarcoFalke closed an issue: "Bech32 address generation in regtest does not have the prefix `tb`"
(https://github.com/bitcoin/bitcoin/issues/12314)
(https://github.com/bitcoin/bitcoin/issues/12314)
💬 MarcoFalke commented on issue "Bech32 address generation in regtest does not have the prefix `tb`":
(https://github.com/bitcoin/bitcoin/issues/12314#issuecomment-1440252506)
Closing due to lack of direction and progress. Pull requests with improvements are always welcome.
(https://github.com/bitcoin/bitcoin/issues/12314#issuecomment-1440252506)
Closing due to lack of direction and progress. Pull requests with improvements are always welcome.
💬 hebasto commented on pull request "clang-tidy: Add more `performance-*` checks and related fixes":
(https://github.com/bitcoin/bitcoin/pull/26642#issuecomment-1440256210)
> I don't know much about how the CI works, maybe it's possible to install a newer clang version? I'm using 15.0.7
Ah, that makes sense.
Maybe keep this PR diff CI-driven? I assume that bumping tools versions in a CI task will force us to fix more warnings, not just those you have already [mentioned](https://github.com/bitcoin/bitcoin/pull/26642#pullrequestreview-1302031747).
(https://github.com/bitcoin/bitcoin/pull/26642#issuecomment-1440256210)
> I don't know much about how the CI works, maybe it's possible to install a newer clang version? I'm using 15.0.7
Ah, that makes sense.
Maybe keep this PR diff CI-driven? I assume that bumping tools versions in a CI task will force us to fix more warnings, not just those you have already [mentioned](https://github.com/bitcoin/bitcoin/pull/26642#pullrequestreview-1302031747).
💬 roconnor-blockstream commented on pull request "test: Replace 0xC0 constant":
(https://github.com/bitcoin/bitcoin/pull/27143#issuecomment-1440257802)
Updated. I've left `VALID_LEAF_VERS` alone because, logically speaking, the definition of the valid tapleaf versions (defined in BIP-341) is independent of the choice of which tapleaf version to assign to tapscript (defined in BIP-342).
(https://github.com/bitcoin/bitcoin/pull/27143#issuecomment-1440257802)
Updated. I've left `VALID_LEAF_VERS` alone because, logically speaking, the definition of the valid tapleaf versions (defined in BIP-341) is independent of the choice of which tapleaf version to assign to tapscript (defined in BIP-342).
💬 instagibbs commented on pull request "test: Replace 0xC0 constant":
(https://github.com/bitcoin/bitcoin/pull/27143#issuecomment-1440278700)
ACK https://github.com/bitcoin/bitcoin/pull/27143/commits/c3b4b5a142b204ceeca4e9b1ca1e2ff41ddd1308
(https://github.com/bitcoin/bitcoin/pull/27143#issuecomment-1440278700)
ACK https://github.com/bitcoin/bitcoin/pull/27143/commits/c3b4b5a142b204ceeca4e9b1ca1e2ff41ddd1308
📝 theuni opened a pull request: "kernel: add missing include"
(https://github.com/bitcoin/bitcoin/pull/27144)
This syncs the cs_main definition/declaration.
Noticed when experimenting with the external visibility of `cs_main`.
Specifically, this is needed for the following to work as intended:
```c++
__attribute__ ((visibility ("default"))) extern RecursiveMutex cs_main;
```
(https://github.com/bitcoin/bitcoin/pull/27144)
This syncs the cs_main definition/declaration.
Noticed when experimenting with the external visibility of `cs_main`.
Specifically, this is needed for the following to work as intended:
```c++
__attribute__ ((visibility ("default"))) extern RecursiveMutex cs_main;
```
💬 pinheadmz commented on pull request "blockstorage: do not flush block to disk if it is already there":
(https://github.com/bitcoin/bitcoin/pull/27039#discussion_r1114563559)
Thanks Jon I believe I addressed all the style nits and reduced the number of generated blocks as requested in ec7dab684f172c7df37b3a9fe16250bedc2b775f. Adding test coverage for flush to disk is next...
(https://github.com/bitcoin/bitcoin/pull/27039#discussion_r1114563559)
Thanks Jon I believe I addressed all the style nits and reduced the number of generated blocks as requested in ec7dab684f172c7df37b3a9fe16250bedc2b775f. Adding test coverage for flush to disk is next...
💬 theuni commented on issue "`libbitcoinkernel`: Building `mingw-w64` dll's broken":
(https://github.com/bitcoin/bitcoin/issues/25008#issuecomment-1440326006)
@TheCharlatan symbol visibility is really complex, but it boils down to 2 main choices on our side, see here: https://github.com/bitcoin/bitcoin/issues/25008#issuecomment-1113661684
We can either ship a bunch of dll's (kernel, libsecp256k1, libstdc++, libpthread, etc)
_or_
We can roll everything up into 1 dll and have it just work.
For now, I propose we do the latter. However, this means we need tight control over our symbol visibility. If you're not familiar, see here for the canonical
...
(https://github.com/bitcoin/bitcoin/issues/25008#issuecomment-1440326006)
@TheCharlatan symbol visibility is really complex, but it boils down to 2 main choices on our side, see here: https://github.com/bitcoin/bitcoin/issues/25008#issuecomment-1113661684
We can either ship a bunch of dll's (kernel, libsecp256k1, libstdc++, libpthread, etc)
_or_
We can roll everything up into 1 dll and have it just work.
For now, I propose we do the latter. However, this means we need tight control over our symbol visibility. If you're not familiar, see here for the canonical
...