--- Day changed Thu Apr 21 2016
00:44 -!- Cory [~C@unaffiliated/cory] has quit [Ping timeout: 250 seconds]
00:47 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
00:49 -!- Cory [~C@unaffiliated/cory] has joined #bitcoin-core-dev
00:49 -!- droark [~droark@c-24-22-36-12.hsd1.or.comcast.net] has joined #bitcoin-core-dev
01:15 -!- jannes [~jannes@178.132.211.90] has joined #bitcoin-core-dev
02:40 -!- KHCkjhv [~OUYOybgP@188.25.138.138] has joined #bitcoin-core-dev
02:49 -!- jtimon [~quassel@18.29.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev
02:59 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev
02:59 -!- cryptapus_afk [~cryptapus@unaffiliated/cryptapus] has quit [Ping timeout: 268 seconds]
03:13 -!- xiangfu [~xiangfu@111.198.29.53] has quit [Remote host closed the connection]
03:23 -!- fengling [~fengling@111.198.29.53] has quit [Quit: WeeChat 1.4]
03:23 < nickler> phantomcircuit: what do you plan to fuzz?
03:28 < wumpus> all the things!!?!?!
03:28 < wumpus> I have a fuzzing branch for univalue if you want to fuzz that
03:29 < phantomcircuit> wumpus, i cant figure out a sane way to get the build system to work
03:30 < wumpus> I'll see if I can find my notes
03:35 < wumpus> phantomcircuit: first you need this branch: https://github.com/laanwj/univalue/tree/2015_11_unifuzz   (helpfully rebased on top of my UTF-8 branch)  ... secondly use this to build: https://gist.github.com/laanwj/68551528b7ae641ccaeb519566ca67c7
03:35 < wumpus> then you can use afl with the executable 'unifuzz'
03:38 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has quit [Read error: Connection reset by peer]
03:44 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has joined #bitcoin-core-dev
03:59 < phantomcircuit> wumpus, hmm so you have the fuzzing thing as a test binary
03:59 < phantomcircuit> i guess that makes more sense than adding a new directory
04:01 -!- afk11 [~afk11@unaffiliated/afk11] has quit [Ping timeout: 276 seconds]
04:02 -!- afk11 [~afk11@unaffiliated/afk11] has joined #bitcoin-core-dev
04:04 -!- Pasha [~C@unaffiliated/cory] has joined #bitcoin-core-dev
04:06 < wumpus> yes you need to recompile using the fuzzing gcc/g++ for instrumentation, and you need an executable that takes input on stdin and returns an exit status based on the input (or crashes, if it's found a bug)
04:06 < wumpus> also you need input samples that are ok and that fail, univalue has a few of those int the test directory
04:07 < wumpus> afl-fuzz generates further samples based on those
04:08 -!- Cory [~C@unaffiliated/cory] has quit [Ping timeout: 276 seconds]
04:08 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
04:08 -!- Alopex1 [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
04:11 -!- Pasha is now known as Cory
04:13 < phantomcircuit> wumpus, yeah i have a special vm where i have CC=afl-gcc and CXX=afl-g++ for the entire system
04:13 < phantomcircuit> so all libraries are instrumented
04:13 < phantomcircuit> (also i have some glibc debugging stuff enabled system wide)
04:13 < wumpus> that's not usually neede though
04:13 < phantomcircuit> wumpus, i know, it basically means im also fuzzing the library
04:14  * sipa likes seeing this discussion
04:14 -!- toker [5c05a05c@gateway/web/freenode/ip.92.5.160.92] has joined #bitcoin-core-dev
04:14 < wumpus> which is the same thing you do if you build univalue with the switches I gave. Sure, that won't fuzz libc and such, but for me at least that's out of scope.
04:15 < phantomcircuit> i like that it's fuzzing libc also, in case there's some weird interaction that is non-obvious
04:15 < phantomcircuit> i've not caught anything yet because of that of course
04:15 < wumpus> (and it may work the wrong way around, for example slow down runtime of functions you're not interested in in the first place)
04:19 < phantomcircuit> wumpus, oh it's definitely slower
04:19 < phantomcircuit> not generally much slower though unless the codes making heavy use of stuff which would otherwise be un-instrumented.... but that's exactly where im kind of interested in instrumenting it
04:19 < phantomcircuit> also i have cpu cycles to spare...
04:20 -!- cryptapus__ [~cyptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev
04:20 < phantomcircuit> oops it's 4:30am
04:20  * phantomcircuit sleeps
04:21 < wumpus> yes well happy fuzzing then
04:21 < wumpus> :)
04:22 -!- cryptapus__ is now known as cryptapus_
04:35 -!- KHCkjhv [~OUYOybgP@188.25.138.138] has quit [Ping timeout: 244 seconds]
04:38 -!- KHCkjhv [~OUYOybgP@188.25.22.57] has joined #bitcoin-core-dev
04:43 -!- KHCkjhv [~OUYOybgP@188.25.22.57] has quit [Quit: Leaving]
04:44 -!- KHCkjhv [~OUYOybgP@188.25.138.138] has joined #bitcoin-core-dev
04:47 -!- dermoth__ [~thomas@dsl-66-36-157-105.mtl.aei.ca] has joined #bitcoin-core-dev
04:49 < GitHub144> [bitcoin] sipa pushed 5 new commits to master: https://github.com/bitcoin/bitcoin/compare/04a29373571d...7daa3adb242d
04:49 < GitHub144> bitcoin/master e9fc71e Cory Fields: net: require lookup functions to specify all arguments...
04:49 < GitHub144> bitcoin/master a98cd1f Cory Fields: net: manually resolve dns seed sources...
04:49 < GitHub144> bitcoin/master 3675699 Cory Fields: net: resolve outside of storage structures...
04:49 < GitHub128> [bitcoin] sipa closed pull request #7868: net: Split DNS resolving functionality out of net structures (master...net-cleanup-resolve) https://github.com/bitcoin/bitcoin/pull/7868
04:52 -!- dermoth_ [~thomas@dial-216-221-42-131.mtl.aei.ca] has quit [Ping timeout: 276 seconds]
04:53 -!- KHCkjhv [~OUYOybgP@188.25.138.138] has quit [Ping timeout: 276 seconds]
04:57 < GitHub164> [bitcoin] sipa pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/7daa3adb242d...bafd075c5e6a
04:57 < GitHub164> bitcoin/master 220f950 Yuri Zhykin: Fix for incorrect locking in GetPubKey() (keystore.cpp)
04:57 < GitHub164> bitcoin/master bafd075 Pieter Wuille: Merge #7913: Fix for incorrect locking in GetPubKey() (keystore.cpp)...
04:57 < GitHub5> [bitcoin] sipa closed pull request #7913: Fix for incorrect locking in GetPubKey() (keystore.cpp) (master...getpubkey-locking-fix) https://github.com/bitcoin/bitcoin/pull/7913
04:57 -!- toker [5c05a05c@gateway/web/freenode/ip.92.5.160.92] has quit [Quit: Page closed]
05:11 -!- KHCkjhv [~OUYOybgP@188.25.22.57] has joined #bitcoin-core-dev
05:16 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
05:19 -!- gevs [~greg@unaffiliated/gevs] has quit [Remote host closed the connection]
05:20 -!- xiangfu [~xiangfu@60.10.71.37] has joined #bitcoin-core-dev
05:24 -!- gevs [~greg@ip-81-11-204-21.dsl.scarlet.be] has joined #bitcoin-core-dev
05:24 -!- gevs [~greg@ip-81-11-204-21.dsl.scarlet.be] has quit [Changing host]
05:24 -!- gevs [~greg@unaffiliated/gevs] has joined #bitcoin-core-dev
05:26 -!- MarcoFalke [8af6020a@gateway/web/cgi-irc/kiwiirc.com/ip.138.246.2.10] has joined #bitcoin-core-dev
05:26 -!- xiangfu [~xiangfu@60.10.71.37] has quit [Ping timeout: 246 seconds]
05:31 -!- xiangfu [~xiangfu@60.10.71.37] has joined #bitcoin-core-dev
05:41 -!- gevs [~greg@unaffiliated/gevs] has quit [Remote host closed the connection]
05:41 -!- gevs [~greg@unaffiliated/gevs] has joined #bitcoin-core-dev
05:50 -!- d_t [~textual@195.52.242.214] has joined #bitcoin-core-dev
05:55 < GitHub119> [bitcoin] laanwj pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/bafd075c5e6a...3689ac463439
05:55 < GitHub119> bitcoin/master 764d237 Jorge Timón: Globals: Explicitly pass const CChainParams& to UpdateTip()
05:55 < GitHub119> bitcoin/master d0a6353 face: Pass CChainParams to DisconnectTip()
05:55 < GitHub119> bitcoin/master 176869f face: Explicitly pass CChainParams to ConnectBlock
05:55 < GitHub1> [bitcoin] laanwj closed pull request #7916: Explicitly pass CChainParams& to DisconnectTip() (master...global-params-cleanup) https://github.com/bitcoin/bitcoin/pull/7916
06:07 < wumpus> MarcoFalke: I've just enabled commit access to bitcoin/bitcoin for you - to get you started, can you try to merge #7912 using the github-merge.py script? If you need any help setting it up let me know
06:09 < jonasschnelli> \o/
06:09 < MarcoFalke> whoohoo
06:10 < sipa> MarcoFalke: :)
06:10 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has joined #bitcoin-core-dev
06:10 < MarcoFalke> I should edit verify-commits first?
06:10 < jonasschnelli> Hmm... maybe you should add you key here first: https://github.com/bitcoin/bitcoin/blob/master/contrib/verify-commits/trusted-keys
06:11  * jonasschnelli can hear TheBlueMatt murmur in the background
06:11 < jonasschnelli> Otherwise verify-commits will fail.
06:12 < jonasschnelli> MarcoFalke: and make sure your sign the merge commits
06:13 < sipa> github-merge does that automatically
06:14 -!- xiangfu [~xiangfu@60.10.71.37] has quit [Quit: leaving]
06:17 -!- face [~face@mail.hmel.org] has quit [Remote host closed the connection]
06:18 < jonasschnelli> sipa: okay. But I guess at least you need to specify/gen a key if you haven't done that before. Not sure about MarcoFalke setup.
06:18 < sipa> right
06:18 < jonasschnelli> His last commits where not listed as "verified" by github: https://github.com/bitcoin/bitcoin/pull/7918/commits
06:18 < jonasschnelli> Could be a missing pubkey upload
06:19 < wumpus> yes, you need to add the key that you use to sign commits to the verify-commits script, good point
06:19 < sipa> ok, so MarcoFalke: can you 1) create a PR to add your key to trusted-keys 2) import your gpg key into github
06:19 < MarcoFalke> I am not signing "usual" commits
06:19 < wumpus> you don't need to
06:19 < MarcoFalke> gpg key is already in github
06:19 < MarcoFalke> only merge commits
06:19 < sipa> ah, i see
06:19 < wumpus> merge commits need to be signed, which is what the script does (as well as other things)
06:19 -!- face [~face@mail.hmel.org] has joined #bitcoin-core-dev
06:20 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has quit [Remote host closed the connection]
06:20 < MarcoFalke> Also cherry pick commits need to be signed but I am not doing backports anyway
06:20 < wumpus> right, as they are effectively merges
06:20 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has joined #bitcoin-core-dev
06:20 < sipa> are cherry-picked turned into merges?
06:21 < MarcoFalke> no, it is how verify-commit works
06:21 < sipa> verify-commits verifies all commits recursively along the leftmost child, i think
06:21 < sipa> whether they're merges or not
06:22 < MarcoFalke> I think it checks both right and left
06:22 < MarcoFalke> (for cherry-pick there is only left ofc)
06:23 < sipa> MarcoFalke: where are you based, btw?
06:23 < wumpus> the idea is that everything top-level has to be signed by a trusted key
06:23 < morcos>  sipa: whats the plan for handling rebases and addressing comments on 7910  (i was optimistically hoping for more of a code freeze while we review it)
06:23 < MarcoFalke> süddeutschland :)
06:24  * MarcoFalke wonders if sipa is fluent in swabian yet
06:24  * sipa is not
06:25 < sipa> morcos: i plan to add "fixup" commits to address the nits
06:25 < sipa> unless there is something significant
06:28 -!- zooko [~user@c-73-229-199-227.hsd1.co.comcast.net] has quit [Ping timeout: 268 seconds]
06:28 < MarcoFalke> Basically https://github.com/bitcoin/bitcoin/pull/7918 would conflict with segwit (on purpose) to get rid of the wildcard import and other cleanup. Should I submit this to the segwit branch instead?
06:28 < morcos> ok good and avoid rebasing for merge conflicts until the end i guess?
06:29 < sipa> MarcoFalke, morcos: your two above messages are a problem together :)
06:30 < sipa> MarcoFalke: it's probably better to do in the segwit branch (which would only modify its final commit)
06:31 -!- jtimon [~quassel@18.29.134.37.dynamic.jazztel.es] has quit [Ping timeout: 252 seconds]
06:32 < MarcoFalke> Ok, will add this to https://github.com/sipa/bitcoin/pull/79
06:32 < morcos> sipa: i perhaps started being a bit too thorough in my review (hence getting lost in the weeds of addrman) and i just got worried that its going to be hard to keep up if everythign is changing from underneath me.  but i'm glad to see a bunch of people seem to be reviewing right away, and fixup commits make a lot of sense to me.
06:33 < sipa> morcos: yeah, it would have been easier to ask for public review on the 0.12 version, i guess, but they have diverged already a bit
06:35 < GitHub84> [bitcoin] MarcoFalke opened pull request #7921: [contrib] verify-commits: Add MarcoFalke fingerprint (master...Mf1604-contribMFfingerp) https://github.com/bitcoin/bitcoin/pull/7921
06:38 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]
06:39 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-core-dev
06:41 -!- TomMc [~tom@unaffiliated/tommc] has joined #bitcoin-core-dev
06:43 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev
06:58 -!- shesek [~shesek@bzq-84-110-109-203.cablep.bezeqint.net] has quit [Ping timeout: 276 seconds]
07:01 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev
07:01 -!- fanquake [~Adium@unaffiliated/fanquake] has joined #bitcoin-core-dev
07:12 -!- fanquake [~Adium@unaffiliated/fanquake] has quit [Quit: Leaving.]
07:14 -!- muuqwaul [~denetrabu@2601:45:4002:d800:8dbb:a626:43ed:66ba] has joined #bitcoin-core-dev
07:15 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev
07:19 -!- earlest [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
07:21 -!- zooko [~user@50.243.136.91] has joined #bitcoin-core-dev
07:23 -!- muuqwaul [~denetrabu@2601:45:4002:d800:8dbb:a626:43ed:66ba] has quit [Ping timeout: 276 seconds]
07:25 -!- earlest [~denetrabu@96.93.57.150] has quit [Read error: Connection reset by peer]
07:33 -!- muuqwaul [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
07:33 -!- BashCo_ [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev
07:35 < GitHub77> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/3689ac463439...78d61aab233f
07:35 < GitHub77> bitcoin/master fa24329 MarcoFalke: [contrib] verify-commits: Add MarcoFalke fingerprint
07:35 < GitHub77> bitcoin/master 78d61aa Wladimir J. van der Laan: Merge #7921: [contrib] verify-commits: Add MarcoFalke fingerprint...
07:35 < GitHub188> [bitcoin] laanwj closed pull request #7921: [contrib] verify-commits: Add MarcoFalke fingerprint (master...Mf1604-contribMFfingerp) https://github.com/bitcoin/bitcoin/pull/7921
07:35 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 240 seconds]
07:50 -!- Thireus [~Thireus@vps-92.197.170.217.stwvps.net] has quit [Ping timeout: 268 seconds]
07:50 < Chris_Stewart_5> How is the sigop limit reached on this test case inside of script_invalid.json? 
07:51 < Chris_Stewart_5> ["",
07:51 < Chris_Stewart_5> "NOP NOP NOP NOP NOP NOP NOP NOP NOP NOP NOP NOP NOP 0 0 'a' 'b' 'c' 'd' 'e' 'f' 'g' 'h' 'i' 'j' 'k' 'l' 'm' 'n' 'o' 'p' 'q' 'r' 's' 't' 20 CHECKMULTISIG 0 0 'a' 'b' 'c' 'd' 'e' 'f' 'g' 'h' 'i' 'j' 'k' 'l' 'm' 'n' 'o' 'p' 'q' 'r' 's' 't' 20 CHECKMULTISIG 0 0 'a' 'b' 'c' 'd' 'e' 'f' 'g' 'h' 'i' 'j' 'k' 'l' 'm' 'n' 'o' 'p' 'q' 'r' 's' 't' 20 CHECKMULTISIG 0 0 'a' 'b' 'c' 'd' 'e' 'f' 'g' 'h' 'i' 'j'
07:51 < Chris_Stewart_5> 'k' 'l' 'm' 'n' 'o' 'p' 'q' 'r' 's' 't' 20 CHECKMULTISIG 0 0 'a' 'b' 'c' 'd' 'e' 'f' 'g' 'h' 'i' 'j' 'k' 'l' 'm' 'n' 'o' 'p' 'q' 'r' 's' 't' 20 CHECKMULTISIG 0 0 'a' 'b' 'c' 'd' 'e' 'f' 'g' 'h' 'i' 'j' 'k' 'l' 'm' 'n' 'o' 'p' 'q' 'r' 's' 't' 20 CHECKMULTISIG 0 0 'a' 'b' 'c' 'd' 'e' 'f' 'g' 'h' 'i' 'j' 'k' 'l' 'm' 'n' 'o' 'p' 'q' 'r' 's' 't' 20 CHECKMULTISIG 0 0 'a' 'b' 'c' 'd' 'e' 'f' 'g' 'h' 'i'
07:51 < Chris_Stewart_5> 'j' 'k' 'l' 'm' 'n' 'o' 'p' 'q' 'r' 's' 't' 20 CHECKMULTISIG 0 0 'a' 'b' 'c' 'd' 'e' 'f' 'g' 'h' 'i' 'j' 'k' 'l' 'm' 'n' 'o' 'p' 'q' 'r' 's' 't' 20 CHECKMULTISIG",
07:51 < Chris_Stewart_5> "P2SH,STRICTENC",
07:51 < Chris_Stewart_5> "Fails due to 201 sig op limit"]
07:51 < Chris_Stewart_5> There are (by my count) 9 OP_CHECKMULTISIG ops with 20 keys a piece 
07:51 < Chris_Stewart_5> which is 180 sigops
07:52 < Chris_Stewart_5> counting sigops by this function https://github.com/bitcoin/bitcoin/blob/master/src/script/script.cpp#L156-L178
07:56 -!- wasi [~wasi@pub082136076168.dh-hfc.datazug.ch] has joined #bitcoin-core-dev
07:57 -!- KHCkjhv [~OUYOybgP@188.25.22.57] has quit [Ping timeout: 246 seconds]
08:00 < sipa> Chris_Stewart_5: please don't paste quotes longer than 3-5 lines
08:04 < Chris_Stewart_5> Sorry, copy and pasted it from the file. 
08:05 -!- muuqwaul [~denetrabu@96.93.57.150] has quit [Ping timeout: 276 seconds]
08:05 < sipa> use a pastebin site, please
08:07 < Chris_Stewart_5> I'll make sure to do that in the future, here is the pastebin http://pastebin.com/vcEELjwF
08:09 -!- wasi [~wasi@pub082136076168.dh-hfc.datazug.ch] has quit [Quit: Leaving]
08:14 -!- gevs [~greg@unaffiliated/gevs] has quit [Ping timeout: 240 seconds]
08:18 -!- muuqwaul [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
08:21 -!- bsm1175321 [~mcelrath@38.121.165.30] has joined #bitcoin-core-dev
08:22 -!- bsm1175321 is now known as bsm117532
08:24 < GitHub39> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/78d61aab233f...59ad56851a34
08:24 < GitHub39> bitcoin/master 807fa47 Suhas Daftuar: Tests: Fix deserialization of reject messages...
08:24 < GitHub39> bitcoin/master 59ad568 MarcoFalke: Merge #7912: Tests: Fix deserialization of reject messages...
08:24 < GitHub137> [bitcoin] MarcoFalke closed pull request #7912: Tests: Fix deserialization of reject messages (master...fix-mininode-reject) https://github.com/bitcoin/bitcoin/pull/7912
08:27 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev
08:27 -!- gevs [~greg@ip-81-11-204-8.dsl.scarlet.be] has joined #bitcoin-core-dev
08:27 -!- gevs [~greg@ip-81-11-204-8.dsl.scarlet.be] has quit [Changing host]
08:27 -!- gevs [~greg@unaffiliated/gevs] has joined #bitcoin-core-dev
08:38 -!- Thireus [~Thireus@vps-92.197.170.217.stwvps.net] has joined #bitcoin-core-dev
08:39 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt]
08:43 < sipa> MarcoFalke: congrats :)
08:43 < btcdrak> first merge :)
08:48 < jl2012> Chris_Stewart_5: the comment is misleading
08:49 < jl2012> and I think it's actually a bug
08:49 < jl2012> https://github.com/bitcoin/bitcoin/blob/master/src/script/interpreter.cpp#L905
08:49 < jl2012> the 201 is the op code limit. Not sigop limit
08:50 < jl2012> and CHECKMULTISIG is counted as (number of keys +1) op codes
08:50 < jl2012> so 21*9 + 13 (NOP) = 202
08:52 -!- cryptocoder [~cryptocod@cpe-76-90-140-31.socal.res.rr.com] has quit [Quit: cryptocoder]
08:54  * MarcoFalke is waiting for per-repo   .js-merge-branch-action {display: none;}
08:58 < Chris_Stewart_5> jl2012: I understand how the comment can be misleading, but how is this a bug? Seems like just a typo in the comment?
08:59 < jl2012> CHECKMULTISIG is over counted
09:00 < Chris_Stewart_5> jl2012: is +1 for the null dummy?
09:01 -!- MarcoFalke [8af6020a@gateway/web/cgi-irc/kiwiirc.com/ip.138.246.2.10] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
09:01 < jl2012> data push should not be counted
09:01 < jl2012> and thanks for pointing out. I don't know this "hidden rule"
09:03 < Chris_Stewart_5> jl2012: Looks like you right, in sipa's pull request refactoring test cases he expects an OP_COUNT error https://github.com/sipa/bitcoin/blob/refactorscriptests_12/src/test/data/script_tests.json#L1097-L1101
09:04 -!- earlest [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
09:07 -!- muuqwaul [~denetrabu@96.93.57.150] has quit [Ping timeout: 250 seconds]
09:14 -!- d_t [~textual@195.52.242.214] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
09:20 -!- zooko [~user@50.243.136.91] has quit [Remote host closed the connection]
09:23 -!- zooko [~user@50.243.136.91] has joined #bitcoin-core-dev
09:34 -!- cryptocoder [~cryptocod@cpe-76-90-140-31.socal.res.rr.com] has joined #bitcoin-core-dev
09:37 -!- zooko [~user@50.243.136.91] has quit [Ping timeout: 268 seconds]
09:49 -!- jtimon [~quassel@18.29.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev
--- Log closed Thu Apr 21 10:03:35 2016
--- Log opened Thu Apr 21 10:11:24 2016
10:11 -!- kanzure [~kanzure@bryan.fairlystable.org] has joined #bitcoin-core-dev
10:11 -!- Irssi: #bitcoin-core-dev: Total of 144 nicks [0 ops, 0 halfops, 0 voices, 144 normal]
10:11 -!- kanzure_ [~kanzure@bryan.fairlystable.org] has joined #bitcoin-core-dev
10:11 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 275 seconds]
10:11 -!- kanzure_ [~kanzure@bryan.fairlystable.org] has quit [Client Quit]
10:16 -!- trippysa1mon [~trippy@cyberdynesys.org] has joined #bitcoin-core-dev
10:17 -!- Thireus1 [~Thireus@vps-92.197.170.217.stwvps.net] has joined #bitcoin-core-dev
10:18 -!- JackH_ [~Jack@79-73-185-113.dynamic.dsl.as9105.com] has joined #bitcoin-core-dev
10:18 -!- dermoth_ [~thomas@dsl-66-36-157-105.mtl.aei.ca] has joined #bitcoin-core-dev
10:19 -!- Netsplit *.net <-> *.split quits: adam3us, dermoth__, Thireus, JackH, pedrobranco, nanotube, trippysalmon
10:21 -!- Netsplit over, joins: adam3us
10:22 -!- Irssi: Join to #bitcoin-core-dev was synced in 736 secs
10:27 -!- nanotube [~nanotube@unaffiliated/nanotube] has joined #bitcoin-core-dev
10:27 -!- arowser_ [~quassel@106.120.101.38] has quit [Ping timeout: 244 seconds]
10:28 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev
10:33 < cfields> phantomcircuit: sorry i missed your ping yesterday. A fuzzer sounds like a great idea
10:33 < cfields> phantomcircuit: what's the problem you're having?
10:57 -!- bysherper [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
11:00 -!- earlest [~denetrabu@96.93.57.150] has quit [Ping timeout: 250 seconds]
11:01 < gmaxwell> jtimon: meeting in one hour.
11:03 < jtimon> is not now?
11:04 < gmaxwell> jtimon: no it's in one hour.
11:05 < gmaxwell> The time of the meeting is 1900 UTC.
11:05 < jtimon> yeah, sorry, thanks
11:07 < wumpus> lol, enter it into google schedule already
11:08 < wumpus> every week you're either a week early or late :)
11:08 < wumpus> hour*
11:08 -!- pedrobra_ [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Remote host closed the connection]
11:10 < jtimon> last week one hour later, this one hour early, next week...
11:14 -!- moli [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
11:16 -!- mrkent_ [~textual@unaffiliated/mrkent] has joined #bitcoin-core-dev
11:16 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 244 seconds]
11:24 -!- telelvis [5f5add97@gateway/web/freenode/ip.95.90.221.151] has joined #bitcoin-core-dev
11:38 < btcdrak> next week jtimon will perfect the quantum state of being both early and late for the meeting, but not on time.
11:40 < jtimon> no, next week I will be half an hour late, then half an hour early, then 15 min late...
11:41 -!- earlest [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
11:45 -!- muuqwaul [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
11:45 -!- bysherper [~denetrabu@96.93.57.150] has quit [Ping timeout: 276 seconds]
11:48 -!- earlest [~denetrabu@96.93.57.150] has quit [Ping timeout: 276 seconds]
11:52 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev
11:56 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit]
11:59 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has joined #bitcoin-core-dev
12:00 < wumpus> meeting time
12:00 < jonasschnelli> ding-dong
12:00 < wumpus> #startmeeting
12:00 < lightningbot> Meeting started Thu Apr 21 19:00:34 2016 UTC.  The chair is wumpus. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:00 < lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
12:01 < gmaxwell> jtimon: now.
12:01 < wumpus> topic ideas?
12:01 -!- Guyver2_ [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev
12:01 < kanzure> segwit review
12:02 < gmaxwell> cfields: morcos: sdaftuar: sipa: petertod1: jonasschnelli: MarcoFalke: phantomcircuit: BlueMatt_: 
12:02  * sipa not very present
12:02 < cfields> gmaxwell: here, thanks :)
12:02 < sdaftuar> here
12:02 < kanzure> there were some ideas submitted to split the segwit pull request for some not-quite-segwit but still good contributions into separate pull requests, i think it was phantomcircuit who said these things
12:02 < wumpus> only one action item from last week, move the 0.13 release schedule a month forward, that has been done
12:02 < sipa> kanzure: they already are
12:03 < sipa> kanzure: it's a single PR, enforcing service bits
12:03 < kanzure> alright
12:03 < wumpus> #topic segwit review
12:03 < gmaxwell> There has been a lot of input, which is good.
12:03 < morcos> i'm here temporarily
12:03 < cfields> sipa: i suppose you'd prefer to review and merge that first and rebase on top?
12:03 < sipa> my suggestion is to not rebase on master, and only add fixes as new commits
12:04 < kanzure> i have finished a read-through of the pull request although i might ask for assistance with someone to eliminate chunks of my notes (e.g. stuff it wouldn't be helpful for me to double check)...
12:04 < kanzure> (actually, i have read only the source code but not per commit, so commit ACKs will be incoming later)
12:04 < morcos> i think we should all make an effort to review as much segwit and do as little other merging as we can until we are ready to merge it.
12:05 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
12:05 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Ping timeout: 260 seconds]
12:05 -!- Guyver2_ is now known as Guyver2
12:06 < sdaftuar> +1
12:06 < sdaftuar> i think it'd be helpful to focus review effort now
12:06 < cfields> morcos: ok by me. I'd like to ask for an exception for the Travis migration stuff though, since I've got them actively engaged
12:06 < gmaxwell> That is going to create artifical merge pressure to avoid stalling everything else.
12:06 < cfields> (that shouldn't affect segwit at all)
12:06 < wumpus> I don't think we can stop the world until segwit gets in
12:06 < morcos> s/artificial//
12:06 < wumpus> there are *lots* of things going on right now
12:06 < wumpus> I do agree we should delay things that potentially conflict with segwit
12:07 < wumpus> to save sipa on rebasing work
12:07 < sdaftuar> save sipa and also help reviewers
12:07 < kanzure> pull request 7910 says "But a lot of testing (unit tests, rpc tests, p2p tests, and tests by external software projects) are being done already, so it is probably time to make it visible as a PR for general review."
12:07 < morcos> mostly i'm talking about order of operations here.  if there are people who aren't going to review segwit, sure, keep on doing what you're doing.  but whoever is going to review segwit.  why not do that first.
12:07 < kanzure> but perhaps a more elaborate test status update could be given by sipa either today or eventually?
12:07 < jtimon> I'm fine with delaying after segwit as well, at least for things that are clearly going to conflict
12:09 < morcos> if it was up to me, i would say we should stop the world until it gets in.  i'm of course aware that it is not up to me and can live with other approaches, but just trying to push us as much that direction as possible
12:09 < wumpus> also mind that lots of pulls are being submitted, multiple every day, there's only a few days that we really can hold up merging until the load becomes unbearable
12:10 < wumpus> what areas should we avoid changes to make it easier for segwit?
12:11 < kanzure> would we want to do backport implementation and testing and review before merging something like 7910?
12:11 < cfields> wumpus: there's also the option of a rebase exemption for segwit, allowing a traditional merge for the sake of not invalidating reviews
12:11 < wumpus> cfields: but that doesn't help the underlying issue, it just moves the work to the merge
12:11 < morcos> btw, to clarify my earlier comment, this isn't about getting segwit in as quickly as possible according to the calendar.  this is about being as efficient workers as possible.
12:12 < wumpus> morcos: an efficient project has multiple people working in parallel on multiple things
12:12 < wumpus> especially if these things are orthogonal, e.g. RPC or P2P work
12:12 < gmaxwell> I don't think right now we're at a point where if there was nothing in flight that we'd merge today. If we were, then I'd agree that we should stop the world.
12:13 < jtimon> maybe it make sense to merge and backport the first "preparations" section of the PR separately (that should be fast)?
12:13 < morcos> i guess maybe we're talking at cross purposes.  i just don't understand why people are working on other things instead of reviewing segwit so we are at a point where it can be merged
12:13 < kanzure> #action more code review of segwit
12:13 < morcos> it needs review, and its a priority for the project
12:13 < wumpus> cfields: and if you move the work to the merge then the review is pretty much invalidated too, because the code after the merge looks much different from taht before
12:13 < gmaxwell> I think there are probably a couple rebases worth of general hammering on segwit before we'd do that. There are also 'preparations' PRs that are seperate which can go in now. So perhaps those should also be a priority.
12:13 < sipa> wumpus: rebasing from 0.12 to master took me 2 hours or so; i think we shouldn't overeagerly rebase, but it's not impossible
12:14 < kanzure> that gives us only 360 rebases per month not counting sleep
12:14 -!- zooko [~user@96.90.163.54] has joined #bitcoin-core-dev
12:14 < jtimon> the sooner we merge these safe preparations, the sooner can stop worrying about other things conflicting with them
12:14 < cfields> wumpus: fair enough
12:15 < wumpus> so again:
12:15 < wumpus> changes to what areas should be avoided to make it easier for segwit?
12:15 < wumpus> what are the most annoying things to rebase sipa?
12:15 < wumpus> or at least, risky
12:15 < jtimon> I would assume consensus and relay policy refactors not directly contributing as preparations to segwit should wait
12:16 < wumpus> makes sense
12:16 -!- earlest [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
12:16 < gmaxwell> do we have coverage analysis for the current tests? relative to segwit? 
12:16 < jtimon> not sure about other areas
12:17 < wumpus> and yes if things can be merged already to pave the way for segwit, all the better
12:17 < jonasschnelli> gmaxwell: LCOV was included recently. I think there is a make target for the tests that produce coverage files
12:18 < cfields> gmaxwell: i can whip up a simple before/after. That's a good incentive to see if the dusty coverage stuff comes anywhere close to working.
12:18 < jtimon> I think that will also simplify review, by allowing one to make it in "phases"
12:18 < sipa> i'm not very worried about anything in-progres changes now
12:18 < gmaxwell> cfields: it might be useful in order to focus some attention on areas where people could contribute tests.
12:18 < wumpus> ok, in that case I'm not worried either, just trying to help
12:19 < cfields> yep, agreed. it'd be helpful to find what paths aren't covered for serialization too, since those changes are hard to review.
12:19 -!- muuqwaul [~denetrabu@96.93.57.150] has quit [Ping timeout: 250 seconds]
12:19 < cfields> (hard for me, anyway)
12:19 < kanzure> #action look at test coverage output
12:19 < morcos> sipa: so i'm not sure i understand.  are you only going to rebase rarely and announce in advance?  and how does one review the rebase other than trying to recreate it?
12:19 < gmaxwell> can we agree on a subset of the segwit commits as being most in need of review right now, to focus on those?
12:20 < gmaxwell> one thing we need to be warry of is loss of synchronization between 0.12 and 0.13, if the patches are not updated primarily by updating 0.12 and then carrying the updates in a rebase.
12:21 < jtimon> that's why I suggested merging and backporting the preparations first
12:21 < sipa> morcos: i'm not sure, i can not rebase at all
12:21 < sipa> gmaxwell: i think we'll end uo backporting the master patchset back to 0.12
12:22 < luke-jr> personally, I think it would be cleaner and perhaps easier to review a merge rather than a rebase. but I suspect others here disagree.
12:22 < jtimon> oh, #7910 needs rebase...
12:23 < sipa> luke-jr: you can always recreate the merge, and then diff against the result.of the rebase
12:23 < kanzure> er, i think that requires the original commits- which you might not have if you didn't fetch in time
12:23 < kanzure> *git fetch in time
12:24 < luke-jr> kanzure: if you didn't fetch, how did you review the older commits? ;)
12:24 < jtimon> well, mergers can test locally whether a given PR is going to create conflicts to segwit or leave the hypotethical rebase clean before merging (perhaphs that's too much work)
12:24 < kanzure> luke-jr: there's an answer but it's not a good answer
12:24 < kanzure> luke-jr: (for the record, i definitely fetched.)
12:24 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has quit [Quit: Leaving.]
12:25 < morcos> ok. well i have to run.  i hope i'm not being difficult, i just think sometimes we could work together a little better as a team if we're more willing to coordinate/cooperate.
12:25 < kanzure> also interested in determining which areas or which segwit commits are most needing of review
12:25 < morcos> in that vein if there is something else i could do to help, please let me know, in the meantime i'm going to keep going through segwit commits one by one
12:25 < jtimon> morcos: I don't think anybody disagreed on your point about review for segwit being a priority
12:26 < morcos> jtimon: i know, i'm just used to people telling other people what to do.  :)
12:27 < gmaxwell> I think I will make an effort to encourage people I see working on other things who haven't reviewed segwit to also review segwit.
12:27 < wumpus> at least I don't disagree, just that we can't force people to not work on other stuff, and that that wouldn't be constructive either (it'd just result in less work in other things instead of more work on segwit)
12:27 < kanzure> getblocktemplate changes probably need a few eyeballs to confirm things..
12:27 < luke-jr> yes, I need to update the GBT change PR
12:27 < CodeShark> sipa: I've mostly reviewed the older segwit branches - is there anything specific to look for or test in the rebase?
12:28 < luke-jr> #action (Luke) update GBT segwit stuff
12:28 < sipa> luke-jr: first figure out the bip9 related changes, i guess
12:28 < kanzure> luke-jr: should others wait on looking at getblocktemplate things there until you submit your update?
12:28 -!- airmac [~airmac@103-224-130-8.flip.co.nz] has joined #bitcoin-core-dev
12:28 -!- BlueMatt_ is now known as BlueMatt
12:28 -!- BlueMatt [~BlueMatt@mail.bluematt.me] has quit [Changing host]
12:28 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has joined #bitcoin-core-dev
12:28 < sipa> kanzure: it'll just add a few fields
12:28 < airmac> anyone intrested in trading bitgold for bitcoin we can use escrow if you like
12:28 < airmac> <airmac> you have to have a non us bitgold account to received bitgold
12:28 < airmac> <airmac> www.bitgold.com
12:28 < jtimon> I have still only reviewed a few commits, and they may have changed
12:29 -!- mode/#bitcoin-core-dev [+o sipa] by ChanServ
12:29 -!- mode/#bitcoin-core-dev [+b *!*airmac@*.flip.co.nz] by sipa
12:29 -!- airmac was kicked from #bitcoin-core-dev by sipa [airmac]
12:29 < kanzure> OK new fields sounds trivial-ish, so probably not a review blocker
12:29 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Remote host closed the connection]
12:30 < luke-jr> I don't know what the code state is for that, but the BIP PR needs updating at least
12:30 -!- JackH_ is now known as JackH
12:30 < luke-jr> sipa: any changes needed beyond our last conversation on that?
12:30 < gmaxwell> we probably need a deployment related affordance, where one can continue to mine without changes to GBT but not mine any new SW transactions; so that the recourse when there are downstream issues isn't back-out segwit.
12:31 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev
12:31 < jtimon> I think after the next rebase, we should be careful to merge anything that will require another non-trivial rebase
12:31 -!- zooko [~user@96.90.163.54] has quit [Ping timeout: 246 seconds]
12:31 < luke-jr> gmaxwell: before merging segwit, or as a follow-up PR?
12:32 < gmaxwell> doesn't have to be before.
12:34 < wumpus> ok, next topic? any proposals?
12:35 < cfields> topic proposal: travis switchover
12:35 < kanzure> if we could get an outline of which areas have been receiving lots of testing, which areas are under-tested, and which areas should be review critical and extra attention, then i think it will help smooth the review process
12:35 < wumpus> #topic travis switch to trusty
12:35 < wumpus> kanzure: agree that would be useful
12:35 < luke-jr> I dislike breaking external repos' ability to use Travis, but… we're already at that point, so meh
12:36 < cfields> I tried to summarize in #7920. Basically we need to hit a few buttons that may cause a few hours of instability. I don't think there's really much downside other than that, I just didn't want to pull the trigger without opening it for discussion
12:36 < cfields> luke-jr: this doesn't disable their ability
12:36 < wumpus> a few hours travis downtime is no problem
12:36 < cfields> luke-jr: they just won't get caching until the feature is generally available. They can ask for it as well.
12:36 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev
12:36 < wumpus> luke-jr: how would this change that?
12:36 < luke-jr> cfields: well, right now Travis is unwilling to enable it for other repos without a contractual agreement
12:36 < wumpus> we already have special support for caching
12:36 < jtimon> cfields: hours of isntability? meh, people can just change the commit id without changes and force push
12:36 < luke-jr> wumpus: it wouldn't, hence meh
12:37 < wumpus> right.
12:37 < cfields> luke-jr: eh? It's an email asking for a flag :)
12:37 < gmaxwell> luke-jr: right now we have some special settings that are us only. This moves us closer to a standard configuration.
12:37 < kanzure> is the concern that build caching is too much load on travis?
12:37 < jonasschnelli> cfields: Is there still no way to use the non-sudo travis way?
12:37 < kanzure> *their concern
12:37 < luke-jr> cfields: and gets denied unless you have an arrangement
12:37 < jonasschnelli> cfields: qt has been added to the "allowed packages"
12:37 < cfields> luke-jr: huh? This _removes_ our arrangement.
12:37 < luke-jr> gmaxwell: cfields: oh, I missed that detail
12:38 < gmaxwell> luke-jr: basically this gets rid of the old thing, in favor of a new feature which will be available to everyone.
12:38 < btcdrak> luke-jr: travis plan to roll it out for everyone.
12:38 < luke-jr> even better
12:38 < cfields> jonasschnelli: there are a few annoying things that won't every work without sudo, I'm afraid
12:38 < gmaxwell> it isn't _yet_ available to everyone, but the plan is that it will be, and it sounds like they would be much more willing to enable it for others.
12:39 < cfields> unless they can be encouraged to come up with some workarounds
12:39  * luke-jr looked at removing sudo use a while ago, and thought it just needed whitelisted pkgs
12:39 < cfields> right, we're beta testers. Pretty strenuous ones too :)
12:39 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit]
12:39 <@sipa> i would love to just enable travis on my own bitcoin fork repo
12:39 < kanzure> and travis changes are off-limits if they break lots of downstream forked projects?
12:39 -!- mode/#bitcoin-core-dev [-o sipa] by sipa
12:39 < kanzure> what level of commitment are we making there anyway..
12:39 < jonasschnelli> sipa: you can?!
12:39 < jtimon> sipa + 5
12:39 < jtimon> oh, really?
12:39 < cfields> sipa: you can already, it just takes ages
12:39 < jonasschnelli> unless you pay.
12:39 < sipa> cfields: it fails for me
12:40 < sdaftuar> takes ages?  i find that about half the time the jobs fail
12:40 < jtimon> #action tutorial to enable travis on your own repo
12:40 < sipa> jonasschnelli: no, it:s free
12:40 < jonasschnelli> sipa: you might need to push a recent master
12:40 < luke-jr> sdaftuar: recently?
12:40 < cfields> everyone can ask for the flag, we can nag them into pulling it out of beta :p
12:40 < sdaftuar> yeah, all the time
12:40 < jonasschnelli> sipa: its free but you get more cycles if you pay.
12:40 < sipa> of course
12:40 < sipa> bit until recently everything jist failed to build
12:40 < kanzure> sounds like the failure might be due to lack of flag enablement
12:40 < luke-jr> hrm, I fixed some Travis-outside-of-"bitcoin" issues earleir this year
12:41 < cfields> i'm working with them on a few other things (their-side) that should speed up builds as well
12:41  * gmaxwell looks over at the rack in his office with hundreds of processors that can't be used for this because we're depending on external infrastructure. 
12:41 < cfields> so likely in the near future it will be possible for everyone to have their own repos being built
12:41 < jonasschnelli> While where at travis: we could also think about adding another github compatible CI to speedup tests (share platforms over two CI systems)?
12:41 < wumpus> in any case very good to hear the trusty conversion is very close now, let's set things in motion
12:41 < kanzure> perhaps some companies would be willing to sponsor large piles of testing infrastructure :)
12:41 < wumpus> jonasschnelli: nah, maintaining one is enough work
12:41 < kanzure> lots of testing infrastructure would mean big development cycle speedups, less time waiting scratching heads
12:41 < cfields> wumpus: ok, can be done today
12:41 < wumpus> cfields: +1
12:42 < wumpus> cfields: let me know when I need to merge
12:42 < gmaxwell> cfields: in any case, push button; please
12:42 < cfields> wumpus: just need someone around to click the merge button on my PR after it goes live
12:42 < cfields> roger. Confirming now.
12:42  * jtimon remembers asking for a script to run everything travis runs in his own computer, is there such a thing?
12:42 < luke-jr> if there was a non-proprietary CI option, we could use gmaxwell's hundreds of processors, and also reproduce issues locally ;)
12:42 < cfields> jtimon: sure
12:43 < btcdrak> cfields: +1
12:43 < luke-jr> there is?
12:43 < cfields> luke-jr: travis is completely open, btw
12:43 < kanzure> #action (cfields) travis changes requiring some downtime
12:43 < wumpus> thanks kanzure
12:43 < jtimon> well, I could use a link to a tutorial or something, but I guess we can take that offline (ie after the meeting), thanks cfields
12:44 < wumpus> #action merge #7920 when cfields says so
12:44 < cfields> jtimon: sure
12:44 < jtimon> if I could queue builds that would be even more awesome
12:44 < wumpus> ok, any other topics to be discussed?
12:46 < wumpus> seems not :)
12:46 < btcdrak> the segwit afterparty!
12:46 < jtimon> https://i.ytimg.com/vi/_QR9QP0Rjsc/maxresdefault.jpg
12:47 < wumpus> #endmeeting
12:47 < lightningbot> Meeting ended Thu Apr 21 19:46:41 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
12:47 < lightningbot> Minutes:        http://www.erisian.com.au/meetbot/bitcoin-core-dev/2016/bitcoin-core-dev.2016-04-21-19.00.html
12:47 < lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/bitcoin-core-dev/2016/bitcoin-core-dev.2016-04-21-19.00.txt
12:47 < lightningbot> Log:            http://www.erisian.com.au/meetbot/bitcoin-core-dev/2016/bitcoin-core-dev.2016-04-21-19.00.log.html
12:47 < kanzure> i was told there would be a space boat party
12:47 < wumpus> haha that party gets grander every time
12:48 < jtimon> so, cfields, maybe a mail to the ml with a little introduction to "travis, you didn't know? you can do this at home!" and I can ask questions there (maybe more people are interested)
12:49 < kanzure> approximately how much time on average per travis build without caching?
12:49 < cfields> jtimon: sure. The foundation of moving to travis was to get everything in-tree so that anyone can run it. Travis just happens to be running it for us automatically
12:49 < gmaxwell> kanzure: by space boat party http://www.lorensworld.com/wp-content/uploads/2014/06/Outer-Space-themed-glowing-bath.jpg
12:50 < cfields> kanzure: now that we have docker availability, we can work on stashing depends as a separate step. I know you don't like 'docker build', but it'd be a stepping stone
12:50 < jtimon> I thought it was a private cloud service we were paying...
12:50 -!- bysherper [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
12:50 < kanzure> gmaxwell: the real party https://en.wikipedia.org/wiki/Hubble_Ultra-Deep_Field
12:50 -!- telelvis [5f5add97@gateway/web/freenode/ip.95.90.221.151] has quit [Quit: Page closed]
12:51 < kanzure> cfields: thanks for remembering that actually, world would be a much better place if we could all remember everyone else's dispreferences :)
12:51 < cfields> jtimon: travis just spawns VM instances and runs your build scripts. We could just as easily have someone else running it
12:51 < cfields> heh
12:51 < kanzure> cfields: yeah stashing would be helpful i'm sure. but i was asking for time averages because that number is helpful when asking companies for testing resources sponsorship.
12:52 < cfields> kanzure: it varies, but we push 50min for the worst case
12:52 < cfields> but again, that includes depends
12:52 < kanzure> or does travis throw as much computing as we request?
12:52 < cfields> kanzure: remember though, we dropped our own hosted bot because it required meddling with things under the hood. The nice thing about travis is that we give it a descriptive recipe, and we know what to expect.
12:53 < jtimon> cfields: I guess I should start here https://docs.travis-ci.com/user/getting-started/
12:53 < cfields> I'd be pretty adamant about making sure it continues to go that way
12:53 < wumpus> yes I prefer travis too to hosting something on our own
12:53 < wumpus> pulltester required so much babysitting
12:53 < kanzure> i know travis does freebies for open-source project but if we have 80 pull requests opened on the same day, do they go in parallel?
12:53 < cfields> jtimon: all you need to do is yank commands out of the .travis.yml and run them locally
12:53 -!- earlest [~denetrabu@96.93.57.150] has quit [Ping timeout: 276 seconds]
12:54 < wumpus> kanzure: no, they'll be queued
12:54 < jtimon> well, if it's free software there's no problem in it being hosted, we can host it ourselves later if needed
12:54 < cfields> kanzure: 4 concurrent builds, iirc
12:54 < kanzure> what is the queue width?
12:54 < kanzure> eww 4??
12:54 < wumpus> hosting it yourself would *also* cost money
12:54 < kanzure> yeah okay, so 50 minutes, 4 builds at most
12:54 < kanzure> yeah i know
12:54 < jtimon> cfields: oh, that easy? thank you, awesome!
12:54 < kanzure> anyway this is useful. i will repeat these numbers in public more frequently.
12:54 < cfields> kanzure: well on the good case, each build only takes about 5min
12:55 < cfields> kanzure: sec, i'll grab a random PR and check
12:55 < wumpus> as well as time spent working to administrate servers, which is far from free
12:55 < kanzure> yeah i understand. travis makes sense to me. i have no problems with travis at the moment.
12:55 < cfields> kanzure: https://travis-ci.org/bitcoin/bitcoin/builds/123870873
12:56 < kanzure> but.... if ecosystem companies want more development, paying for some more travis concurrency would go a long way.
12:56 < jtimon> so...hours of disruption, merging when #7920 when cfields says so...what is the blocker?
12:56 < cfields> kanzure: yes, that's very reasonable imo
12:56 < kanzure> "Total time 1 hr 2 min 4 sec" yeah this can easily clog 4 workers..
12:56 < kanzure> jtimon: he just wanted to inform us about it
12:56 < jtimon> the sooner we enjoy those hours of disruption, the better, no?
12:57 < kanzure> jtimon: since it would be kinda rude to flip the switch otherwise
12:57 < cfields> jtimon: I've already requested it, just waiting on a mail
12:57 < jtimon> kanzure: I see, that makes sense
12:58 < cfields> btw, there should be no actual disruption. In all likelihood we just get one slow build. I'm just adding in the human factor of "something always goes wrong".
12:59 -!- cryptapus_ [~cyptapus@unaffiliated/cryptapus] has quit [Ping timeout: 246 seconds]
12:59 < jtimon> the good old trick of lowering expectations as an insurance ;)
12:59 < cfields> heh
13:01 < cfields> sipa: would you prefer that I hold off on the c++11 PR until after segwit? I don't imagine it would interfere, but it could cause a little unforeseen distraction for builders trying to test if it causes any build issues
13:02 < sipa> cfields: nah, go ahead
13:02 < cfields> ok
13:03 < BlueMatt> ffs...totally just realized the meeting happened :'(
13:03 < BlueMatt> and I was here, just not reading :(
13:04 < gmaxwell> if only someone pinged you at the start.
13:05 < gmaxwell> Now we can theorize on the BlueMatt/jtimon exclusion principle.
13:06 < BlueMatt> i know, I know...I saw the ping and then went and did other things with a mental note to come back and see what it was
13:07 < gmaxwell> BlueMatt: well in any case, you didn't miss much. We assigned you to review all of segwit for us, and also to make sure blocks relay under it faster than they do today.  By next tuesday.
13:08 < BlueMatt> that seems....agressive...I'm travelling this weekend again
13:20 -!- shesek [~shesek@bzq-84-110-109-203.cablep.bezeqint.net] has joined #bitcoin-core-dev
13:21 -!- Cory [~C@unaffiliated/cory] has quit []
13:21 -!- jannes [~jannes@178.132.211.90] has quit [Quit: Leaving]
13:29 < sipa> BlueMatt: priorities...
13:31 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has joined #bitcoin-core-dev
13:31 < gmaxwell> BlueMatt: well okay, then you can have until thursday to get the improvements widely deployed.
13:31 < BlueMatt> heh
13:31 -!- earlest [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
13:33 -!- zooko [~user@2601:281:8000:8387:5522:b6ce:1c7a:811d] has joined #bitcoin-core-dev
13:35 -!- bysherper [~denetrabu@96.93.57.150] has quit [Ping timeout: 276 seconds]
13:36 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has quit [Ping timeout: 276 seconds]
13:43 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev
13:47 -!- Cory [~C@unaffiliated/cory] has joined #bitcoin-core-dev
13:51 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
13:53 -!- bysherper [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
13:56 -!- cryptapus is now known as cryptapus_afk
13:57 -!- earlest [~denetrabu@96.93.57.150] has quit [Ping timeout: 260 seconds]
13:58 -!- cryptapus_afk is now known as cryptapus
14:01 -!- murch [~murch@p4FDB77B2.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
14:28 -!- mrkent__ [~textual@unaffiliated/mrkent] has joined #bitcoin-core-dev
14:30 -!- mrkent_ [~textual@unaffiliated/mrkent] has quit [Ping timeout: 244 seconds]
14:49 -!- d_t [~textual@195.52.242.214] has joined #bitcoin-core-dev
14:50 -!- earlest [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
14:53 -!- bysherper [~denetrabu@96.93.57.150] has quit [Ping timeout: 276 seconds]
15:04 -!- arowser [~quassel@106.120.101.38] has quit [Quit: No Ping reply in 180 seconds.]
15:04 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev
15:05 -!- d_t [~textual@195.52.242.214] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:06 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)]
15:07 -!- murch [~murch@p4FDB77B2.dip0.t-ipconnect.de] has quit [Remote host closed the connection]
15:08 -!- face [~face@mail.hmel.org] has quit [Excess Flood]
15:08 -!- face [~face@mail.hmel.org] has joined #bitcoin-core-dev
15:25 -!- bysherper [~denetrabu@96.93.57.150] has joined #bitcoin-core-dev
15:29 -!- earlest [~denetrabu@96.93.57.150] has quit [Ping timeout: 276 seconds]
15:29 -!- cryptapus is now known as cryptapus_afk
15:38 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has joined #bitcoin-core-dev
15:44 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 250 seconds]
15:49 -!- TomMc [~tom@unaffiliated/tommc] has quit [Ping timeout: 276 seconds]
16:07 -!- kangx [2f2168ed@gateway/web/freenode/ip.47.33.104.237] has quit [Quit: Page closed]
16:18 -!- jtimon [~quassel@18.29.134.37.dynamic.jazztel.es] has quit [Ping timeout: 244 seconds]
16:20 -!- zooko [~user@2601:281:8000:8387:5522:b6ce:1c7a:811d] has quit [Ping timeout: 250 seconds]
16:41 -!- PRab_ [~chatzilla@c-68-34-102-231.hsd1.mi.comcast.net] has quit [Quit: ChatZilla 0.9.92 [Firefox 45.0.2/20160407164938]]
16:51 -!- Squidicuz [~squid@pool-173-48-102-116.bstnma.fios.verizon.net] has joined #bitcoin-core-dev
17:24 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has quit [Quit: Leaving.]
17:37 -!- grassass [grass@gateway/vpn/mullvad/x-lykmsyliiupfmzzx] has joined #bitcoin-core-dev
18:16 -!- belcher [~user@unaffiliated/belcher] has quit [Quit: Leaving]
18:23 -!- Alopex1 [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
18:24 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
18:26 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has joined #bitcoin-core-dev
18:29 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Read error: Connection reset by peer]
18:30 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
18:32 -!- nickler [~nickler@185.12.46.130] has quit [Ping timeout: 276 seconds]
18:34 < GitHub71> [bitcoin] kazcw opened pull request #7922: CBase58Data::SetString: cleanse the full vector (master...cleanse-fully) https://github.com/bitcoin/bitcoin/pull/7922
18:39 -!- nickler [~nickler@185.12.46.130] has joined #bitcoin-core-dev
19:00 < GitHub185> [bitcoin] kazcw opened pull request #7923: Enable leveldb obfuscation for new databases (master...obfuscate) https://github.com/bitcoin/bitcoin/pull/7923
19:00 -!- dermoth_ [~thomas@dsl-66-36-157-105.mtl.aei.ca] has quit [Read error: Connection reset by peer]
19:01 -!- dermoth_ [~thomas@dsl-66-36-157-105.mtl.aei.ca] has joined #bitcoin-core-dev
19:02 -!- nickler [~nickler@185.12.46.130] has quit [Ping timeout: 250 seconds]
19:03 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-fmcnxdxjhbxnevje] has quit [Quit: Connection closed for inactivity]
19:09 < GitHub172> [bitcoin] kazcw closed pull request #7923: Enable leveldb obfuscation for new databases (master...obfuscate) https://github.com/bitcoin/bitcoin/pull/7923
19:09 -!- nickler [~nickler@185.12.46.130] has joined #bitcoin-core-dev
19:10 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
19:13 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has quit [Read error: Connection reset by peer]
19:19 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has joined #bitcoin-core-dev
19:39 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 252 seconds]
19:43 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
19:46 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
19:47 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
20:02 -!- cryptapus_afk [~cryptapus@unaffiliated/cryptapus] has quit [Ping timeout: 244 seconds]
20:02 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev
20:02 -!- cryptapus is now known as cryptapus_afk
20:03 -!- lightningbot [supybot@2400:8900::f03c:91ff:fedf:3a06] has quit [Ping timeout: 268 seconds]
20:04 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 276 seconds]
20:05 -!- aj [aj@cerulean.erisian.com.au] has quit [Ping timeout: 260 seconds]
20:05 -!- wangchun [~wangchun@li414-193.members.linode.com] has quit [Ping timeout: 260 seconds]
20:12 -!- arowser_ [~quassel@106.120.101.38] has joined #bitcoin-core-dev
20:13 -!- arowser [~quassel@106.120.101.38] has quit [Ping timeout: 260 seconds]
20:33 -!- wangchun [~wangchun@li414-193.members.linode.com] has joined #bitcoin-core-dev
20:35 -!- aj [aj@cerulean.erisian.com.au] has joined #bitcoin-core-dev
20:37 -!- lightningbot [supybot@2400:8900::f03c:91ff:fedf:3a06] has joined #bitcoin-core-dev
20:48 -!- grassass [grass@gateway/vpn/mullvad/x-lykmsyliiupfmzzx] has quit [Ping timeout: 260 seconds]
20:50 -!- xiangfu [~xiangfu@111.198.29.53] has joined #bitcoin-core-dev
20:57 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev
21:01 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 260 seconds]
21:16 -!- PatBoy [xyz@192.99.249.215] has quit [Ping timeout: 260 seconds]
21:16 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
21:16 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
21:17 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
21:18 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
21:20 -!- mrkent__ [~textual@unaffiliated/mrkent] has quit []
21:20 -!- PatBoy [xyz@192.99.249.215] has joined #bitcoin-core-dev
21:23 -!- jl2012 [uid133844@gateway/web/irccloud.com/x-aizpfpsfgflfmrlm] has quit [Remote host closed the connection]
21:23 -!- jl2012 [uid133844@gateway/web/irccloud.com/x-gqtaxbutrudcrlhx] has joined #bitcoin-core-dev
21:33 -!- jl2012 [uid133844@gateway/web/irccloud.com/x-gqtaxbutrudcrlhx] has quit [Ping timeout: 260 seconds]
21:34 -!- jl2012 [uid133844@gateway/web/irccloud.com/x-qfxhkjgkktiqccgm] has joined #bitcoin-core-dev
21:44 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has quit [Remote host closed the connection]
21:45 -!- aquentson [~aquentson@unaffiliated/aquentson] has quit [Read error: Connection reset by peer]
21:46 -!- aquentson [~aquentson@unaffiliated/aquentson] has joined #bitcoin-core-dev
21:53 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
21:54 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
21:58 -!- jl2012 [uid133844@gateway/web/irccloud.com/x-qfxhkjgkktiqccgm] has quit [Ping timeout: 268 seconds]
22:00 -!- jl2012 [uid133844@gateway/web/irccloud.com/x-nexxmvrvvlvreece] has joined #bitcoin-core-dev
22:15 -!- Don_John [~Don@250-223-114-134.nat.resnet.nau.edu] has joined #bitcoin-core-dev
22:17 -!- xiangfu [~xiangfu@111.198.29.53] has quit [Ping timeout: 240 seconds]
22:18 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Ping timeout: 260 seconds]
22:19 -!- xiangfu [~xiangfu@111.198.29.53] has joined #bitcoin-core-dev
22:22 -!- arowser_ [~quassel@106.120.101.38] has quit [Quit: No Ping reply in 180 seconds.]
22:23 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev
22:29 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
22:30 -!- Don_John [~Don@250-223-114-134.nat.resnet.nau.edu] has quit [Quit: Later]
22:44 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
22:45 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
22:51 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has quit [Ping timeout: 260 seconds]
22:57 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has joined #bitcoin-core-dev
23:00 -!- lightningbot [supybot@2400:8900::f03c:91ff:fedf:3a06] has quit [Ping timeout: 250 seconds]
23:00 -!- dermoth_ [~thomas@dsl-66-36-157-105.mtl.aei.ca] has quit [Read error: Connection reset by peer]
23:01 -!- aj [aj@cerulean.erisian.com.au] has quit [Ping timeout: 246 seconds]
23:01 -!- dermoth_ [~thomas@dsl-66-36-157-105.mtl.aei.ca] has joined #bitcoin-core-dev
23:04 < phantomcircuit> sipa, gmaxwell anywhere in particular i should start poking around?
23:04 -!- wangchun [~wangchun@li414-193.members.linode.com] has quit [Ping timeout: 260 seconds]
23:04 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Ping timeout: 260 seconds]
23:06 < wumpus> well the most straightforward place to start is all kinds of parsing/deserialization functions, from json to base58 to consensus deserialization...
23:06 < wumpus> that's why I gave you the univalue example
23:07 -!- cryptocoder [~cryptocod@cpe-76-90-140-31.socal.res.rr.com] has quit [Read error: Connection reset by peer]
23:09 -!- aj [aj@cerulean.erisian.com.au] has joined #bitcoin-core-dev
23:09 -!- BashCo_ [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]
23:10 -!- wangchun [~wangchun@li414-193.members.linode.com] has joined #bitcoin-core-dev
23:11 -!- amiller [~socrates1@unaffiliated/socrates1024] has quit [Ping timeout: 244 seconds]
23:11 -!- lightningbot [supybot@2400:8900::f03c:91ff:fedf:3a06] has joined #bitcoin-core-dev
23:13 < wumpus> I submitted my first patch to gcc, wish me luck :< https://gcc.gnu.org/ml/gcc-patches/2016-04/msg01222.html
23:16 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
23:19 < paveljanik> :-)
23:20 -!- fkhan_ [weechat@gateway/vpn/mullvad/x-rntyoyhxdhucxyjl] has quit [Ping timeout: 276 seconds]
23:20 < paveljanik> seems like you like removing stuff ;-)
23:23 -!- Guest85934 [~socrates1@li175-104.members.linode.com] has joined #bitcoin-core-dev
23:24 < phantomcircuit> wumpus, yeah i fuzzed libconsensus before the launch of alpha
23:27 < wumpus> makes sense too, probably with disabled signature validation to give the fuzzer a chance?
23:28 -!- Guest85934 [~socrates1@li175-104.members.linode.com] has quit [Max SendQ exceeded]
23:28 < wumpus> paveljanik: I can't deny I do :)
23:32 < phantomcircuit> wumpus, nah i was looking for interesting results not valid results, so the harness returned 0 for valid and invalid scripts
23:33 -!- amiller_ [~socrates1@li175-104.members.linode.com] has joined #bitcoin-core-dev
23:33 < phantomcircuit> indeed i virtually always want the harness to return 0
23:34 < wumpus> ok, anyhow, go fuzz something already :)
23:37 < GitHub132> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/59ad56851a34...0c95ebce7e67
23:37 < GitHub132> bitcoin/master 9f7336b Jonas Schnelli: [Wallet] slightly refactor GetOldestKeyPoolTime()
23:37 < GitHub132> bitcoin/master 0c95ebc Wladimir J. van der Laan: Merge #7816: [Wallet] slighly refactor GetOldestKeyPoolTime()...
23:37 < GitHub90> [bitcoin] laanwj closed pull request #7816: [Wallet] slighly refactor GetOldestKeyPoolTime() (master...2016/04/wallet_oldest_key) https://github.com/bitcoin/bitcoin/pull/7816
23:38 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev
23:41 < GitHub59> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/0c95ebce7e67...76176823ba6a
23:41 < GitHub59> bitcoin/master 3a99fb2 Suhas Daftuar: Fix headers announcements edge case...
23:41 < GitHub59> bitcoin/master 7617682 Wladimir J. van der Laan: Merge #7919: Fix headers announcements edge case...
23:41 < GitHub157> [bitcoin] laanwj closed pull request #7919: Fix headers announcements edge case (master...fix-sendheaders-edge-case) https://github.com/bitcoin/bitcoin/pull/7919
23:43 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-qcbtnaytdcienvce] has joined #bitcoin-core-dev
23:45 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has joined #bitcoin-core-dev
23:45 < wumpus> cfields: ccache eats gcc's warning/error coloring!
23:47 < gmaxwell> I think gcc probably doesn't emit it unless it's writing to a terminal.
23:47 < wumpus> ah right, ccache probably pipes the output
23:47 < gmaxwell> try -fdiagnostics-color=always
23:48 -!- amiller_ [~socrates1@li175-104.members.linode.com] has quit [Ping timeout: 250 seconds]
23:49 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has quit [Ping timeout: 240 seconds]
23:53 -!- amiller_ [~socrates1@li175-104.members.linode.com] has joined #bitcoin-core-dev