< jtimon> BlueMatt: I don't have much experience with python asynchronous stuff without zmq/nanomsg, wouldn't touch lower level sockets in python :p
< jtimon> unless you're running some weird high performance experiment on pypy or something
< bitcoin-git> [bitcoin] pstratem opened pull request #9716: [Net] Clarity TIMEOUT_INTERVAL constant meaning. (master...2017-02-07-ping-timeout-interval) https://github.com/bitcoin/bitcoin/pull/9716
< bitcoin-git> [bitcoin] jtimon opened pull request #9717: Pow: Remove fCheckPOW from CheckBlockHeader (master...pre-0.14-dont-call-me) https://github.com/bitcoin/bitcoin/pull/9717
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/b709fe7ffc44...d304fef37460
< bitcoin-git> bitcoin/master 29c5328 Wladimir J. van der Laan: bench: Fix initialization order in registration...
< bitcoin-git> bitcoin/master d304fef MarcoFalke: Merge #9712: bench: Fix initialization order in registration...
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #9712: bench: Fix initialization order in registration (master...2017_02_fiasco) https://github.com/bitcoin/bitcoin/pull/9712
< bitcoin-git> [bitcoin] luke-jr opened pull request #9718: Qt/Intro: Various fixes (master...intro_fixes) https://github.com/bitcoin/bitcoin/pull/9718
< bitcoin-git> [bitcoin] rebroad opened pull request #9719: Allow abortion of ConnectBlock() when shutdown requested. (master...AbortConnectBlockAtShutdown) https://github.com/bitcoin/bitcoin/pull/9719
< bitcoin-git> [bitcoin] theuni opened pull request #9720: net: fix banning and disallow sending messages before receiving verack (master...fix-ban) https://github.com/bitcoin/bitcoin/pull/9720
< bitcoin-git> [bitcoin] rebroad opened pull request #9721: Headers announcement for nodes that can do headers. (master...AnnounceUsingHeaders) https://github.com/bitcoin/bitcoin/pull/9721
< bitcoin-git> [bitcoin] CryptAxe opened pull request #9722: GUI: Display warning when attempting address reuse (master...reuse) https://github.com/bitcoin/bitcoin/pull/9722
< divyang> hello
< bitcoin-git> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/d304fef37460...6a55515a9b8f
< bitcoin-git> bitcoin/master 8713de8 Wladimir J. van der Laan: build: Add options to override BDB cflags/libs...
< bitcoin-git> bitcoin/master 5cc2ebb Wladimir J. van der Laan: Update OpenBSD and FreeBSD build steps...
< bitcoin-git> bitcoin/master 6a55515 Wladimir J. van der Laan: Merge #9705: build: Add options to override BDB cflags/libs...
< bitcoin-git> [bitcoin] laanwj closed pull request #9705: build: Add options to override BDB cflags/libs (master...2017_02_bdb_location) https://github.com/bitcoin/bitcoin/pull/9705
< bitcoin-git> [bitcoin] laanwj pushed 5 new commits to master: https://github.com/bitcoin/bitcoin/compare/6a55515a9b8f...dd163f578869
< bitcoin-git> bitcoin/master fd13eca Matt Corallo: Lock cs_vSend and cs_inventory in a consistent order even in TRY
< bitcoin-git> bitcoin/master 8465631 Matt Corallo: Always enforce lock strict lock ordering (try or not)
< bitcoin-git> bitcoin/master 2a962d4 Matt Corallo: Fixup style a bit by moving { to the same line as if statements
< bitcoin-git> [bitcoin] laanwj closed pull request #9674: Always enforce strict lock ordering (try or not) (master...2017-02-inv-send-lockorder) https://github.com/bitcoin/bitcoin/pull/9674
< udiWertheimer> Hey, Udi from Colu here, maintainers of the coloredcoins.org protocol. We are looking to start devoting some dev time to contribute to Bitcoin Core (just wherever we can help, not related to colored coins development).
< Chris_Stewart_5> udiWertheimer: Awesome!
< udiWertheimer> first steps I'm thinking of is getting to know the project and helping with reviewing open pull requests, then probably look for small open issues to work on, or missing tests. wondered if you guys have any suggestions for getting started?
< achow101> udiWertheimer: look through the PRs page and see what you can review. take a look at what the current issues are and see if there is anything you can do with some of the open issues.
< Chris_Stewart_5> If you haven't read already: https://github.com/bitcoin/bitcoin/blob/master/doc/developer-notes.md
< achow101> also, since the 0.14 release cycle is currently upon us, it would be nice if you could review the PRs in https://github.com/bitcoin/bitcoin/milestone/21
< achow101> (that's the 0.14 milestone)
< udiWertheimer> gotcha. thanks
< BlueMatt> ok, so it looks like all the last-minute race testing is starting to clean up, but that means we need review to get 0.14 branched and rc1 out the door.... https://github.com/bitcoin/bitcoin/milestone/21 has the list, plus #9708 would be nice
< gribble> https://github.com/bitcoin/bitcoin/issues/9708 | Clean Up all known races/platform-specific UB by TheBlueMatt · Pull Request #9708 · bitcoin/bitcoin · GitHub
< luke-jr> is github broken? it doesn't seem to be accepting my forcepush
< cdecker> luke-jr: protected branch?
< luke-jr> cdecker: it let me push, but it isn't updating the PR
< luke-jr> wasn't*.. finally did
< cdecker> Oh yeah, I noticed some lag upon push as well
< luke-jr> 9718 looks good to go for 0.14 now
< bitcoin-git> [bitcoin] luke-jr opened pull request #9724: Qt/Intro: Add explanation of IBD process (master...intro_explain) https://github.com/bitcoin/bitcoin/pull/9724
< cfields> BlueMatt: want me to just close 9695? as far as i can tell it's just a dupe now
< BlueMatt> cfields: meh, whatever, the point of splitting them is in case people complain about the copies in 9708 we can just merge 9707 and deal with it separately
< luke-jr> BlueMatt: could your size be rounded up based on filesystem overhead?
< BlueMatt> luke-jr: unless ext4+du rounds up a shitload?
< BlueMatt> i mean it is many files
< BlueMatt> but I think the const should incl reasonable overhead in any case?
< luke-jr> du --apparent-size ?
< BlueMatt> du -hs
< luke-jr> try with --apparent-size
< luke-jr> also, is -h using SI or 1024-based?
< BlueMatt> no idea
< sipa> 109 GiB here, or 117 GB
< BlueMatt> heh, that would do it
< sipa> including chainstate and undo data
< BlueMatt> oh
< BlueMatt> oh, yes
< sipa> which we should include, i think
< sipa> undo data is 10%
< luke-jr> so = 120?
< sipa> du by default is 1024-based, unless you pass --si
< BlueMatt> yes, 120
< luke-jr> sipa: note chainstate is a separate number used also when pruning is enabled
< sipa> ok
< BlueMatt> i mean whatever, just has to be reasonable rounded up
< BlueMatt> 120 sounds good
< BlueMatt> fine
< sipa> oh, my numbers exclude chainstate
< sipa> sorry
< sipa> but include undo data
< sipa> 120 sounds good
< luke-jr> sipa: does -prune limit undo data?
< luke-jr> I guess so
< sipa> it also deletes undo data, yes
< sipa> and the ratio between blocks and undo data is pretty much constant
< bitcoin-git> [bitcoin] TheBlueMatt opened pull request #9725: CValidationInterface Cleanups (master...2017-01-wallet-cache-inmempool-1) https://github.com/bitcoin/bitcoin/pull/9725
< BlueMatt> is it a supported feature that if you do a getmempoolentry/getrawmempool/etc and a transaction shows up which applies to your wallet, a later call (immediately thereafter) to getbalance will show the balance including that transaction?
< BlueMatt> or is it only supported that sendrawtransaction followed by a getbalance/listtransactions/etc/etc will be consistent?