fanquake

Results 616 comments of fanquake

> Aha! I think this describes the problem exactly. Disabling fullfsync gets us the performance of using system sqlite. The question is whether it is safe for us to do...

p2p_ping is now failing: ```bash 222/251 - p2p_ping.py failed, Duration: 1 s stdout: 2022-09-14T10:06:23.895000Z TestFramework (INFO): Initializing test directory /tmp/cirrus-ci-build/ci/scratch/test_runner/test_runner_₿_🏃_20220914_095106/p2p_ping_26 2022-09-14T10:06:24.156000Z TestFramework (INFO): Check that ping is sent after connection...

If there are any more changes can you pull them in here. Planning on merging this shortly.

> It was added because otherwise static builds don't work If users need it for static builds, they can/should at it to their own link flags. It looks like it...

Note that this also breaks builds in a second way. If you're linking with gcc and `-static-libstdc++` you'll get the bogus `-lstdc++` on your link line, which undermines the `-static-libstdc++`...

I've marked branch-off as complete (bringing the date forward to today, and pushing release aim back a day). There is now a tag for `v24.0rc1`: https://github.com/bitcoin/bitcoin/releases/tag/v24.0rc1.

Binaries for 24.0rc1 are now available: https://bitcoincore.org/bin/bitcoin-core-24.0/test.rc1/. I've also created a testing issue here: https://github.com/bitcoin/bitcoin/issues/26175. > Is a 23.1 release planned as well or is it unnecessary? A 23.1 release...

@t-bast note that a 23.1 release candidate has now been tagged: https://github.com/bitcoin/bitcoin/releases/tag/v23.1rc1.

v24.0 has now been tagged: https://github.com/bitcoin/bitcoin/releases/tag/v24.0.