--- Day changed Mon Nov 09 2015
00:14 -!- guest234234 [~guest2342@171.5.144.133] has joined #bitcoin-core-dev
00:15 -!- guest234234 [~guest2342@171.5.144.133] has quit [Max SendQ exceeded]
00:16 -!- guest234234 [~guest2342@171.5.144.133] has joined #bitcoin-core-dev
00:16 -!- guest234234 [~guest2342@171.5.144.133] has quit [Max SendQ exceeded]
00:23 < Luke-Jr> FWIW, a KDE developer in #qt told me if it needs to be accessed from other software, don't use QSettings and write our own :/
00:23 < Luke-Jr> (I asked a while ago when it was ongoing discussion)
00:28 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev
00:34 -!- JackH [~Jack@host-80-43-141-3.as13285.net] has joined #bitcoin-core-dev
00:34 < wumpus> won't 'write your own' effectively end up reimplementing qsettings? you need to do something for every OS
00:37 < wumpus> not saying that is not the way forward to 'find' the same datadir in bitcoin-cli and bitcoind, as well as other software, but it doesn't quite make it easier
00:38 < wumpus> oops accidentally had 'debian desktop environment' on while installing a VM, was wondering why it was pulling 2300+ packages in debian 8 :-)
00:44 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.]
00:57 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]
01:15 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev
01:17 -!- NLNico [~NLNico@unaffiliated/nlnico] has quit [Quit: Leaving]
01:29 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev
02:13 -!- rubensayshi [~ruben@91.206.81.13] has joined #bitcoin-core-dev
02:22 < wumpus> executables for 0.11.2rc1 are live: https://bitcoin.org/bin/bitcoin-core-0.11.2/test/   sorry for the delay
02:25 -!- jtimon [~quassel@74.29.134.37.dynamic.jazztel.es] has quit [Read error: Connection reset by peer]
02:27 < GitHub133> [bitcoin] laanwj closed pull request #6968: [Docs] First-draft release notes for 0.11.2RC1 (0.11...release-notes-0.11.2) https://github.com/bitcoin/bitcoin/pull/6968
02:27 < GitHub138> [bitcoin] laanwj pushed 4 new commits to 0.11: https://github.com/bitcoin/bitcoin/compare/984587ac5d3e...3dcb390fe9e2
02:27 < GitHub138> bitcoin/0.11 40941d9 David A. Harding: [Docs] First-draft release notes for 0.11.2RC1
02:27 < GitHub138> bitcoin/0.11 929b2c7 David A. Harding: [docs] Minor revisions to 0.11.2RC1 release notes...
02:27 < GitHub138> bitcoin/0.11 9149589 David A. Harding: [docs] 0.11.2 release notes: add sipa graphs & leveldb note...
--- Log closed Mon Nov 09 02:34:01 2015
--- Log opened Mon Nov 09 03:41:35 2015
03:41 -!- kanzure [~kanzure@unaffiliated/kanzure] has joined #bitcoin-core-dev
03:41 -!- Irssi: #bitcoin-core-dev: Total of 78 nicks [0 ops, 0 halfops, 0 voices, 78 normal]
03:41 < wumpus> it should be forbidden to use C and its cursed offspring for anything such as string processing
03:41 < gmaxwell> wumpus: yea, there are a bunch of multimedia file formats where there are subtle incompatiblities in every implementation because of number in "ascii" headers.
03:41 < gmaxwell> You can change your locale in the program, but doing so will change it in other threads.. not exactly nice to do in libraries.
03:42 < wumpus> yes that solves one problem but causes many others. We tried forcing the locale to C in bitcoin for a while but this messed with file name encodings on windows.
03:43 < wumpus> solve one subtle problem, create another
03:44 < phantomcircuit> just pause world, change locale to c, call strtol, change back to whatever, and unpause world
03:44 < phantomcircuit> no problem
03:44  * phantomcircuit runs
03:45 < gmaxwell> Well for example, you could change it just around the single point(s) you need C locale-- at least for the specific problem of file format compatiblity; but ... threads break that. so to fix this elsewhere I've had to just rewrite those C parser functions.
03:45 < wumpus> phantomcircuit: travel back in time and ... try to convince Dennis Ritchie to not make this awful mistake
03:45 < gmaxwell> wumpus: thats really a subcase of my maxium about strings being doom. :)  Other languages have their own string awfulness. :(
03:46 < wumpus> yes, typical C, inthe end you have to roll everything yourself, because the library support sucks
03:46 < gmaxwell> (often around unicode)
03:46 < wumpus> and if it happens to not suck on your platform, be prepared to do that when making your application portable
03:47 < wumpus> well other languages also have issues, but usually not as dangerous
03:47 < gmaxwell> yea, then you end up somewhere where someone thought 'UCS-2' was a good idea... and then you want to carry some chinese characters that aren't part of the BMP. :)
03:48 < gmaxwell> and fun like: https://en.wikipedia.org/wiki/Bush_hid_the_facts
03:48 < wumpus> yes, typical C, inthe end you have to roll everything yourself, because the library support sucks <- and of course while doing that you write it half assed, so it walks out of a buffer somewhere... happiness, more fun
03:48  * midnightmagic likes C
03:48 < wumpus> gmaxwell: LOl yeah
03:49 < wumpus> I like C to, but not for anything involving string processing or dynamic structures
03:49 < gmaxwell> I am pretty sure that every cases where I've used a string where something else would have been a reasonable choice, I regretted the string. :)
03:50 < gmaxwell> But this may reflect too much time spent in C. OTOH, I think in terms of sheer hours lost, I've lost more to string hell in python. (probably because I avoid strings like the plague in C).
03:50 < wumpus> or anything that can result in buffers that overflow, for that matter
03:50 -!- Irssi: Join to #bitcoin-core-dev was synced in 558 secs
03:50 < midnightmagic> +1 python string hell, plus incompatibility with unicode handling across versions
03:51 < wumpus> almost the entire infosec industry can thank C for their jobs
03:51 < wumpus> I've never had any problems with strings in python
03:52 < gmaxwell> wumpus: python string hell mostly needs the help of unicode. 
03:52 < wumpus> what's so bad about unicode? just use UTF-8 everywhere
03:52 < gmaxwell> esp less common unicode. Like chinese.
03:52 < midnightmagic> former employer wrote unicode handling in python 2.x, and as a result, had a *dual* python installation requirement for about a year for a flagship product while transitioning to python 3
03:52  * midnightmagic claws own eyes out
03:52 < gmaxwell> wumpus: because random python library code catches fire inconsistently with invalid, or worse --valid but unusual-- unicode. 
03:53 < gmaxwell> I believe its improved a lot in the last couple years at least.
03:55 < wumpus> anyhow, I don't have any reason to defend python. I just think C for anything involving strings should die. And this reflects spending too much time in C (and related languages) solving stupid string handling, truncation, buffer overflow issues and crashes and security holes
03:56 < gmaxwell> wumpus: not just C's fault, we can also blame microarchitecutrs for not making tagged/bounds checked pointers cheap in hardware. (Intel tried once but their product was premature and a commercial failure...)
03:57 < wumpus> gmaxwell: well, sure, that would be perfect. But I think C could have been less devious and not suffer anything in performance.
03:59 < wumpus> sometimes it seems to have been designed to make software as insecure and buggy as possible
03:59 < wumpus> (and mind you,that's mostly the library, not the langauge at fault!)
04:00 < gmaxwell> I think part of the problem is also that "parsing" code ends up having much higher branch-complexity than almost any other code, so it is very hard to test completely... so thats where the bugs endup being, and often its strings being parsed. In libsecp256k1 the der parsers are ~25% of the conditional statements, but only about 9% of the lines of code... and they required very clever tests to ev
04:00 < gmaxwell> en execute all their branches. 
04:02 < wumpus> sure, but if straightforward functions like strtol, which they teach new people to use, simply did parse according to a clear specification instead of 'leave it to the locale', that doesn't make parsing code any easier to write
04:02 < wumpus> s/doesn't/would/
04:02 < gmaxwell> things like strtol did originally not to locale stuff... that was a later enhancement that fit poorly with the architecutre of the functions.
04:02 < wumpus> bleh sometimes I think programming is no longer for me
04:03 < wumpus> get too angered about stuff lately
04:04 < gmaxwell> One must come to terms with everything being broken as the natural state of the world.  On the plus side, you will never run out of things to fix. :)
04:04 < dcousens> gmaxwell: I have a weekly break-down about that on Fridays
04:04 < wumpus> ah yes 'enhancement' :-) just like there was strcpy, which was plain stupid, then they tried to fix it using strncpy, which had other warts, and then there came platform-specific ones like strlcpy ...
04:05 < gmaxwell> in software we makes things 10,000x (or more) more complex than other more mature domains of engineering would even dare; and with much smaller budgets and compressed timelines.
04:06 < wumpus> which of course are still not supported on all platforms, so even if there is a better function you still end up implementing it yourself, or wrapping something, of course introducing more bugs
04:07  * midnightmagic is not surprised at all that deRaadt seems deflated and fatalistic these days
04:07 < wumpus> well given how much time we spend working around warts in our tools that's amazing
04:07 < dcousens> wumpus: interestingly, in 6 years of doing C++
04:07 < dcousens> I think I can count strcpy uses on my hand
04:08 < wumpus> dcousens: oh yes, but you'll encounter it in other people's code that you are using / relying on! that's half the fun
04:08 < gmaxwell> C++ allows you to swap out your choice of the warts in C with different and more exciting warts. :)
04:08 < wumpus> midnightmagic: it's hard to not be fatalistic about these things, this is quite a hole we've digged ourself in
04:08 < dcousens> wumpus: simple, don't just don't rely on other peoples code
04:08 < dcousens> (/s)
04:09 < wumpus> dcousens: hehe
04:11 < gmaxwell> The space shuttle had about 2 million moving parts. Firefox has something like 10 million 'moving parts'. If the space shuttle has a problem a half dozen people have a very bad day, if firefox has an issue a few hundred million people may have a (less, I hope) bad day.
04:11 < wumpus> dcousens: that's surprisingly hard, even if you'd write your own OS and compiler, there is a whole castle of shit (depending on the platform, bootrom, UEFI, ACPI, etc) that runs before you can and can subtly mess things up! 
04:12 < wumpus> no surprise we're not going to the moon anymore :-)
04:12 < midnightmagic> wumpus: people yelling at you all the time probably doesn't help much. I dunno how deRaadt's made it this far without melting down and just disappearing off into the bush with a crossbow..
04:12 < gmaxwell> In any case, there is something worse than (all) things being broken. And thats being stuck working on software where things are broken and _no one cares_. Here we do really care, even if we're sometimes helpless because there is so much debt and the problems are so hard.
04:12 < midnightmagic> (I mention deRaadt only because you said something about strlcpy)
04:13 < dcousens> haha, gmaxwell here here
04:13 < dcousens> wumpus: I know, you can only chase the rabbit whole so far until you realise hardware is completely retarded as well
04:13 < midnightmagic> gmaxwell: Or, worse than no-one caring, but everyone getting *angry* at you for pointing out all these problems that indicate the software will fail in production!
04:14 < gmaxwell> but yea, the specifics around C/posix where common mistakes reliably result in exploitable vulnerabilities is why @blockstream we're trying rust for some things.
04:14 < wumpus> gmaxwell: very true
04:14 < wumpus> gmaxwell: yes, I've also started using rust for some private tools, can say it's pretty nice
04:14 < gmaxwell> midnightmagic: yea no kidding. It's really bad in much of the software writing world. You're the bad guy for pointing out things are dangerously broken.
04:14 < midnightmagic> As in..  they *want* to not care about broken things, but by pointing broken things out to them, they are forced to care, and then they get angry at you and make you present at conferences things that kill you a little inside.
04:15 < dcousens> midnightmagic: haha
04:15 < gmaxwell> wumpus: I heard from andytoshi that you've been keeping him honest on rust-bitcoin. :)
04:15 < wumpus> midnightmagic: well the messenger of bad news and al
04:16 < wumpus> midnightmagic: or rather, people *know* how broken things are, but feel helpless, and get homicidal when they are reminded :)
04:17 < wumpus> like we're all on the same boat, and it's sinking, but there's no use in telling people that because they already know, but there's no way to stop it
04:18  * midnightmagic mutters about Mongol messengers getting a bit more respect after the first few times they were decapitated..
04:18 < gmaxwell> some of this is about variance, the tools we have for software are so amazingly powerful-- but they mostly reduce the average case complexity of software engineering.  The worst case complexity of software engineering is still little better than if were wirewraping out programs, except in wirewrap form they would be the size of the planet.
04:18 < midnightmagic> loll
04:19 < gmaxwell> s/out programs/our programs/
04:22 < dcousens> wumpus: its like the boat is perpetually sinking though
04:22 < dcousens> but you keep inflating life boats to hold up the hull
04:22 < gmaxwell> (I really didn't appriciate how awesome the tools we have for software were, until I had a dream once that I was working on a car, and had GDB like tools. "set a watch on that air molecule and single step; ah it escapes the intake at the throttle body, but only under boost" :)  Slim consolation, we use these tools to make software much more complex than we'd dare attempt otherwise.
04:22 < gmaxwell> )
04:23 < dcousens> haha
04:23 < wumpus> gmaxwell: one problem is that it's become so easy to make something that *seems* to do what you want :)
04:25 < gmaxwell> In 15 seconds you can write a program with 20 moving parts (e.g. branches or what not); if you built a simple machine with that complexity you'd probably expect to spend days twiddling with it to get it working right.
04:25 < dcousens> gmaxwell: thats why I try to just avoid moving parts as much as possible :P
04:26 < dcousens> functionality purity is great
04:26 < dcousens> (a different problem, but, similar prospect)
04:26 < wumpus> gmaxwell: hehe, yes, some of the tools are pretty awesome. When they work.
04:27 < gmaxwell> Still, even the most pure functional code has its own 'moving part complexity' (even though avoiding mutable state really does simplify analysis of many kinds)
04:27 < wumpus> (and once you've learned how to use them, which, by the time you fully grasp them, they're deprecated and you need to learn something new :p)
04:27 < jonasschnelli> hah
04:28 < gmaxwell> gdb is still gdb. :) Part of why I'm so happy that RR works with GDB so well now.
04:31 < wumpus> and gdb, while great with C, works so bad with C++ :-( the many times I've seen (optimized out) just for the variable I was trying to inspect... even when compiling without optimizations. Or inspecting e.g. stl containers, which have a maze of templated objects inside...
04:31 < wumpus> anyhow, enough ranting for today, sorry
04:32 < gmaxwell> A rant here or there is good for everyone.
04:32 < gmaxwell> :) Always good to confirm that you're not alone.
04:33 < wumpus> yes, thanks :)
04:38  * jonasschnelli likes lldb
04:51 < wumpus> haven't tried lldb yet
05:17 -!- ParadoxSpiral [~ParadoxSp@p508B8F19.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
05:19 < GitHub67> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/6176e9bf3d55...f24880b13213
05:19 < GitHub67> bitcoin/master c53d48a Jorge Timón: BIP70: Chainparams: DRY: Make qt/guiutil.cpp fit BIP70 chain name strings...
05:19 < GitHub67> bitcoin/master f24880b Wladimir J. van der Laan: Merge pull request #6908...
05:19 < GitHub130> [bitcoin] laanwj closed pull request #6908: Chainparams: DRY: Make qt/guiutil.cpp fit BIP70 chain name strings (master...chainparams-bip70-0.12.99) https://github.com/bitcoin/bitcoin/pull/6908
05:19 < GitHub173> [bitcoin] laanwj closed pull request #6953: Backport bugfixes to 0.10 (2015-10-22 / f2c869a) (0.10...backport-bugfixes-to-0.10-20151014) https://github.com/bitcoin/bitcoin/pull/6953
05:19 < GitHub98> [bitcoin] laanwj pushed 15 new commits to 0.10: https://github.com/bitcoin/bitcoin/compare/cbc4e3bd37da...3b89bf643896
05:19 < GitHub98> bitcoin/0.10 9c81005 Diego Viola: Fix spelling of Qt
05:19 < GitHub98> bitcoin/0.10 3ad96bd Alex Morcos: Fix locking in GetTransaction....
05:19 < GitHub98> bitcoin/0.10 612efe8 MarcoFalke: [Qt] Raise debug window when requested...
05:33 < GitHub120> [bitcoin] ptschip opened pull request #6973: Zlib Block Compression for block relay (master...compress) https://github.com/bitcoin/bitcoin/pull/6973
05:33 < GitHub72> [bitcoin] laanwj opened pull request #6974: Always allow getheaders from whitelisted peers (master...2015_11_whitelisted_allow_headers) https://github.com/bitcoin/bitcoin/pull/6974
05:44 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has quit [Ping timeout: 240 seconds]
06:07 -!- Guest91590 [~pigeons@94.242.209.214] has quit [Ping timeout: 255 seconds]
06:09 < GitHub127> [bitcoin] laanwj pushed 1 new commit to 0.10: https://github.com/bitcoin/bitcoin/commit/c2e7baf2bdb2e2c163bcadaebe68ee00c9a27e7c
06:09 < GitHub127> bitcoin/0.10 c2e7baf Wladimir J. van der Laan: Bump version to 0.10.4, add release notes
06:12 < wumpus>  * [new tag]         v0.10.4rc1 -> v0.10.4rc1
06:13 -!- pigeons [~pigeons@94.242.209.214] has joined #bitcoin-core-dev
06:13 -!- pigeons is now known as Guest51134
06:20 < helo> another couple days, another abort on assert(onlyMaybeDeadlock)... am i the only one seeing these?
06:29 < wumpus> haven't seen it yet
06:35 -!- ParadoxSpiral_ [~ParadoxSp@p508B9112.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
06:38 -!- ParadoxSpiral [~ParadoxSp@p508B8F19.dip0.t-ipconnect.de] has quit [Ping timeout: 272 seconds]
06:39 < helo> i think it's only started since i upgraded to ubuntu 15.10
06:40 < wumpus> so you're building with -DDEBUG_LOCKORDER?
06:41 < wumpus> that became the default for --enable-debug some time ago, that's probably when it started
06:42 < helo> i've been using --enable-debug for quite a while now
06:43 < helo> i've seen plenty of the potential deadlock warnings, but never aborting until recently
06:43 < wumpus> the commit that enables it is Mon Jul 13 14:28:03 2015
06:45 -!- lclc [~lclc@unaffiliated/lclc] has quit [Ping timeout: 272 seconds]
06:48 < GitHub135> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/f24880b13213...503ff6e1ae69
06:48 < GitHub135> bitcoin/master 9ea7762 Matt Corallo: Use Pieter's signing subkey instead of his primary key...
06:48 < GitHub135> bitcoin/master 503ff6e Wladimir J. van der Laan: Merge pull request #6967...
06:48 < GitHub148> [bitcoin] laanwj closed pull request #6967: Use Pieter's signing subkey instead of his primary key (master...verify-commits-fixes) https://github.com/bitcoin/bitcoin/pull/6967
06:53 -!- lclc [~lclc@unaffiliated/lclc] has joined #bitcoin-core-dev
06:56 < jonasschnelli> on my libsecp256k verification node, my active tip is at 382748 (~-10 blocks), headers are up to 382758... 
06:56 < GitHub75> [bitcoin] harding opened pull request #6975: [doc] 0.11.2 release notes: use original pull numbers (0.11...note-0.11.2-orig-prs) https://github.com/bitcoin/bitcoin/pull/6975
06:56 < jonasschnelli> 20049 transaction stuck in the mempool
06:56 < jonasschnelli> 286MB dynamic usage
06:59 < jonasschnelli> On of my local nodes (non libsecp256k1 verification) tells me i'm on 382758 with ~5000tx in mempool. 
07:14 -!- lclc [~lclc@unaffiliated/lclc] has quit [Ping timeout: 240 seconds]
07:14 -!- bsm1175321 [~mcelrath@38.121.165.30] has quit [Ping timeout: 240 seconds]
07:19 -!- bsm1175321 [~mcelrath@38.121.165.30] has joined #bitcoin-core-dev
07:21 -!- lclc [~lclc@unaffiliated/lclc] has joined #bitcoin-core-dev
07:21 -!- GAit [~GAit@2-228-102-98.ip191.fastwebnet.it] has joined #bitcoin-core-dev
07:22 < wumpus> jonasschnelli: why is the node stuck? did it reject a block?
07:23 < jonasschnelli> wumpus: can't see anything in the debug.log (have no -debug flag activated)
07:23 < wumpus> you don't need a debug flag to log block rejection, just for tx rejection
07:23 < jonasschnelli> let me check again...
07:25 < jonasschnelli> i can see the update tip to: 382748
07:25 < jonasschnelli> after that, only "boring" stuff like "receive version message:"
07:25 < jonasschnelli> no reject
07:26 < jonasschnelli> last 1000 lines of my debug log: https://bitcoin.jonasschnelli.ch/secp/stuck_debug.log
07:28 -!- lclc [~lclc@unaffiliated/lclc] has quit [Ping timeout: 260 seconds]
07:29 -!- lclc [~lclc@unaffiliated/lclc] has joined #bitcoin-core-dev
07:29 < bsm1175321> jonasschnelli: that seems like an awful lot of version messages to me.  Why so many disconnects/reconnects?
07:30 < bsm1175321> My node has been running since ~Thursday and is on peer=14, yours is at peer=2715.
07:30 < helo> i get insane disconnects/reconnects from bitnodes
07:31 < bsm1175321> Mine is firewalled though, no incoming connections.
07:31 < jonasschnelli> hmm... no idea. getpeerinfo reports a huge list.
07:31 < jonasschnelli> node is up since: 2015-11-08 19:17:23 
07:31 < bsm1175321> Maybe your node has fallen behind and is getting banned?
07:32 < bsm1175321> jonasschnelli: my node is up since 2015-11-05.
07:33 < jonasschnelli> bsm1175321: hmm.. don't think so.. getpeerinfo reports many peers with reasonable connect time
07:33  * jonasschnelli needs to attach the debugger for more info...
07:34 < jonasschnelli> i assume -dbcache=6000 should not be related to this issue?
07:35 < bsm1175321> jonasschnelli: In between blocks 382748 and a peer notifying blocks=382749 is: 2015-11-09 13:39:07 socket recv error Connection reset by peer (104)
07:35 < bsm1175321> Could that have been the 382749 block download?  
07:35 < jonasschnelli> theres a second headers-only chain which i accidentally cut of in the comment: now re-added: https://github.com/bitcoin/bitcoin/pull/6954#issuecomment-155093019
07:36 < wumpus> ouch, I shut down a VM where a bitcoind w/ -dbcache=8000 was running, without waiting for bitcoind shutdown to complete and flush. A learning moment. Lost a lot of state :-) But no leveldb corruption at least...
07:36 < jonasschnelli> wumpus: hah. yeah. 8GB are some amount of blocks... :) happy catch up...
07:37 < jonasschnelli> as said, im stuck on 382748, and i have two headers-only chains, one at the most recent height of 382761, the other at 382649 (=stuck block +1)
07:39 < bsm1175321> jonasschnelli: Might be worth checking out the code path if a connection gets closed during block download.
07:39 < jonasschnelli> i could restart with -debug=net, but i guess i ruin the error-picture we have here...
07:43 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.]
08:03 < sipa> jonasschnelli: strange
08:03 < sipa> jonasschnelli: does getpeerinfo list any of those blocks as in flight?
08:04 < jonasschnelli> sipa: let me check...
08:04 < sipa> or anything about failed validation in debug.log
08:05 < jonasschnelli> sipa: nope. All inflight array empty.
08:05 < sipa> very strange
08:05 < jonasschnelli> sipa: nothing in the debug log: check here if you wan't: https://bitcoin.jonasschnelli.ch/secp/stuck_debug.log
08:05 < sipa> how long have you been stuck?
08:06 < jonasschnelli> i just checked 1-2h ago and encountered the issue... so height 382748 (where i'm stuck is from today ~13:30)
08:07 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has quit [Remote host closed the connection]
08:08 < jonasschnelli> git log says: 4ee149a6db25cde31432f83369b40c92be13021c + Merge branch 'secp256k1' of https://github.com/sipa/bitcoin
08:08 < sipa> have you restarted the note yet?
08:08 < jonasschnelli> no. i guess this will cure the issue... 
08:08 < sipa> (not that that should be needed, but if it's a bug related due to switchover from IBD to normal sync, that would solve it)
08:08 < jonasschnelli> but i'd like to not ruin the possibility to debug that issue
08:09 < jonasschnelli> as you can see in the debug log, IBD was already done
08:10 < jonasschnelli> but i try to restart now...
08:10 < jonasschnelli> what -debug flags would be helpful? =net?
08:10 < jonasschnelli> (in case the issue shows up again)
08:12 < michagogo> Wtf? https://usercontent.irccloud-cdn.com/file/i4xhIkLw/IMG_3113.PNG
08:17 < jonasschnelli> michagogo : ppa?
08:17 < michagogo> Hm?
08:17 < michagogo> This is in a gitian build
08:18 < jonasschnelli> hu!
08:18 < michagogo> (That's build.log)
08:18  * jonasschnelli thinks michagogo should use a desktop shell to avoid the use of a magnify
08:18 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has joined #bitcoin-core-dev
08:18 < michagogo> jonasschnelli: what?
08:18 < jonasschnelli> Where do we use Qt4.6.4? Aren't the current linux builds not done with qt5?
08:18 < michagogo> (That's a screenshot from me remoting into my laptop from my phone)
08:19 < jonasschnelli> ^^
08:19 < michagogo> jonasschnelli: 0.10.4rc1
08:22 < sipa> jonasschnelli: this may be related to the IsInitialBlovkdownload logic wumpus and suhas have been talking about
08:22 < sipa> see #6971 and #6974
08:23 < jonasschnelli> right.. could be. Restarting the node now...
08:23 < jonasschnelli> (dbcache=6000, takes a while)
08:25 < sipa> yes, leveldb always does a full compaction at startup
08:25 < sipa> rather than at shutdown
08:25 < jonasschnelli> jup... sync up to the "most recent block"
08:26 < jonasschnelli> getchaintips still reports a "headers-only" chain on height (382649 , height I have ben stuck +1).
08:27 < sipa> where are you syncing from?
08:29 < jonasschnelli> sipa: before i restarted i started from genesis (fresh node sync, full IBD)
08:30 < jonasschnelli> It was the 3h22min IBD (https://github.com/bitcoin/bitcoin/pull/6954#issuecomment-154993958)
08:30 < jonasschnelli> with dbcache 6GB
08:31 < jonasschnelli> i keep an eye on that node and will report if it happens again...
08:31 < morcos> jonasschnelli: so that node is still up and running and stuck?
08:31 < sipa> but where is it pulling blocks from?
08:31 < jonasschnelli> morcos: a restart cured the issue
08:31 < morcos> whoops, was behind in my history
08:33 < jonasschnelli> sipa: you mean from which node? I think without the -debug=net tag i can't see the node,.. i just get the UpdateTip log entry
08:34 < sipa> jonasschnelli: so i assume the answer is "random nodes on the internet" :)
08:34 < jonasschnelli> sipa: i have set up the node with standard parameters in a non-firewalled zone.
08:34 < jonasschnelli> right
08:37 < sdaftuar> jonasschnelli: am i right in thinking your node that got stuck had inbound connections?
08:37 < jonasschnelli> sdaftuar: right..
08:37 < jonasschnelli> it was connected to 38 nodes
08:38 < michagogo> Hrm. http://paste.ubuntu.com/13209510/
08:39 < michagogo> cfields: depends doesn't seem to be fetching qt 4.6.4 for the 0.10.4rc1 build
08:41 -!- GAit [~GAit@2-228-102-98.ip191.fastwebnet.it] has quit [Quit: Leaving.]
08:43 -!- GAit [~GAit@2-228-102-98.ip191.fastwebnet.it] has joined #bitcoin-core-dev
08:43 < michagogo> Nevermind
08:44 < michagogo> But do we REALLY need to be using dotfiles for download stamps, in a directory that's dedicated to those?
08:54 -!- GAit [~GAit@2-228-102-98.ip191.fastwebnet.it] has quit [Quit: Leaving.]
08:58 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev
09:10 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev
09:32 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]
09:48 -!- zooko [~user@72.42.70.227] has joined #bitcoin-core-dev
09:48 -!- jgarzik [~jgarzik@172.85.35.242] has joined #bitcoin-core-dev
09:48 -!- jgarzik [~jgarzik@172.85.35.242] has quit [Changing host]
09:48 -!- jgarzik [~jgarzik@unaffiliated/jgarzik] has joined #bitcoin-core-dev
10:01 -!- Arabe [Arabe@190.247.33.220] has joined #bitcoin-core-dev
10:03 -!- Arabe [Arabe@190.247.33.220] has quit [Client Quit]
10:04 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has joined #bitcoin-core-dev
10:07 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev
10:11 -!- rubensayshi [~ruben@91.206.81.13] has quit [Remote host closed the connection]
10:20 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has quit [Read error: Connection reset by peer]
10:20 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has joined #bitcoin-core-dev
10:21 -!- zooko [~user@72.42.70.227] has quit [Read error: Connection reset by peer]
10:23 -!- zooko [~user@72.42.70.227] has joined #bitcoin-core-dev
10:31 < morcos> I posted issued #6976 with some performance estimates.  If we can merge all of these for 0.12, we'll have sped up ConnectBlock by over 400% and CreateNewBlock by 2000%.
10:37 -!- BashCo [~BashCo@unaffiliated/bashco] has quit []
10:38 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev
10:59 -!- zooko [~user@72.42.70.227] has quit [Ping timeout: 240 seconds]
11:11 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has quit [Remote host closed the connection]
11:26 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has joined #bitcoin-core-dev
11:37 -!- skyraider [uid41097@gateway/web/irccloud.com/x-vvtfgzrqhllfkbge] has joined #bitcoin-core-dev
12:12 -!- zooko [~user@208.54.38.140] has joined #bitcoin-core-dev
12:18 -!- tulip [~tulip@46.101.245.204] has joined #bitcoin-core-dev
12:19 < jcorgan> #6973 could use some additional review.  i don't think it is the right approach but would like to see more input from others.
12:32 -!- zooko [~user@208.54.38.140] has quit [Ping timeout: 276 seconds]
12:49 -!- Eliel_ is now known as Eliel
13:03 -!- evoskuil [~evoskuil@c-73-225-134-208.hsd1.wa.comcast.net] has quit [Read error: Connection reset by peer]
13:09 -!- evoskuil [~evoskuil@c-73-225-134-208.hsd1.wa.comcast.net] has joined #bitcoin-core-dev
13:11 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Quit: Leaving]
13:21 -!- zooko [~user@c-71-237-69-190.hsd1.co.comcast.net] has joined #bitcoin-core-dev
13:32 -!- zooko [~user@c-71-237-69-190.hsd1.co.comcast.net] has quit [Ping timeout: 244 seconds]
13:35 -!- ParadoxSpiral_ [~ParadoxSp@p508B9112.dip0.t-ipconnect.de] has quit [Remote host closed the connection]
13:58 -!- jgarzik [~jgarzik@unaffiliated/jgarzik] has quit [Quit: hotel-ward]
14:00 < cfields> gitian signers: osx detached sig for 0.10.4rc1: https://bitcoincore.org/cfields/bitcoin-0.10.4rc1/signature.tar.gz
14:03 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has joined #bitcoin-core-dev
14:27 -!- zooko [~user@70.96.9.174] has joined #bitcoin-core-dev
14:36 -!- zooko` [~user@172.56.8.239] has joined #bitcoin-core-dev
14:37 -!- zooko [~user@70.96.9.174] has quit [Ping timeout: 260 seconds]
14:42 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has quit [Read error: Connection reset by peer]
14:43 -!- zooko` is now known as zooko
14:48 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has joined #bitcoin-core-dev
14:58 -!- dixson3 [~dixson3@cpe-72-182-110-15.austin.res.rr.com] has quit [Ping timeout: 252 seconds]
15:08 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has quit [Quit: Leaving.]
15:18 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)]
15:39 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has joined #bitcoin-core-dev
15:41 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has quit [Client Quit]
15:41 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has joined #bitcoin-core-dev
15:50 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has quit [Quit: Leaving.]
16:15 -!- zooko` [~user@70.96.9.174] has joined #bitcoin-core-dev
16:16 -!- zooko [~user@172.56.8.239] has quit [Ping timeout: 276 seconds]
16:17 -!- zooko` is now known as zooko
16:28 -!- zooko [~user@70.96.9.174] has quit [Read error: Connection reset by peer]
16:30 -!- zooko` [~user@70.96.9.174] has joined #bitcoin-core-dev
16:31 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has joined #bitcoin-core-dev
16:33 -!- zooko` is now known as zokoo
16:33 -!- zokoo is now known as zooko
16:53 -!- Guest51134 is now known as pigeons
17:08 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has quit [Quit: Leaving.]
17:16 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has joined #bitcoin-core-dev
17:16 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has quit [Client Quit]
17:34 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-macuigubwwfjmatj] has quit [Quit: Connection closed for inactivity]
17:42 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has joined #bitcoin-core-dev
17:56 < PRab> no surprise, but running 0.11.2rc1 uneventfully.
17:56 < gmaxwell> Likewise.
17:58 < PRab> If you guys want, I can crash my computer. I have been hit by the DB corruption bug several times and it looks like this release might fix that.
18:00 < btcdrak> PRab, great.
18:00 -!- CodeShark_ [~CodeShark@cpe-76-167-237-202.san.res.rr.com] has joined #bitcoin-core-dev
18:01 < PRab> btcdrak: Great that its running, or great that I can test crashing?
18:01 < btcdrak> that it is running great
18:01 < gmaxwell> PRab: yes, it should fix most of the corruption reports on windows. All except the anti-virus related ones, as far as we know.
18:01 -!- CodeShark is now known as Guest30488
18:02 -!- CodeShark_ [~CodeShark@cpe-76-167-237-202.san.res.rr.com] has quit [Client Quit]
18:02 -!- CodeShark_ [CodeShark@cpe-76-167-237-202.san.res.rr.com] has joined #bitcoin-core-dev
18:02 -!- CodeShark_ [CodeShark@cpe-76-167-237-202.san.res.rr.com] has quit [Client Quit]
18:08 -!- Guest30488 [~androirc@cpe-76-167-237-202.san.res.rr.com] has quit [Quit: AndroIRC - Android IRC Client ( http://www.androirc.com )]
18:09 -!- CodeShark_ [CodeShark@cpe-76-167-237-202.san.res.rr.com] has joined #bitcoin-core-dev
18:09 -!- CodeShark_ [CodeShark@cpe-76-167-237-202.san.res.rr.com] has quit [Client Quit]
18:09 -!- CodeShark [CodeShark@cpe-76-167-237-202.san.res.rr.com] has joined #bitcoin-core-dev
18:15 -!- zooko [~user@70.96.9.174] has quit [Remote host closed the connection]
18:21 -!- zooko [~user@70.96.9.174] has joined #bitcoin-core-dev
18:25 < GitHub106> [bitcoin] theuni opened pull request #6978: Alternative fix for #6248 (qt+fPIE) (master...qt-pie) https://github.com/bitcoin/bitcoin/pull/6978
18:56 -!- CodeShark [CodeShark@cpe-76-167-237-202.san.res.rr.com] has quit [Ping timeout: 250 seconds]
19:01 -!- CodeShark [CodeShark@cpe-76-167-237-202.san.res.rr.com] has joined #bitcoin-core-dev
19:07 -!- guest234234 [~guest2342@223.207.200.123] has joined #bitcoin-core-dev
19:09 -!- zooko` [~user@172.56.9.100] has joined #bitcoin-core-dev
19:12 -!- zooko`` [~user@70.96.9.174] has joined #bitcoin-core-dev
19:13 -!- zooko [~user@70.96.9.174] has quit [Ping timeout: 276 seconds]
19:16 -!- zooko` [~user@172.56.9.100] has quit [Ping timeout: 255 seconds]
19:21 -!- zooko`` [~user@70.96.9.174] has quit [Ping timeout: 255 seconds]
19:50 -!- zooko [~user@2601:281:8001:26aa:3c89:60d9:cbe:edd1] has joined #bitcoin-core-dev
19:56 -!- zooko [~user@2601:281:8001:26aa:3c89:60d9:cbe:edd1] has quit [Ping timeout: 240 seconds]
20:06 -!- zooko` [~user@2601:281:8001:26aa:3c89:60d9:cbe:edd1] has joined #bitcoin-core-dev
20:15 -!- CodeShark [CodeShark@cpe-76-167-237-202.san.res.rr.com] has quit [Ping timeout: 246 seconds]
20:26 -!- tulip [~tulip@46.101.245.204] has quit [Remote host closed the connection]
20:31 -!- guest234234 [~guest2342@223.207.200.123] has quit [Ping timeout: 265 seconds]
21:02 -!- skyraider [uid41097@gateway/web/irccloud.com/x-vvtfgzrqhllfkbge] has quit [Quit: Connection closed for inactivity]
21:08 -!- zooko` [~user@2601:281:8001:26aa:3c89:60d9:cbe:edd1] has quit [Ping timeout: 246 seconds]
21:12 -!- tulip [~tulip@46.101.245.204] has joined #bitcoin-core-dev
21:39 -!- guest234234 [~guest2342@171.5.159.71] has joined #bitcoin-core-dev
22:23 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-wtmiirdfedouefgi] has joined #bitcoin-core-dev
22:46 -!- fkhan [weechat@gateway/vpn/mullvad/x-urggymssigpspxaw] has quit [Ping timeout: 260 seconds]
22:50 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Ping timeout: 246 seconds]
22:51 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev
22:53 -!- CodeShark [~androirc@100.9.177.117] has joined #bitcoin-core-dev
23:05 -!- guest234234 [~guest2342@171.5.159.71] has quit [Ping timeout: 240 seconds]
23:09 -!- tulip [~tulip@46.101.245.204] has quit []
23:13 -!- fkhan [weechat@gateway/vpn/mullvad/x-aopqxjyqxklngfzi] has joined #bitcoin-core-dev
23:13 -!- CodeShark_ [~CodeShark@cpe-76-167-237-202.san.res.rr.com] has joined #bitcoin-core-dev
23:14 -!- CodeShark [~androirc@100.9.177.117] has quit [Read error: Connection reset by peer]
23:15 -!- CodeShark [~androirc@100.9.177.117] has joined #bitcoin-core-dev
23:17 -!- CodeShark_ [~CodeShark@cpe-76-167-237-202.san.res.rr.com] has quit [Ping timeout: 240 seconds]
23:32 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.]
23:33 -!- CodeShark [~androirc@100.9.177.117] has quit [Quit: AndroIRC - Android IRC Client ( http://www.androirc.com )]