π¬ fanquake commented on pull request "build: Require libc++-16 or later":
(https://github.com/bitcoin/bitcoin/pull/29077#issuecomment-1856394358)
> and OSS-Fuzz?
So won't this break as soon as we have code that requires libstdc++-16, given that OSS-Fuzz is still pinned to 15?
Are there no other projects using (some?) C++20 code on OSS-Fuzz?
(https://github.com/bitcoin/bitcoin/pull/29077#issuecomment-1856394358)
> and OSS-Fuzz?
So won't this break as soon as we have code that requires libstdc++-16, given that OSS-Fuzz is still pinned to 15?
Are there no other projects using (some?) C++20 code on OSS-Fuzz?
π¬ theuni commented on pull request "refactor: Remove gmtime*":
(https://github.com/bitcoin/bitcoin/pull/29081#issuecomment-1856399535)
Finally :)
Concept ACK.
(https://github.com/bitcoin/bitcoin/pull/29081#issuecomment-1856399535)
Finally :)
Concept ACK.
π¬ achow101 commented on pull request "Make bitcoin-tx replaceable value optional":
(https://github.com/bitcoin/bitcoin/pull/29022#issuecomment-1856400401)
ACK 98afe7866185ed4157ffc581763e11dc02fcbae0
(https://github.com/bitcoin/bitcoin/pull/29022#issuecomment-1856400401)
ACK 98afe7866185ed4157ffc581763e11dc02fcbae0
π achow101 merged a pull request: "Make bitcoin-tx replaceable value optional"
(https://github.com/bitcoin/bitcoin/pull/29022)
(https://github.com/bitcoin/bitcoin/pull/29022)
β
achow101 closed an issue: "bitcoin-tx replaceable value should be optional, but isn't"
(https://github.com/bitcoin/bitcoin/issues/28638)
(https://github.com/bitcoin/bitcoin/issues/28638)
π¬ theuni commented on pull request "refactor: Remove gmtime*":
(https://github.com/bitcoin/bitcoin/pull/29081#issuecomment-1856412027)
> util/time.cpp:60:24: error: βyear_month_dayβ in namespace βstd::chronoβ does not name a type
It would have been too easy if it had just worked in the real world :p
(https://github.com/bitcoin/bitcoin/pull/29081#issuecomment-1856412027)
> util/time.cpp:60:24: error: βyear_month_dayβ in namespace βstd::chronoβ does not name a type
It would have been too easy if it had just worked in the real world :p
π¬ maflcko commented on pull request "refactor: Remove gmtime*":
(https://github.com/bitcoin/bitcoin/pull/29081#issuecomment-1856419623)
Jup, a bump to g++-11 should be fine, but currently not possible because the guix build is still on g++-10 π«
(https://github.com/bitcoin/bitcoin/pull/29081#issuecomment-1856419623)
Jup, a bump to g++-11 should be fine, but currently not possible because the guix build is still on g++-10 π«
π¬ furszy commented on pull request "fuzz: coinselection, improve `min_viable_change`/`change_output_size`":
(https://github.com/bitcoin/bitcoin/pull/28372#issuecomment-1856422920)
> So, instead of passing coin_params.m_cost_of_change and 0, we should be passing coin_params.min_viable_change and coin_params.m_change_fee. Just fixing one or the other was insufficient, but when I replace both all my fuzz crashes pass.
Yeah, thats good.
It is because `cost_of_change`, the BnB upper bound, includes `change_fee` while `min_viable_change` does not.
(https://github.com/bitcoin/bitcoin/pull/28372#issuecomment-1856422920)
> So, instead of passing coin_params.m_cost_of_change and 0, we should be passing coin_params.min_viable_change and coin_params.m_change_fee. Just fixing one or the other was insufficient, but when I replace both all my fuzz crashes pass.
Yeah, thats good.
It is because `cost_of_change`, the BnB upper bound, includes `change_fee` while `min_viable_change` does not.
π¬ fanquake commented on pull request "guix: use GCC 12.3.0 to build releases":
(https://github.com/bitcoin/bitcoin/pull/27897#issuecomment-1856423621)
Yes, iirc. I'll get back to this now that it's becoming more of a blocker. I've bed sick of continually dealing with/having to track dow problems in gui and similar non-critical code, when it comes to these kinds changes.
(https://github.com/bitcoin/bitcoin/pull/27897#issuecomment-1856423621)
Yes, iirc. I'll get back to this now that it's becoming more of a blocker. I've bed sick of continually dealing with/having to track dow problems in gui and similar non-critical code, when it comes to these kinds changes.
π¬ mzumsande commented on pull request "p2p: attempt to fill full outbound connection slots with peers that support tx relay":
(https://github.com/bitcoin/bitcoin/pull/28538#discussion_r1427157449)
done
(https://github.com/bitcoin/bitcoin/pull/28538#discussion_r1427157449)
done
π¬ mzumsande commented on pull request "p2p: attempt to fill full outbound connection slots with peers that support tx relay":
(https://github.com/bitcoin/bitcoin/pull/28538#issuecomment-1856427821)
[d636e38 ](https://github.com/bitcoin/bitcoin/commit/d636e38d79a4c3950da91090b1f787163f11e24d)to 2a17ac3:
Renamed `GetExtraFullOutboundCount` to `GetFullOutboundDelta` since it can now return negative values, plust small doc change in the test.
(https://github.com/bitcoin/bitcoin/pull/28538#issuecomment-1856427821)
[d636e38 ](https://github.com/bitcoin/bitcoin/commit/d636e38d79a4c3950da91090b1f787163f11e24d)to 2a17ac3:
Renamed `GetExtraFullOutboundCount` to `GetFullOutboundDelta` since it can now return negative values, plust small doc change in the test.
π¬ mzumsande commented on pull request "p2p: attempt to fill full outbound connection slots with peers that support tx relay":
(https://github.com/bitcoin/bitcoin/pull/28538#discussion_r1427158995)
done now!
(https://github.com/bitcoin/bitcoin/pull/28538#discussion_r1427158995)
done now!
π¬ achow101 commented on pull request "test: add TestNode wait_until helper":
(https://github.com/bitcoin/bitcoin/pull/29070#issuecomment-1856431717)
ACK bf0f7dbec6590a54ec890e7a2ca5d85427995334
(https://github.com/bitcoin/bitcoin/pull/29070#issuecomment-1856431717)
ACK bf0f7dbec6590a54ec890e7a2ca5d85427995334
π achow101 merged a pull request: "test: add TestNode wait_until helper"
(https://github.com/bitcoin/bitcoin/pull/29070)
(https://github.com/bitcoin/bitcoin/pull/29070)
β
achow101 closed an issue: "test: Add TestNode wait_until helper"
(https://github.com/bitcoin/bitcoin/issues/29029)
(https://github.com/bitcoin/bitcoin/issues/29029)
π€ furszy reviewed a pull request: "fuzz: coinselection, improve `min_viable_change`/`change_output_size`"
(https://github.com/bitcoin/bitcoin/pull/28372#pullrequestreview-1782561357)
Left a comment
(https://github.com/bitcoin/bitcoin/pull/28372#pullrequestreview-1782561357)
Left a comment
π¬ furszy commented on pull request "fuzz: coinselection, improve `min_viable_change`/`change_output_size`":
(https://github.com/bitcoin/bitcoin/pull/28372#discussion_r1427177813)
> This will narrow down the range of output sizes being fuzzed.
Agree.
You don't need to create valid known destinations, we only care about the change output size. All yours:
```diff
diff --git a/src/wallet/test/fuzz/coinselection.cpp b/src/wallet/test/fuzz/coinselection.cpp
--- a/src/wallet/test/fuzz/coinselection.cpp (revision ccb25a1ddc1f79f432a6718604f01ed97dced15f)
+++ b/src/wallet/test/fuzz/coinselection.cpp (date 1702581796902)
@@ -11,6 +11,7 @@
#include <test/util/setup_commo
...
(https://github.com/bitcoin/bitcoin/pull/28372#discussion_r1427177813)
> This will narrow down the range of output sizes being fuzzed.
Agree.
You don't need to create valid known destinations, we only care about the change output size. All yours:
```diff
diff --git a/src/wallet/test/fuzz/coinselection.cpp b/src/wallet/test/fuzz/coinselection.cpp
--- a/src/wallet/test/fuzz/coinselection.cpp (revision ccb25a1ddc1f79f432a6718604f01ed97dced15f)
+++ b/src/wallet/test/fuzz/coinselection.cpp (date 1702581796902)
@@ -11,6 +11,7 @@
#include <test/util/setup_commo
...
π¬ theuni commented on pull request "[WIP, DO NOT MERGE!!11111!!!!!] build: Require libc++-16 or later":
(https://github.com/bitcoin/bitcoin/pull/29077#discussion_r1427188598)
More missing in v10: https://github.com/bitcoin/bitcoin/pull/29081#issuecomment-1856419623
(https://github.com/bitcoin/bitcoin/pull/29077#discussion_r1427188598)
More missing in v10: https://github.com/bitcoin/bitcoin/pull/29081#issuecomment-1856419623
β οΈ LeoSpyke opened an issue: "test: feature_index_prune.py timeout failure"
(https://github.com/bitcoin/bitcoin/issues/29082)
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behaviour
The `test/functional/test_runner.py --extended --jobs=8` command raises an `AssertionError: Block sync timed out after 60s` when running the `feature_index_prune.py` suite.
Also tried with `--jobs=4`.
Very similar to #27091.
### Expected behaviour
I expected the test to complete successfully.
### Steps to reproduce
```bash
git clone https://github.com/bitcoin/bitcoin
# instal
...
(https://github.com/bitcoin/bitcoin/issues/29082)
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behaviour
The `test/functional/test_runner.py --extended --jobs=8` command raises an `AssertionError: Block sync timed out after 60s` when running the `feature_index_prune.py` suite.
Also tried with `--jobs=4`.
Very similar to #27091.
### Expected behaviour
I expected the test to complete successfully.
### Steps to reproduce
```bash
git clone https://github.com/bitcoin/bitcoin
# instal
...
π¬ maflcko commented on issue "test: `feature_index_prune.py` timeout failure":
(https://github.com/bitcoin/bitcoin/issues/29082#issuecomment-1856485017)
Does it pass if you increase the timeout factor? See `./test/functional/test_runner.py --help | grep factor`?
(https://github.com/bitcoin/bitcoin/issues/29082#issuecomment-1856485017)
Does it pass if you increase the timeout factor? See `./test/functional/test_runner.py --help | grep factor`?