< GitHub91>
[bitcoin] luke-jr opened pull request #8687: Bugfix: RPC/Wallet: removeprunedfunds should flush the wallet db (master...bugfix_removeprunedfunds) https://github.com/bitcoin/bitcoin/pull/8687
< gmaxwell>
and it also means you couldn't use bitcoin anymore on a connection of less than about 50kbit/sec which, otherwise, could keep up with the chain.
< GitHub48>
[bitcoin] laanwj closed pull request #8677: Do not shadow upper local variable 'send', prevent -Wshadow compiler warning. (master...20160907_Wshadow_8606) https://github.com/bitcoin/bitcoin/pull/8677
< GitHub33>
bitcoin/master 125b946 Pavel Janík: Do not shadow upper local variable 'send', prevent -Wshadow compiler warning.
< GitHub33>
bitcoin/master 4daf02a Wladimir J. van der Laan: Merge #8677: Do not shadow upper local variable 'send', prevent -Wshadow compiler warning....
< CodeShark>
in my ideal world, Bitcoin Core would just do peer discovery, validation, and relay
< CodeShark>
I have a process connect to bitcoin core via p2p which receives inv messages and sends getdata
< midnightmagic>
it should then be in an external library. putting reliable message delivery into bitcoin core would also make the binary liable in the event something (inevitably) goes wrong.
2016-09-08
< BlueMatt>
sipa: https://github.com/TheBlueMatt/bitcoin/commit/96cef326f9184aefd1c562f64a21298a15f0adde simplifies the total diff from master to be more readable, to me...it matches the bip, but another way to look at it is that you have two booleans: which version of compact blocks they want (which you use to send to them) and whether they will send us segwit cmpctblocks...you simply introduce the the do-they-support-v2 bool as an additional
< cfields>
kanzure: and #8680 introduces blocking calls. So you could "./bitcoin-cli waitfornewblock && ./dosomething.sh", which would essentially be blocknotify. Obviously the same could be done for wallet stuff
< kanzure>
so- for example- imagine you are operating a lot of bitcoin infrastructure. you do a bunch of per-block processing. when you are running functional/integration tests, you can't run your test checks immediately after issuing a command because things take a while. so when do you expect to run? well you setup a hook and you ask your infrastructure to ping your tester as soon as the data's available, or you poll for some internal state.
< wumpus>
/home/user/projects/bitcoin/bitcoin/src/test/addrman_tests.cpp:336:471: warning: stack frame size of 328360 bytes in function 'addrman_tests::addrman_delete::test_method' [-Wframe-larger-than=] whoa :) luckily only in the tests
< wumpus>
let's try to make cfields network refactor (https://github.com/bitcoin/bitcoin/pull/8085/files) happen , it's been open so long now, line-wise there's a lot of changes so he keeps having to rebase it
< veleiro>
Im trying to build v0.13.0 from source on a beaglebone black with debian jessie, i had to compile db4.8 from source but i installed libboost-all-dev, but in the ./configure stage the error i see is "configure: error: No working boost sleep implementation found." I went through https://github.com/bitcoin/bitcoin/issues/3003 with no success
< Chris_Stewart_5>
jeremyrubin: With your new pull request (#8670), are you suggesting writing a new testing framework specific to bitcoin from scratch?
< GitHub128>
[bitcoin] MarcoFalke closed pull request #8673: Trivial: Fix obvious assignment/equality error in test (master...fix_arith_tests_trivial) https://github.com/bitcoin/bitcoin/pull/8673
< GitHub150>
[bitcoin] jonasschnelli opened pull request #8678: [Qt][CoinControl] fix UI bug that could result in paying unexpected fee (master...2016/09/qt_cc_ui_radrio_fix) https://github.com/bitcoin/bitcoin/pull/8678
< GitHub136>
[bitcoin] paveljanik opened pull request #8677: Do not shadow upper local variable 'send', prevent -Wshadow compiler warning. (master...20160907_Wshadow_8606) https://github.com/bitcoin/bitcoin/pull/8677
< GitHub122>
[bitcoin] JeremyRubin opened pull request #8673: Trivial: Fix obvious assignment/equality error in test (master...fix_arith_tests_trivial) https://github.com/bitcoin/bitcoin/pull/8673
< GitHub82>
[bitcoin] JeremyRubin closed pull request #8632: Speed up prevector tests by parallelization (master...faster_prevector_tests) https://github.com/bitcoin/bitcoin/pull/8632
< GitHub172>
[bitcoin] JeremyRubin closed pull request #8650: Make tests much faster by replacing BOOST_CHECK with FAST_CHECK (master...faster_tests) https://github.com/bitcoin/bitcoin/pull/8650
< GitHub186>
[bitcoin] Cocosoft opened pull request #8672: Qt: Show transaction size in transaction details window (master...qttxsizeindetails) https://github.com/bitcoin/bitcoin/pull/8672
< GitHub117>
[bitcoin] JeremyRubin opened pull request #8671: Minimal fix to slow prevector tests as stopgap measure (master...simple_faster_tests) https://github.com/bitcoin/bitcoin/pull/8671
< sipa>
the bitcoin and libsecp256k1 benchmark tools just run many times, and give you minimum, maximum and average run time
2016-09-05
< BlueMatt>
general fyi: book your accomodation to wed, if you feel like sticking around to do in-person Bitcoin Core code review/hacking just like the last few times
< BlueMatt>
ie another core hackathon after scaling bitcoin: milan, monday and tuesday
< BlueMatt>
but I dont particularly want to have /the/ key that can sign for lots of updated bitcoin-qt clients
< Lightsword>
could just stick it on bitcoin.org
< BlueMatt>
kanzure: people with their heads on straight are correctly avoiding ubuntu for their bitcoin node hosting, I'd think
< BlueMatt>
bitcoin.org maybe, but I'd prefer to not put it there
< GitHub176>
[bitcoin] NicolasDorier opened pull request #8665: Trivial: ContextualCheckBlockHeader should never have pindexPrev equals to NULL (master...fixup) https://github.com/bitcoin/bitcoin/pull/8665
< GitHub142>
[bitcoin] fivepiece closed pull request #8598: Fix displaying of invalid and non-minimal small pushes as numbers (master...fixasm) https://github.com/bitcoin/bitcoin/pull/8598
< sipa>
but that probably means in practice we can't use it in bitcoin core until 2024 or so :p
< gmaxwell>
In the case of bitcoin the cookie auth is an ephemeral username and password, saved in a cookie file, which can be used for HTTP authentication.
2016-09-03
< GitHub3>
[bitcoin] gmaxwell opened pull request #8661: Do not set an addr time penalty when a peer advertises itself. (master...addrman_nopenalty_self) https://github.com/bitcoin/bitcoin/pull/8661
< GitHub70>
[bitcoin] paveljanik opened pull request #8658: WIP/DO NOT MERGE: Remove unused statements in serialization (master...20160902_nVersion_serialization_cleanup) https://github.com/bitcoin/bitcoin/pull/8658
< GitHub12>
[bitcoin] paveljanik opened pull request #8656: Do not shadow global variable fileout (master...20160902_Wshadow_fileout) https://github.com/bitcoin/bitcoin/pull/8656
< GitHub78>
[bitcoin] paveljanik opened pull request #8655: Do not shadow variables (trivials) (master...20160902_Wshadow_trivials) https://github.com/bitcoin/bitcoin/pull/8655
< GitHub85>
[bitcoin] jl2012 opened pull request #8654: Reuse sighash computations across evaluation (rebase of #4562) (master...sighashcache) https://github.com/bitcoin/bitcoin/pull/8654
< jonasschnelli>
2016-09-02 07:56:40 Bitcoin version v0.13.99.0-df98230
< GitHub117>
[bitcoin] sstone opened pull request #8653: doc (trivial): add tip for cross-builds on ubuntu (master...wip-doccrosscompile) https://github.com/bitcoin/bitcoin/pull/8653
< GitHub186>
[bitcoin] JeremyRubin opened pull request #8650: Make tests much faster by replacing BOOST_CHECK with FAST_CHECK (master...faster_tests) https://github.com/bitcoin/bitcoin/pull/8650
< GitHub176>
[bitcoin] gmaxwell opened pull request #8646: [0.13 backport] Reduce default number of blocks to check at startup (0.13...reduceblocks_backport) https://github.com/bitcoin/bitcoin/pull/8646
< GitHub92>
[bitcoin] gmaxwell opened pull request #8644: [0.13 backport] Check for compatibility with download in FindNextBlocksToDownload (0.13...findnext_backport) https://github.com/bitcoin/bitcoin/pull/8644
< GitHub2>
[bitcoin] sipa closed pull request #8597: Move code from VERACK to VERSION (since VERACK is not requied) (master...NotDependentOnVerack) https://github.com/bitcoin/bitcoin/pull/8597
< warren>
I'm surprised to find that the gitian documentation in the bitcoin repo no longer explains the gitian default qemu-kvm (non-LXC) method of using make-base-vm.
< GitHub53>
[bitcoin] laanwj closed pull request #8612: Check for compatibility with download in FindNextBlocksToDownload (master...fixwitban) https://github.com/bitcoin/bitcoin/pull/8612
< GitHub127>
bitcoin/master 887919c Pieter Wuille: Check for compatibility with download in FindNextBlocksToDownload
< GitHub127>
bitcoin/master 84decb5 Wladimir J. van der Laan: Merge #8612: Check for compatibility with download in FindNextBlocksToDownload...
< murch>
sipa: I didn't get a ticket for Scaling Bitcoin unfortunately. :( I'm now hoping that my proposal will be accepted, otherwise it looks like I might not be able to go. (I'm on the waiting list.)
< murch>
sipa: I had read part of the discussion on the BIP status updates on the dev list. There was a bit about the gap limit there and I assumed that Bitcoin Core also implements BIP44.
< achow101>
the idea is that the user should be able to just start Bitcoin Core with no options (except server=1 I guess) and the software (Armory) would be able to automatically know how to connect to the server without any user input
< GitHub112>
[bitcoin] JeremyRubin opened pull request #8633: Ugly hack to print out tests as they are run to mitigate travis timeouts (master...test-driver-hack) https://github.com/bitcoin/bitcoin/pull/8633
< GitHub111>
[bitcoin] JeremyRubin opened pull request #8632: Speed up prevector tests by parallelization (master...faster_prevector_tests) https://github.com/bitcoin/bitcoin/pull/8632
< GitHub184>
[bitcoin] theuni opened pull request #8631: Nuke boost::thread and boost::thread_group (master...no-interrupt-threads) https://github.com/bitcoin/bitcoin/pull/8631