afiore has quit [Remote host closed the connection]
afiore has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] musaHaruna opened pull request #35970: Test persisted health requires mempool restore (master...test-persisted-health-requires-mempool-restore) https://github.com/bitcoin/bitcoin/pull/35970
<bitcoin-git>
[bitcoin] musaHaruna closed pull request #35970: Test persisted health requires mempool restore (master...test-persisted-health-requires-mempool-restore) https://github.com/bitcoin/bitcoin/pull/35970
conman has quit [Quit: Konversation terminated!]
conman has joined #bitcoin-core-dev
diego has left #bitcoin-core-dev [#bitcoin-core-dev]
<bitcoin-git>
bitcoin/master a3597e2 Martin Zumsande: test: move BuildChain helper into test mining util
<bitcoin-git>
bitcoin/master 2232d6a Martin Zumsande: test: move index_reorg_crash to baseindex_tests
<bitcoin-git>
[bitcoin] fanquake merged pull request #35847: test: move more tests to `baseindex_tests` and run them for all indexes (master...202607_baseindex_tests) https://github.com/bitcoin/bitcoin/pull/35847
PaperSword has quit [Read error: Connection reset by peer]
jerryf has quit [Remote host closed the connection]
<l0rinc>
bitcoindev1337: I have reproduced the speedup with IBD as well now - 20% faster on a HDD. Excellent finding!
<pinheadmz>
any macOS devs using cmake 4.3 or greater? They changed FindSQLite3 and it looks like it's injecting the macOS SDK usr/include as a system include, which breaks clang/libc++ header ordering. Effect is brilliant errors like "error: unknown type name '__uint32_t'"... for me the fix was adding -DSQLite3_ROOT="$(brew --prefix sqlite)"
<l0rinc>
I always had that on local non-Apple clang
<pinheadmz>
i.e. forcing the compiler to use the homebrew sqlite instead of make 4.3 looking for it in the system shit, and pulling in all the system headers too early
<pinheadmz>
i only pulled cmake 4.4 this week
<pinheadmz>
we could add something to cmakelists.txt to avoid MacOSX.sdk for sqlite @hebasto ?
<bitcoin-git>
[bitcoin] sedited opened pull request #35976: test: Speedup fee estimation functional test with batching (master...fee_estimation_test_speedup) https://github.com/bitcoin/bitcoin/pull/35976
uqlidi54 has joined #bitcoin-core-dev
uqlidi5 has quit [Read error: Connection reset by peer]
greypw1495085720 has quit [Remote host closed the connection]
greypw1495085720 has joined #bitcoin-core-dev
jonatack has joined #bitcoin-core-dev
___nick___ has joined #bitcoin-core-dev
<_aj_>
are we using co-author to mean "wrote some of the code in this commit" or "contributed to the design" these days? i thought the former, but i've seen a few cases where the latter seems to be more in play? does the distinction matter for some people's grant KPIs?
uqlidi54 has quit [Read error: Connection reset by peer]
uqlidi547 has joined #bitcoin-core-dev
jerryf has quit [Remote host closed the connection]