💬 hebasto commented on pull request "cmake: use python from venv if available":
(https://github.com/bitcoin/bitcoin/pull/31411#issuecomment-2515600619)
> ... it can be tricky to configure cmake to use a python venv.
I've read https://github.com/astral-sh/uv/blob/main/README.md#python-management and used the following script for simplicity:
```cmake
cmake_minimum_required(VERSION 3.22)
project(test_py LANGUAGES NONE)
find_package(Python3 COMPONENTS Interpreter)
message("Python3_EXECUTABLE=${Python3_EXECUTABLE}")
```
I have no problems with finding `uv`'s Python on my Ubuntu 24.04:
```
$ python3 --version # system's Python
Python
...
(https://github.com/bitcoin/bitcoin/pull/31411#issuecomment-2515600619)
> ... it can be tricky to configure cmake to use a python venv.
I've read https://github.com/astral-sh/uv/blob/main/README.md#python-management and used the following script for simplicity:
```cmake
cmake_minimum_required(VERSION 3.22)
project(test_py LANGUAGES NONE)
find_package(Python3 COMPONENTS Interpreter)
message("Python3_EXECUTABLE=${Python3_EXECUTABLE}")
```
I have no problems with finding `uv`'s Python on my Ubuntu 24.04:
```
$ python3 --version # system's Python
Python
...
💬 sr-gi commented on pull request "p2p: Fill reconciliation sets (Erlay) attempt 2":
(https://github.com/bitcoin/bitcoin/pull/30116#discussion_r1868406931)
I added a comment for this instead of making a full set part of the sorting criteria. This should not happen under normal circumstances provided the set size is defined to account for way over the expected traffic between reconciliations. A peer hitting the limit is likely to be either broken or an attacker, and I don't think we should be catering to them (nor making the logic more complex based on that)
(https://github.com/bitcoin/bitcoin/pull/30116#discussion_r1868406931)
I added a comment for this instead of making a full set part of the sorting criteria. This should not happen under normal circumstances provided the set size is defined to account for way over the expected traffic between reconciliations. A peer hitting the limit is likely to be either broken or an attacker, and I don't think we should be catering to them (nor making the logic more complex based on that)
💬 sr-gi commented on pull request "p2p: Fill reconciliation sets (Erlay) attempt 2":
(https://github.com/bitcoin/bitcoin/pull/30116#discussion_r1868408445)
Done in https://github.com/bitcoin/bitcoin/pull/30116/commits/f51e36057e509356890a70ced3a7209f98e8db4f
(https://github.com/bitcoin/bitcoin/pull/30116#discussion_r1868408445)
Done in https://github.com/bitcoin/bitcoin/pull/30116/commits/f51e36057e509356890a70ced3a7209f98e8db4f
💬 sr-gi commented on pull request "p2p: Fill reconciliation sets (Erlay) attempt 2":
(https://github.com/bitcoin/bitcoin/pull/30116#discussion_r1868409396)
Done in the last force push
(https://github.com/bitcoin/bitcoin/pull/30116#discussion_r1868409396)
Done in the last force push
💬 sr-gi commented on pull request "p2p: Fill reconciliation sets (Erlay) attempt 2":
(https://github.com/bitcoin/bitcoin/pull/30116#discussion_r1868410206)
Covered in https://github.com/bitcoin/bitcoin/pull/30116/commits/f51e36057e509356890a70ced3a7209f98e8db4f
(https://github.com/bitcoin/bitcoin/pull/30116#discussion_r1868410206)
Covered in https://github.com/bitcoin/bitcoin/pull/30116/commits/f51e36057e509356890a70ced3a7209f98e8db4f
💬 achow101 commented on pull request "rpc: Remove submitblock pre-checks":
(https://github.com/bitcoin/bitcoin/pull/31175#issuecomment-2515669856)
ACK 73db95c65c1d372822166045ca8b9f173d5fd883
(https://github.com/bitcoin/bitcoin/pull/31175#issuecomment-2515669856)
ACK 73db95c65c1d372822166045ca8b9f173d5fd883
🚀 achow101 merged a pull request: "rpc: Remove submitblock pre-checks"
(https://github.com/bitcoin/bitcoin/pull/31175)
(https://github.com/bitcoin/bitcoin/pull/31175)
💬 achow101 commented on pull request "Package validation: accept packages of size 1":
(https://github.com/bitcoin/bitcoin/pull/31096#issuecomment-2515696899)
ACK 32fc59796f74a2941772b5ec2755b1319132cd9c
(https://github.com/bitcoin/bitcoin/pull/31096#issuecomment-2515696899)
ACK 32fc59796f74a2941772b5ec2755b1319132cd9c
💬 achow101 commented on pull request "refactor: Clamp worker threads in ChainstateManager constructor":
(https://github.com/bitcoin/bitcoin/pull/31313#issuecomment-2515702156)
ACK 8f85d36d68ab33ba237407a2ed16667eb149d61f
(https://github.com/bitcoin/bitcoin/pull/31313#issuecomment-2515702156)
ACK 8f85d36d68ab33ba237407a2ed16667eb149d61f
✅ achow101 closed an issue: "Why does `submitpackage` require at least two transactions"
(https://github.com/bitcoin/bitcoin/issues/31085)
(https://github.com/bitcoin/bitcoin/issues/31085)
🚀 achow101 merged a pull request: "Package validation: accept packages of size 1"
(https://github.com/bitcoin/bitcoin/pull/31096)
(https://github.com/bitcoin/bitcoin/pull/31096)
🚀 achow101 merged a pull request: "refactor: Clamp worker threads in ChainstateManager constructor"
(https://github.com/bitcoin/bitcoin/pull/31313)
(https://github.com/bitcoin/bitcoin/pull/31313)
🤔 hodlinator reviewed a pull request: "test: Prove+document ConstevalFormatString/tinyformat parity"
(https://github.com/bitcoin/bitcoin/pull/30933#pullrequestreview-2476944966)
So, I was a bit late reacting to the merge of #31174, but here we are - rebased and ready for review again.
Added a commit regarding non-parity of `"%n"` as suggested in https://github.com/bitcoin/bitcoin/pull/31174#issuecomment-2447224880.
(https://github.com/bitcoin/bitcoin/pull/30933#pullrequestreview-2476944966)
So, I was a bit late reacting to the merge of #31174, but here we are - rebased and ready for review again.
Added a commit regarding non-parity of `"%n"` as suggested in https://github.com/bitcoin/bitcoin/pull/31174#issuecomment-2447224880.
💬 hodlinator commented on pull request "test: Prove+document ConstevalFormatString/tinyformat parity":
(https://github.com/bitcoin/bitcoin/pull/30933#discussion_r1868489198)
The known cases where I was using `PassFmtIncorrect` have now become valid `PassFmt` thanks to your #31174. `PassFmtIncorrect` is no more.
(https://github.com/bitcoin/bitcoin/pull/30933#discussion_r1868489198)
The known cases where I was using `PassFmtIncorrect` have now become valid `PassFmt` thanks to your #31174. `PassFmtIncorrect` is no more.
💬 hodlinator commented on pull request "test: Prove+document ConstevalFormatString/tinyformat parity":
(https://github.com/bitcoin/bitcoin/pull/30933#discussion_r1868488090)
Thanks! Ended up naming it **Tfm**FormatZeroes in latest push to highlight the tinyformat part being essential.
(https://github.com/bitcoin/bitcoin/pull/30933#discussion_r1868488090)
Thanks! Ended up naming it **Tfm**FormatZeroes in latest push to highlight the tinyformat part being essential.
👋 hodlinator's pull request is ready for review: "test: Prove+document ConstevalFormatString/tinyformat parity"
(https://github.com/bitcoin/bitcoin/pull/30933)
(https://github.com/bitcoin/bitcoin/pull/30933)
💬 hodlinator commented on pull request "test: Prove+document ConstevalFormatString/tinyformat parity":
(https://github.com/bitcoin/bitcoin/pull/30933#discussion_r1868496986)
I prefer retaining negative tests to increase certainty and would rather not do the `PassFmt<1>("%s")` -> `PassFmt("%s", "test")` refactor in this PR if that's okay with you.
(https://github.com/bitcoin/bitcoin/pull/30933#discussion_r1868496986)
I prefer retaining negative tests to increase certainty and would rather not do the `PassFmt<1>("%s")` -> `PassFmt("%s", "test")` refactor in this PR if that's okay with you.
💬 andrewtoth commented on pull request "validation: fetch block inputs on parallel threads ~17% faster IBD":
(https://github.com/bitcoin/bitcoin/pull/31132#discussion_r1868551853)
We no longer need to block on the shared outpoints vector. We write to it once in the main thread before notifying the other threads and then only read from it afterwards.
(https://github.com/bitcoin/bitcoin/pull/31132#discussion_r1868551853)
We no longer need to block on the shared outpoints vector. We write to it once in the main thread before notifying the other threads and then only read from it afterwards.
💬 andrewtoth commented on pull request "validation: fetch block inputs on parallel threads ~17% faster IBD":
(https://github.com/bitcoin/bitcoin/pull/31132#discussion_r1868552609)
Done.
(https://github.com/bitcoin/bitcoin/pull/31132#discussion_r1868552609)
Done.
💬 andrewtoth commented on pull request "validation: fetch block inputs on parallel threads ~17% faster IBD":
(https://github.com/bitcoin/bitcoin/pull/31132#discussion_r1868552959)
This is the hardcoded batch size used in CheckQueue. Not sure why that was selected, but I deferred to previous choices.
(https://github.com/bitcoin/bitcoin/pull/31132#discussion_r1868552959)
This is the hardcoded batch size used in CheckQueue. Not sure why that was selected, but I deferred to previous choices.