π¬ purpleKarrot commented on pull request "kernel: add contextβfree block validation API (`btck_check_block_context_free`) with POW/Merkle flags":
(https://github.com/bitcoin/bitcoin/pull/33908#issuecomment-3552114302)
Both @w0xlt and @yuvicc, please don't introduce more [boolean trap](https://ariya.io/2011/08/hall-of-api-shame-boolean-trap)s.
(https://github.com/bitcoin/bitcoin/pull/33908#issuecomment-3552114302)
Both @w0xlt and @yuvicc, please don't introduce more [boolean trap](https://ariya.io/2011/08/hall-of-api-shame-boolean-trap)s.
π¬ l0rinc commented on pull request "miniscript refactor: Remove unique_ptr-indirection (#30866 follow-up)":
(https://github.com/bitcoin/bitcoin/pull/31713#issuecomment-3552171802)
Redid the rebase locally, besides an import collision the following was added:
```patch
diff --git a/src/test/miniscript_tests.cpp b/src/test/miniscript_tests.cpp
--- a/src/test/miniscript_tests.cpp (revision 31196b79cabb6e4519e8a27165e1be75c5044403)
+++ b/src/test/miniscript_tests.cpp (date 1763547689484)
@@ -727,7 +727,7 @@
g_testdata.reset();
}
-// Confirm that ~Node() and Node::Clone() are stack-safe.
+// Confirm that ~Node(), Node::Clone() and operator=(Node&&) are stack-s
...
(https://github.com/bitcoin/bitcoin/pull/31713#issuecomment-3552171802)
Redid the rebase locally, besides an import collision the following was added:
```patch
diff --git a/src/test/miniscript_tests.cpp b/src/test/miniscript_tests.cpp
--- a/src/test/miniscript_tests.cpp (revision 31196b79cabb6e4519e8a27165e1be75c5044403)
+++ b/src/test/miniscript_tests.cpp (date 1763547689484)
@@ -727,7 +727,7 @@
g_testdata.reset();
}
-// Confirm that ~Node() and Node::Clone() are stack-safe.
+// Confirm that ~Node(), Node::Clone() and operator=(Node&&) are stack-s
...
π¬ l0rinc commented on pull request "miniscript refactor: Remove unique_ptr-indirection (#30866 follow-up)":
(https://github.com/bitcoin/bitcoin/pull/31713#discussion_r2541499665)
nit, if you touch again, we could simply omit leaves with no subs
```suggestion
if (i.subs) queue.push_back(std::move(i.subs));
```
(https://github.com/bitcoin/bitcoin/pull/31713#discussion_r2541499665)
nit, if you touch again, we could simply omit leaves with no subs
```suggestion
if (i.subs) queue.push_back(std::move(i.subs));
```
π¬ hebasto commented on pull request "Document compiler configuration for native depends packages":
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541619806)
Other native package, not only `native_qt`, require `g++`.
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541619806)
Other native package, not only `native_qt`, require `g++`.
π hebasto approved a pull request: "Document compiler configuration for native depends packages"
(https://github.com/bitcoin/bitcoin/pull/33902#pullrequestreview-3482217585)
ACK b1b559f83f629c7d0976c05d07cbc6ec04e84095.
(https://github.com/bitcoin/bitcoin/pull/33902#pullrequestreview-3482217585)
ACK b1b559f83f629c7d0976c05d07cbc6ec04e84095.
π¬ hebasto commented on pull request "Document compiler configuration for native depends packages":
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541624816)
```suggestion
- `build_CC`: C compiler for native tools (default: `gcc` on Linux, `clang` on macOS/FreeBSD/OpenBSD)
- `build_CXX`: C++ compiler for native tools (default: `g++` on Linux, `clang++` on macOS/FreeBSD/OpenBSD)
```
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541624816)
```suggestion
- `build_CC`: C compiler for native tools (default: `gcc` on Linux, `clang` on macOS/FreeBSD/OpenBSD)
- `build_CXX`: C++ compiler for native tools (default: `g++` on Linux, `clang++` on macOS/FreeBSD/OpenBSD)
```
π¬ hebasto commented on pull request "Document compiler configuration for native depends packages":
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541630314)
```suggestion
You might want to override native tool compilers when your default build compiler (set in `./depends/builders/*.mk`) is not available. For example, when using a Linux host without gcc/g++.
```
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541630314)
```suggestion
You might want to override native tool compilers when your default build compiler (set in `./depends/builders/*.mk`) is not available. For example, when using a Linux host without gcc/g++.
```
π¬ hebasto commented on pull request "Document compiler configuration for native depends packages":
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541632430)
```suggestion
Example using Clang for native build tools on Linux:
```
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541632430)
```suggestion
Example using Clang for native build tools on Linux:
```
π€ l0rinc reviewed a pull request: "ci: Make the max number of commits tested explicit"
(https://github.com/bitcoin/bitcoin/pull/33909#pullrequestreview-3482229939)
I didn't realize this, so concept ACK.
I wouldn't include the value of a variable in the variable's name, though, and I think the job's name should likely also be updated - left a suggestion
(https://github.com/bitcoin/bitcoin/pull/33909#pullrequestreview-3482229939)
I didn't realize this, so concept ACK.
I wouldn't include the value of a variable in the variable's name, though, and I think the job's name should likely also be updated - left a suggestion
π¬ l0rinc commented on pull request "ci: Make the max number of commits tested explicit":
(https://github.com/bitcoin/bitcoin/pull/33909#discussion_r2541635179)
6 is an implementation detail, the high-level point is to signal that not every commit is checked, but that the last few commits in the current PR are.
Also, the job's name should also likely be adjusted, maybe `ci-test-each-commit-exec.py` as well:
```suggestion
test-latest-commits:
name: 'test latest commits'
```
(https://github.com/bitcoin/bitcoin/pull/33909#discussion_r2541635179)
6 is an implementation detail, the high-level point is to signal that not every commit is checked, but that the last few commits in the current PR are.
Also, the job's name should also likely be adjusted, maybe `ci-test-each-commit-exec.py` as well:
```suggestion
test-latest-commits:
name: 'test latest commits'
```
π¬ fanquake commented on pull request "depends: Add patch for Windows11Style plugin":
(https://github.com/bitcoin/bitcoin/pull/33906#issuecomment-3552230525)
Can we just update Qt?
(https://github.com/bitcoin/bitcoin/pull/33906#issuecomment-3552230525)
Can we just update Qt?
β οΈ johnsonella2208-oss opened an issue: "Mighty Hacker Recovery Hope for Support Available for Your Ethereum/Crypto/Asset Recovery Case/ Private Wallet Key"
(https://github.com/bitcoin/bitcoin/issues/33910)
### Motivation
**Mighty Hacker Recovery Hope for Support Available for Your Ethereum/Crypto/Asset Recovery Case/ Private Wallet Key**
### Possible solution
**Mighty Hacker Recovery Hope for Support Available for Your Ethereum/Crypto/Asset Recovery Case/ Private Wallet Key**
### Useful Skills
* Compiling Bitcoin Core from source
* Running the C++ unit tests and the Python functional tests
* ...
### Guidance for new contributors
Want to work on this issue?
For guidance on contributing, pl
...
(https://github.com/bitcoin/bitcoin/issues/33910)
### Motivation
**Mighty Hacker Recovery Hope for Support Available for Your Ethereum/Crypto/Asset Recovery Case/ Private Wallet Key**
### Possible solution
**Mighty Hacker Recovery Hope for Support Available for Your Ethereum/Crypto/Asset Recovery Case/ Private Wallet Key**
### Useful Skills
* Compiling Bitcoin Core from source
* Running the C++ unit tests and the Python functional tests
* ...
### Guidance for new contributors
Want to work on this issue?
For guidance on contributing, pl
...
π¬ hebasto commented on pull request "depends: Add patch for Windows11Style plugin":
(https://github.com/bitcoin/bitcoin/pull/33906#issuecomment-3552247066)
> Can we just update Qt?
Updating Qt would require raising the minimum GCC version for Windows cross-compilation to [13.1](https://doc.qt.io/qt-6.8/supported-platforms.html#windows). Are we comfortable with that?
(https://github.com/bitcoin/bitcoin/pull/33906#issuecomment-3552247066)
> Can we just update Qt?
Updating Qt would require raising the minimum GCC version for Windows cross-compilation to [13.1](https://doc.qt.io/qt-6.8/supported-platforms.html#windows). Are we comfortable with that?
π¬ willcl-ark commented on pull request "Document compiler configuration for native depends packages":
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541662001)
I agree, but going to leave that from this PR for now.
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541662001)
I agree, but going to leave that from this PR for now.
π¬ willcl-ark commented on pull request "Document compiler configuration for native depends packages":
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541662319)
Taken in 75155c073d7
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541662319)
Taken in 75155c073d7
π¬ willcl-ark commented on pull request "Document compiler configuration for native depends packages":
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541662701)
Taken in 75155c073d7
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541662701)
Taken in 75155c073d7
π¬ willcl-ark commented on pull request "Document compiler configuration for native depends packages":
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541662993)
Taken in 75155c073d7
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541662993)
Taken in 75155c073d7
π hebasto approved a pull request: "Document compiler configuration for native depends packages"
(https://github.com/bitcoin/bitcoin/pull/33902#pullrequestreview-3482268948)
re-ACK 7dd714ae71fd18eda82ab4b43d4cecc047b87a2d.
(https://github.com/bitcoin/bitcoin/pull/33902#pullrequestreview-3482268948)
re-ACK 7dd714ae71fd18eda82ab4b43d4cecc047b87a2d.
π¬ willcl-ark commented on pull request "Document compiler configuration for native depends packages":
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541664757)
Reolving this based on wording in 75155c073d7.
(https://github.com/bitcoin/bitcoin/pull/33902#discussion_r2541664757)
Reolving this based on wording in 75155c073d7.
π¬ janb84 commented on pull request "ci: Make the max number of commits tested explicit":
(https://github.com/bitcoin/bitcoin/pull/33909#issuecomment-3552252907)
> Also, the title seems the wrong place to list all the shortcomings of each CI task. For example, the win-cross does not build the gui tests, should it say 'no-gui-tests'? Or the arm test has `-Wno-error=maybe-uninitialized`, so should the title say 'no-error-uninit'? Some tasks do not have `CI_LIMIT_STACK_SIZE` set, some tasks don't run the previous releases, or the extended functional tests, some have the gui disabled, no task is using gcc-15, ...
>
> Maybe it makes sense to document thi
...
(https://github.com/bitcoin/bitcoin/pull/33909#issuecomment-3552252907)
> Also, the title seems the wrong place to list all the shortcomings of each CI task. For example, the win-cross does not build the gui tests, should it say 'no-gui-tests'? Or the arm test has `-Wno-error=maybe-uninitialized`, so should the title say 'no-error-uninit'? Some tasks do not have `CI_LIMIT_STACK_SIZE` set, some tasks don't run the previous releases, or the extended functional tests, some have the gui disabled, no task is using gcc-15, ...
>
> Maybe it makes sense to document thi
...