💬 maflcko commented on pull request "Avoid returning references to mutex guarded members":
(https://github.com/bitcoin/bitcoin/pull/28774#issuecomment-1792035522)
No write will happen to the datadir cache after the first write, and no reader will have the reference before the first write, no? I am trying to say that the current code is fine. Otherwise, it would be good to add steps to reproduce UB.
No objection to changing the code, but if this is worth it to change, it should be done for all places in the whole codebase, not just some places.
(https://github.com/bitcoin/bitcoin/pull/28774#issuecomment-1792035522)
No write will happen to the datadir cache after the first write, and no reader will have the reference before the first write, no? I am trying to say that the current code is fine. Otherwise, it would be good to add steps to reproduce UB.
No objection to changing the code, but if this is worth it to change, it should be done for all places in the whole codebase, not just some places.
📝 hebasto converted_to_draft a pull request: "build: Patch Qt to handle minimum macOS version properly"
(https://github.com/bitcoin/bitcoin/pull/28775)
This PR is:
- required to [switch](https://github.com/bitcoin/bitcoin/pull/28622) to macOS 14 SDK (Xcode 15).
- an alternative to https://github.com/bitcoin/bitcoin/pull/28732.
(https://github.com/bitcoin/bitcoin/pull/28775)
This PR is:
- required to [switch](https://github.com/bitcoin/bitcoin/pull/28622) to macOS 14 SDK (Xcode 15).
- an alternative to https://github.com/bitcoin/bitcoin/pull/28732.
📝 BrandonOdiwuor opened a pull request: "gui: add used balance to overview page"
(https://github.com/bitcoin-core/gui/pull/775)
**Second part** of solving https://github.com/bitcoin-core/gui/issues/769
Add used balance to the overview page for wallets with the avoid_reuse flag enabled
### Prerequsite:
- **Part one**: https://github.com/bitcoin/bitcoin/pull/28776
overview page when avoid_reuse is enabled

overview page when avoid_reuse is not enabled

overview page when avoid_reuse is not enabled
 -> [simplifyMemPoolInteractions_5](https://github.com/TheCharlatan/bitcoin/tree/simplifyMemPoolInteractions_5), [compare](https://github.com/TheCharlatan/bitcoin/compare/simplifyMemPoolInteractions_4..simplifyMemPoolInteractions_5))
* Addressed @ismaelsadeeq's [comment](https://github.com/bitc
...
(https://github.com/bitcoin/bitcoin/pull/28391#issuecomment-1792187238)
Updated 105a0f4db4ffdc25d3ad30300c949d46d5d8e647 -> 65839d6267af1f5e0e04aded72cbfa23b56a1237 ([simplifyMemPoolInteractions_4](https://github.com/TheCharlatan/bitcoin/tree/simplifyMemPoolInteractions_4) -> [simplifyMemPoolInteractions_5](https://github.com/TheCharlatan/bitcoin/tree/simplifyMemPoolInteractions_5), [compare](https://github.com/TheCharlatan/bitcoin/compare/simplifyMemPoolInteractions_4..simplifyMemPoolInteractions_5))
* Addressed @ismaelsadeeq's [comment](https://github.com/bitc
...
💬 hebasto commented on pull request "build: use macOS 14 SDK (Xcode 15.0)":
(https://github.com/bitcoin/bitcoin/pull/28622#discussion_r1381461570)
According to https://developer.apple.com/support/xcode/, additionally, `OSX_MIN_VERSION=13.5` should be adjusted as well.
(https://github.com/bitcoin/bitcoin/pull/28622#discussion_r1381461570)
According to https://developer.apple.com/support/xcode/, additionally, `OSX_MIN_VERSION=13.5` should be adjusted as well.
💬 stratospher commented on pull request "test/BIP324: functional tests for v2 P2P encryption":
(https://github.com/bitcoin/bitcoin/pull/24748#issuecomment-1792201473)
Rebased on master.
(https://github.com/bitcoin/bitcoin/pull/24748#issuecomment-1792201473)
Rebased on master.
💬 Sun0fABeach commented on pull request "datacarriersize: Match more datacarrying":
(https://github.com/bitcoin/bitcoin/pull/28408#issuecomment-1792205732)
Concept ACK
Node runners need a builtin option to ignore all modern forms of datacarrying so they don't have to resort to manually patching their nodes.
... and the 'censorship' framing is getting old by now and has been rebutted often enough. If you really hold these principles, then please remove all your email spam filters. Otherwise you're engaging in censorship of a permissionless protocol and thereby impairing an important source of revenue for network users.
(https://github.com/bitcoin/bitcoin/pull/28408#issuecomment-1792205732)
Concept ACK
Node runners need a builtin option to ignore all modern forms of datacarrying so they don't have to resort to manually patching their nodes.
... and the 'censorship' framing is getting old by now and has been rebutted often enough. If you really hold these principles, then please remove all your email spam filters. Otherwise you're engaging in censorship of a permissionless protocol and thereby impairing an important source of revenue for network users.
👍 dergoegge approved a pull request: "refactors for subpackage evaluation"
(https://github.com/bitcoin/bitcoin/pull/28758#pullrequestreview-1712337150)
Code review ACK b5a60abe8783852f5b31bc1e63b5836530410e65
nit: the commit message in da9aceba217bbded6909f06144eaa1e1a4ebcb69 still has the old names
(https://github.com/bitcoin/bitcoin/pull/28758#pullrequestreview-1712337150)
Code review ACK b5a60abe8783852f5b31bc1e63b5836530410e65
nit: the commit message in da9aceba217bbded6909f06144eaa1e1a4ebcb69 still has the old names
👍 dergoegge approved a pull request: "Fuzz: Check individual and package transaction invariants"
(https://github.com/bitcoin/bitcoin/pull/28764#pullrequestreview-1712356208)
ACK fcb3069fa307942cf7f3edabcda1be96d615c91f
(https://github.com/bitcoin/bitcoin/pull/28764#pullrequestreview-1712356208)
ACK fcb3069fa307942cf7f3edabcda1be96d615c91f
📝 fanquake opened a pull request: "depends: latest config.guess & config.sub"
(https://github.com/bitcoin/bitcoin/pull/28781)
Before we make any local modifications (i.e #28733) pull the latest files from upstream.
(https://github.com/bitcoin/bitcoin/pull/28781)
Before we make any local modifications (i.e #28733) pull the latest files from upstream.
💬 fanquake commented on pull request "depends: Bump to capnproto-c++-1.0.1":
(https://github.com/bitcoin/bitcoin/pull/28735#issuecomment-1792270323)
> so I guess someone can report it upstream?
https://github.com/capnproto/capnproto/issues/1833
(https://github.com/bitcoin/bitcoin/pull/28735#issuecomment-1792270323)
> so I guess someone can report it upstream?
https://github.com/capnproto/capnproto/issues/1833