< gribble>
https://github.com/bitcoin/bitcoin/issues/7522 | Bugfix: Only use git for build info if the repository is actually the right one by luke-jr · Pull Request #7522 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] fanquake merged pull request #18743: depends: Add --sysroot option to mac os native compile flags (master...pr/sysroot) https://github.com/bitcoin/bitcoin/pull/18743
< bitcoin-git>
bitcoin/master 56611b0 fanquake: Merge #18743: depends: Add --sysroot option to mac os native compile flags...
< bitcoin-git>
bitcoin/master 1e94a2b Russell Yanofsky: depends: Add --sysroot option to mac os native compile flags
< gribble>
https://github.com/bitcoin/bitcoin/issues/7522 | Bugfix: Only use git for build info if the repository is actually the right one by luke-jr · Pull Request #7522 · bitcoin/bitcoin · GitHub
< gribble>
https://github.com/bitcoin/bitcoin/issues/18902 | Bugfix: Only use git for build info if the repository is actually the right one by luke-jr · Pull Request #18902 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] luke-jr opened pull request #18902: Bugfix: Only use git for build info if the repository is actually the right one (master...fix_gitdir_again) https://github.com/bitcoin/bitcoin/pull/18902
2020-05-06
< bitcoin-git>
[bitcoin] brakmic opened pull request #18901: fuzz: initialize variable sep_pos to get rid of warning (master...warning-in-fuzz-tests) https://github.com/bitcoin/bitcoin/pull/18901
< gribble>
https://github.com/bitcoin/bitcoin/issues/7522 | Bugfix: Only use git for build info if the repository is actually the right one by luke-jr · Pull Request #7522 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] jtimon closed pull request #17032: Tests: Chainparams: Make regtest almost fully customizable (master...b20-customizable-regtest) https://github.com/bitcoin/bitcoin/pull/17032
< bitcoin-git>
[bitcoin] jtimon closed pull request #17037: Testschains: Many regtests with different genesis and default datadir (master...b20-n-chains) https://github.com/bitcoin/bitcoin/pull/17037
< bitcoin-git>
[bitcoin] promag closed pull request #17457: gui: Fix manual coin control with multiple wallets loaded (master...2019-11-fix-15725) https://github.com/bitcoin/bitcoin/pull/17457
< bitcoin-git>
[bitcoin] promag opened pull request #18894: gui: Fix manual coin control with multiple wallets loaded (master...2019-11-fix-15725.2) https://github.com/bitcoin/bitcoin/pull/18894
< gribble>
https://github.com/bitcoin/bitcoin/issues/18870 | build: Allow BDB between 4.7 and 5.3 without --with-incompatible-bdb by achow101 · Pull Request #18870 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] robot-visions opened pull request #18890: test: disconnect_nodes should warn if nodes were already disconnected (master...disconnect-nodes) https://github.com/bitcoin/bitcoin/pull/18890
< jonasschnelli>
If an "tool" (like bitcoin-wallet) would allow the migration from bdb-storage to new-storage, we still would require the bdb support
< jonasschnelli>
If an storage upgrade is required for legacy wallets (which would be a no-go IMO), it could go over bitcoin-wallet (where we still need both storage backend in the code)
< gribble>
https://github.com/bitcoin/bitcoin/issues/5686 | [Wallet] replace BDB with internal append only (logdb) backend by jonasschnelli · Pull Request #5686 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] luke-jr opened pull request #18880: [0.20] wallet: Add BlockUntilSyncedToCurrentChain to dumpwallet (0.20...pr18671-0.20) https://github.com/bitcoin/bitcoin/pull/18880
< bitcoin-git>
[bitcoin] meshcollider merged pull request #18782: wallet: Make sure no DescriptorScriptPubKeyMan or WalletDescriptor members are left uninitialized after construction (master...uninitialized-members) https://github.com/bitcoin/bitcoin/pull/18782
< bitcoin-git>
bitcoin/master ec79b5f Samuel Dobson: Merge #18782: wallet: Make sure no DescriptorScriptPubKeyMan or WalletDesc...
< bitcoin-git>
bitcoin/master 2a78098 practicalswift: wallet: Make sure no WalletDescriptor members are uninitialized after cons...
< bitcoin-git>
bitcoin/master ff046ae practicalswift: wallet: Make sure no DescriptorScriptPubKeyMan members are uninitialized a...
< bitcoin-git>
[bitcoin] brakmic opened pull request #18871: rpc: prevent circular deps by extracting into separate include (master...prevent-circular-deps) https://github.com/bitcoin/bitcoin/pull/18871
< bitcoin-git>
[bitcoin] achow101 opened pull request #18870: build: Allow BDB between 4.7 and 5.3 without --with-incompatible-bdb (master...allow-other-bdb) https://github.com/bitcoin/bitcoin/pull/18870
< bitcoin-git>
[bitcoin] fanquake opened pull request #18862: Remove fdelt_chk back-compat code and sanity check (master...remove_fdelt_chk_back_compat) https://github.com/bitcoin/bitcoin/pull/18862
< bitcoin-git>
[bitcoin] sipa opened pull request #18861: Do not answer GETDATA for to-be-announced tx (master...202004_private_getdata) https://github.com/bitcoin/bitcoin/pull/18861
< vasild>
although I guess the instruction is available on all platforms where bitcoin core is being run, otherwise somebody would have reported the crash
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #18853: wallet: Fix typo in assert that is compile-time true (master...2004-walletAssertAlwaysTrue) https://github.com/bitcoin/bitcoin/pull/18853
< wumpus>
thomasb06: I'm not here for casual chat sorry, this channel is for bitcoin core development, for general chat w/ other people about bitcoin join #bitcoin
< bitcoin-git>
[bitcoin] laanwj opened pull request #18851: refactor: Replace thread_local use with a mutex-protected map (master...2020_05_replace_threadlocal) https://github.com/bitcoin/bitcoin/pull/18851
< bitcoin-git>
[bitcoin] vasild opened pull request #18843: build: warn on potentially uninitialized reads (master...enable_Wconditional-uninitialized) https://github.com/bitcoin/bitcoin/pull/18843
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #18842: wallet: Mark replaced tx to not be in the mempool anymore (master...2004-walletBumpFeeReplacedTxNoMempool) https://github.com/bitcoin/bitcoin/pull/18842
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #18840: wallet: Fully process previous RPCs before accepting new ones (master...2004-walletFullyProcessRPCs) https://github.com/bitcoin/bitcoin/pull/18840
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #18840: wallet: Fully process previous wallet calls before accepting new ones (master...2004-walletFullyProcessRPCs) https://github.com/bitcoin/bitcoin/pull/18840
< jonatack>
jnewbery: if this is an indicator, I'm not seeing any either... bitcoin-cli getpeerinfo | grep 'getblocks' | sort
< ariard>
we, Rust-Bitcoin ecosystem
< BlueMatt>
to, like, any real bitcoin use where you want to verify that something will be accepted, which is, largely, the point of libbitcoinconsensus as it exists today (given it cant do full verification)
< luke-jr>
I mean, if you really want to, you *could* just copy Bitcoin Core's test suite…
< luke-jr>
ariard: 1) regtest doesn't need any special setup; 2) I would expect every developer to have a full setup Bitcoin env anyway
< ariard>
luke-jr: you're asking people developping and testing higher stuff to have a full setup bitcoin env
< wumpus>
it might be more practical than linking against bitcoin core at compile time though :)
< luke-jr>
ariard: Bitcoin Core does testing this way; it works fine
< wumpus>
which makes me doubt this a bit in the first place, this function accepting your transaction only means that one version of bitcoin core accepted it at one point, it doesn't tell you about the current network
< luke-jr>
there is no "bitcoin core policy", there is "this node's policy" :/
< sipa>
if we expose a way to test policy, it is a "test things against current bitcoin core policy", not a "learn about all the things that may be wrong"
< sipa>
ariard: btw, bitcoin core internally also calls script verification twice to determine cause of failure (once with and once without standardness rules enabled)
< sipa>
i see no problem exposing a Bitcoin Core library that implements the same policies as Bitcoin Core; it's just a more convenient interface to do something you can already do with running a node
< wumpus>
yes, c-lightning depends on bitcoin core (at run time, not at build time)
< MarcoFalke>
ariard: Doesn't lightning depend on Bitcoin Core or a different full node impl anyway?
< bitcoin-git>
[bitcoin] MarcoFalke merged pull request #18829: ci: Merge C++17 build with one of the existing ones (master...2004-ciSpeedupCxx17) https://github.com/bitcoin/bitcoin/pull/18829
< bitcoin-git>
bitcoin/master e5b9308 MarcoFalke: Merge #18829: ci: Merge C++17 build with one of the existing ones
< bitcoin-git>
bitcoin/master aaaacff MarcoFalke: ci: Merge C++17 build with one of the existing ones
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #18829: ci: Merge C++17 build with one of the existing ones (master...2004-ciSpeedupCxx17) https://github.com/bitcoin/bitcoin/pull/18829
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #18828: test: Strip down previous releases boilerplate (master...2004-qaPreviousReleases) https://github.com/bitcoin/bitcoin/pull/18828
< bitcoin-git>
[bitcoin] MarcoFalke merged pull request #18576: test: use unittest for test_framework unit testing (master...framework-unittests) https://github.com/bitcoin/bitcoin/pull/18576
< bitcoin-git>
bitcoin/master a66ba6d MarcoFalke: Merge #18576: test: use unittest for test_framework unit testing
< bitcoin-git>
bitcoin/master de8905a Gloria Zhao: test: use unittest and test_runner for test framework unit testing