--- Log opened Wed Mar 06 00:00:07 2019 00:32 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz] 00:34 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 00:36 < wumpus> Binary files achow101/aarch/bitcoin-0.18.0rc1/bin/test_bitcoin and laanwj/aarch/bitcoin-0.18.0rc1/bin/test_bitcoin differ 00:36 < wumpus> Binary files achow101/riscv/bitcoin-0.18.0rc1/bin/test_bitcoin and laanwj/riscv/bitcoin-0.18.0rc1/bin/test_bitcoin differ 00:36 < wumpus> that's all, apparently 00:38 -!- jungly [~quassel@79.8.200.97] has joined #bitcoin-core-dev 00:42 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 00:45 < gmaxwell> whats the difference look like? 00:45 < gmaxwell> maybe you can see that its a timestamp or something like that. 00:45 < gmaxwell> Are they the same size? 00:52 < wumpus> unfortunately ,no they're different sizes, https://github.com/bitcoin/bitcoin/issues/15541 00:53 < gmaxwell> [offtopic] NSA released an apparently really good reverse engineering / decompiler tool. Bonus: Contains backdoor (apparently unintentional), network accessible RCE. ( https://twitter.com/hackerfantastic/status/1103087869063704576 ) 00:55 < wumpus> amusing, this is as close as you can get to the actual trojan horse story in the modern day 00:56 < gmaxwell> comments on HN were like "oh I dunno if I want to run this, it's from the NSA" which I read and thought, "oh come on thats a bit silly"... then scrolls down a bit further. 01:01 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 01:01 < bitcoin-git> [bitcoin] Bushstar opened pull request #15544: Comment typo "iff" (master...master) https://github.com/bitcoin/bitcoin/pull/15544 01:01 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 01:01 < wumpus> [extreme paranoia mode: they found one of the RCEs quickly so people think it's safe now] 01:03 < gmaxwell> a RE tool also has a lot of attack surface, even with it closed off from the network, ... the whole point is to feed it untrusted inputs. Wouldn't be shocking for a debugger to have an RCE facing the instruction stream. 01:04 < wumpus> yes, very much true 01:04 < gmaxwell> though presumably anyone using this could manage to isolate it reasonably enough. it sounds pretty cool, esp that it supports weird cpus. 01:15 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 246 seconds] 01:15 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 255 seconds] 01:16 < wumpus> yes it looks nice... I'm all for NSA getting into the 'show off capability by releasing cool things' game instead of by leaks of spying and sabotage, though, can't help being skeptical of their motives 01:16 < sipa> gmaxwell: that's hilarious 01:17 -!- promag [~promag@bl23-83-33.dsl.telepac.pt] has joined #bitcoin-core-dev 01:20 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 01:24 < wumpus> aanyhow back to comparing executables using bog-standard unix tools 01:25 < sipa> can we somehow tell gitian it's ok if only the tests are nondeterministic? 01:26 < sipa> i guess we don't actually want that 01:26 < wumpus> I don't think that's okay, all the binaries we distribute should be deterministic 01:26 < wumpus> right 01:29 < wumpus> the difference seems to be minimal: presence/absence of .gnu_debuglink section: https://github.com/bitcoin/bitcoin/issues/15541#issuecomment-470034776 01:30 -!- Deinogalerix21 [~Deinogale@89.238.176.150] has joined #bitcoin-core-dev 01:32 < wumpus> this is the case for both platforms; apparently, mine doesn't have the section but his does 01:32 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 01:33 -!- mmgen [~mmgen@gateway/tor-sasl/mmgen] has joined #bitcoin-core-dev 01:35 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev 01:38 < wumpus> so the good news is that the generated code itself doesn't diverge 01:38 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 01:40 < gmaxwell> add a bit of script to strip that section? 01:42 < wumpus> same for the divergence between my own previous and current builds, except that affects bitcoin-qt 01:43 < wumpus> gmaxwell: yea that seems the most straightforward option 01:43 -!- Zenton [~user@unaffiliated/vicenteh] has joined #bitcoin-core-dev 01:44 < gmaxwell> or find what compiler option controls the creation of that section and set it explicitly, I'm gussing different people's toolchains have changed the defaults on it 01:44 < wumpus> the script that's suppposed to do this is contrib/devtools/split-debug.sh.in 01:44 < wumpus> but this is a deterministic build, we're supposed to use the same toolchain 01:45 < wumpus> the build environment should be exactly the same (ubuntu bionic) 01:45 < wumpus> I don't dare guess what does cause this though … 01:49 < gmaxwell> hm. maybe the part of the buildchain that has been identically built doesn't include those particular cross compilers? 01:53 < wumpus> right, this is why I'm saying "should be" I'm not 100% sure if there isn't something non-deterministic leaking into the toolchain, though it might also be just as well something from the environment (races between threads, ordering of files in file system, system locale, ... we've seen them all by now) 01:54 < wumpus> it's absurd how difficult determninistic builds are to get right, a few days ago I saw a tweet like "oh fix time at epoch 0 lol" and almost cried :-) 01:55 < gmaxwell> this complexity ultimately impacts all software.. basically everything running everywhere is running an an untested configuration due to all these factors. 02:01 -!- kexkey [~kexkey@68.168.122.228] has quit [Read error: Connection reset by peer] 02:02 < wumpus> yes it's true, would have been better if various tools had been written with determinism in mind, it's kind of a hard thing to bolt on later 02:03 < wumpus> the thing is, it's so easy to use a randomized algorithms somewhere without noticing; e.g. various hash tables that are seeded with random nonces, then only something has to accidentially use the order and whoops 02:06 < gmaxwell> filesystem ordering is the funnest stuff. 02:06 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 240 seconds] 02:06 < wumpus> yes 02:11 -!- OneFive [~OneFive@cpc87991-haye25-2-0-cust817.17-4.cable.virginm.net] has quit [Ping timeout: 255 seconds] 02:12 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 02:22 < wumpus> so this is curious: the gnu-debuglink section is *supposed* to be explicitly inserted here @OBJCOPY@ --enable-deterministic-archives -p --add-gnu-debuglink=$3 $2 02:23 < wumpus> that it is missing from my build seems to be a bug 02:26 < luke-jr> are you sure you were using the current yml from the tag? 02:26 < wumpus> yes 02:32 -!- noxx_ [~noxx@p57A6109A.dip0.t-ipconnect.de] has quit [Remote host closed the connection] 02:32 -!- natangl [b0e70b30@gateway/web/freenode/ip.176.231.11.48] has joined #bitcoin-core-dev 02:33 < wumpus> but that's a good point, I can actually edit the descriptor without changing the release otherwise 02:33 < wumpus> (for experimenting ..) 02:33 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 02:35 < wumpus> at minimum to build riscv and aarch only to minimize the iteration time… 02:37 < wumpus> which might reduce to half a day instead of a full day :/ 02:39 -!- timothy [~tredaelli@redhat/timothy] has quit [Read error: Connection reset by peer] 02:40 < wumpus> does the "Upgrading system, may take a while (log in var/install.log)" step take so long for anyone else? 02:40 < wumpus> it always seemse to me (don't think it's really true) that this takes lnoger than the actual build, at least with dependencies cached 02:40 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 02:41 < luke-jr> wumpus: it takes annoyingly long for me, yes 02:42 < luke-jr> I haven't actually timed it, though, just noticed it while I was waiting 02:42 < wumpus> luke-jr: I guess it's a LXC thing, maybe the docker builds don't have this? what is everyone using nowadays? 02:42 < luke-jr> wumpus: I don't use LXC 02:42 < wumpus> I feel like completely nuking this VM and starting over 02:42 < luke-jr> I use KVM 02:42 < wumpus> oh, same there then 02:42 < luke-jr> well, part of why it takes long for me, is *because* it nukes the VM every time :P 02:43 < wumpus> I mean the outer VM where I run gitian in 02:43 < wumpus> I'm aware that's the whole point of gitian, too :) 02:43 < wumpus> maybe it's not thorough enough ! 02:43 -!- ExtraCrispy [~ExtraCris@gateway/tor-sasl/extracrispy] has quit [Ping timeout: 256 seconds] 02:45 < luke-jr> I like the Guix direction 02:46 < wumpus> me too, I genuinely hope it will make things better, though I must also confess being a bit skeptical, replacing a system that almost works (after years of polishing) with a shiny new thing rarely 'just works' 02:48 < promag> wumpus: yeah, Qt folks dropped Qbs development in favour of cmake just because "a shiny new thing rarely 'just works'" 02:49 < luke-jr> Qbs? 02:49 < luke-jr> is that qmake? 02:50 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 02:52 < promag> nop 02:53 < promag> example https://doc.qt.io/qbs/howtos.html#how-do-i-make-my-app-build-against-my-library 02:53 < wumpus> promag: on the long run that's probably a good choice, qt having their own build system is kind of annoying, but yes I can imagine there's a lot of initial breakage and frustration 02:53 < promag> qbs uses qml 02:53 < luke-jr> so Qt had *two* build systems? <.< 02:54 < gmaxwell> there is just an effect where no one realizes how much the existing stuff gets right because you don't see the right parts. ... also much of what people see as "cruft" is actually stored knoweldge about weird corner cases that must be handled. 02:54 < promag> blog post https://blog.qt.io/blog/2018/10/29/deprecation-of-qbs/ 02:54 * wumpus wishes boost would switch away from their own yam or whatever it is as well to something generic 02:55 < promag> luke-jr: they say "Longer term, we plan to switch to CMake for building Qt itsel" 02:56 < wumpus> gmaxwell: that certianly happens 02:57 < wumpus> in the case of gitian the problem is the high overhead, gitian itself is pretty minimalistic, but it spins up a complete Ubuntu VM and updates it to current packages, that's slow and soo many moving (potentially backdoored) parts 02:58 < gmaxwell> yea... I've never been impressed by the gitian approach. 02:58 < gmaxwell> also the need to update the vm amplfies risk a lot. It achieves the purpose of making a backdoored binary provably not any of our own faults, but doesn't increase security as much as it could. 02:59 < gmaxwell> (esp since more expirence with ubuntu packaging security has certantly not increased my confidence there... :) ) 02:59 < wumpus> also the packages used to build are not themselves built deterministically 03:00 < wumpus> no, I'm not too confident there either, ubuntu was never a good choice there, it just was convenient, given the amount of work people were actually spending on this, I mean in all those years it's still the only thing we have 03:00 < gmaxwell> yep 03:00 < wumpus> (not trying to blame anyone specifically there, it's just not a very popular thing) 03:02 < gmaxwell> well we were pretty much the first project doing determinstic builds that I'm aware of... and even today in spite of huge effort and hype, there is still a long way to go ecosystem wise. I don't believe there is yet any 'full' (even minimal) linux distro that is reproducably built. 03:03 -!- promag [~promag@bl23-83-33.dsl.telepac.pt] has quit [Remote host closed the connection] 03:05 -!- natangl [b0e70b30@gateway/web/freenode/ip.176.231.11.48] has quit [Quit: Page closed] 03:06 < wumpus> it's true; I think we were the first open source project doing this, even tor used gitian for a while for deterministic builds though they switched to some other system now 03:06 < Sentineo> gmaxwell: I saw a video last week about reproducable builds and debian has 80% I think they stated of the repos build that way now and the tor project is working on it as well. Fdroid has something similar, too. Let meg find the link. 03:07 -!- jonatack [6dca6b0f@gateway/web/freenode/ip.109.202.107.15] has joined #bitcoin-core-dev 03:07 < wumpus> huh what I read is that debian managed to get 4% of the packages deterministic 03:07 < wumpus> they were having lots of trouble with it 03:08 < wumpus> given how many packages they have to build it's a pretty impressive number, still 03:08 < Sentineo> ah it is 2015 talk, but still ... https://www.youtube.com/watch?v=ilu6yMBGS6I&feature=youtu.be 03:08 * wumpus doesn't even succeed in making the bitcoin core build deterministic so who am I to complain ... 03:09 < gmaxwell> my comment was mostly just "this is absurdly hard" so much effort has been put at it, the fact that it's not 99% successful already shows that its hard. 03:09 < wumpus> yep, exactly 03:10 < wumpus> many people go into it very optimistically, then they start running into edge cases 03:13 < wumpus> whaaaaat . . . ... if I *only* build riscv64 and aarch64 I get the same output as the rest 03:13 < wumpus> I should not only nuke the VM but physically burn this computer too 03:13 < gmaxwell> lol 03:14 < gmaxwell> hm maybe some intemediate output from different builds is getting mixed up? 03:15 < wumpus> it's very possible, the curious thing is that those two platforms are last (being the most recently added) 03:15 < gmaxwell> I wonder if everyone else did the builds seperately and it would be consistent if they were all done at once? 03:16 < wumpus> but that makes it *more likely* they're influenced by earlier things 03:16 < wumpus> nah the same descriptor builds all platforms, the only way to build them separately is to hack the descriptor, I doubt everyone else did that :) 03:18 < wumpus> ideally you'd want to create a new, clean environment every time (as often as possible, so definitely between different platform builds), as soon as there is less overhead to that we should do that 03:18 < wumpus> currently that means adding 30-60 minutes of VM setup in between so I understand why it's merged into as few descriptors as possible 03:20 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 03:22 -!- Deinogalerix21 [~Deinogale@89.238.176.150] has quit [Quit: WeeChat 2.4] 03:25 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 03:25 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev 03:26 -!- zhangzf [~zhangzf@106.38.157.147] has quit [Remote host closed the connection] 03:26 -!- zhangzf [~zhangzf@106.38.157.147] has joined #bitcoin-core-dev 03:26 -!- zhangzf [~zhangzf@106.38.157.147] has quit [Remote host closed the connection] 03:29 -!- Soligor_ [~soligor@unaffiliated/soligor] has joined #bitcoin-core-dev 03:31 -!- Soligor [~soligor@unaffiliated/soligor] has quit [Ping timeout: 246 seconds] 03:40 < wumpus> in any case my suspicion is that something local here is preventing add-gnu-debuglink from working in some cases; I'd recommend to not make this a blocker for getting rc1 out 03:44 < wumpus> there's no `set -e` at the top of that split-debug.sh script, so say objdump fails (for what ever reason), the error will go unnoticed! 03:45 < wumpus> (also: and what does find -exec ... do when its command fails with error status? does it fail) 03:45 -!- Soligor_ [~soligor@unaffiliated/soligor] has quit [Remote host closed the connection] 03:51 < wumpus> "find" ignores errors as well, okay, I don't even have an idea how to make errors propagate up the chain here 03:53 < gmaxwell> interesting, errors in -exec can be used to filter the output of find from extra stages, I don't think I realized that. 03:53 < gmaxwell> e.g. find ./ -exec true \; -print prints everything but using false prints nothing. 03:54 < wumpus> oh! 04:00 < wumpus> apparently the solution to find -exec error propagation is to use 'xargs' instead 04:01 < gmaxwell> thats why I don't have much -exec expirence-- I've always used xargs. (Also -0 option ftw) 04:02 < wumpus> right, switching to that 04:03 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 04:03 < bitcoin-git> [bitcoin] Sjors opened pull request #15545: [doc] explain why CheckBlock() is called before AcceptBlock (master...2019/03/clarify-checkblock) https://github.com/bitcoin/bitcoin/pull/15545 04:03 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 04:03 -!- promag [~promag@83.223.250.247] has joined #bitcoin-core-dev 04:03 < wumpus> find ${DISTNAME}/bin -type f -executable -print0 | xargs -0 -n1 -I{} ../contrib/devtools/split-debug.sh {} {} {}.dbg 04:04 < wumpus> then adding a 'set -e' at top of that script and it should cause the build to stop if any of the objdump commands fails... 04:04 < wumpus> objcopy* 04:06 < wumpus> silently ignoring errors should be the worst sin in computing 04:08 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 04:08 -!- OneFive [~OneFive@cpc87991-haye25-2-0-cust817.17-4.cable.virginm.net] has joined #bitcoin-core-dev 04:09 -!- jerem_ [~jerem@cpc147796-finc20-2-0-cust107.4-2.cable.virginm.net] has joined #bitcoin-core-dev 04:10 -!- OneFive_ [~OneFive@cpc87991-haye25-2-0-cust817.17-4.cable.virginm.net] has joined #bitcoin-core-dev 04:12 -!- jerem_ [~jerem@cpc147796-finc20-2-0-cust107.4-2.cable.virginm.net] has left #bitcoin-core-dev ["Leaving"] 04:13 -!- OneFive [~OneFive@cpc87991-haye25-2-0-cust817.17-4.cable.virginm.net] has quit [Ping timeout: 255 seconds] 04:17 < promag> provoostenator: are you still using boost::process? 04:18 < provoostenator> promag: waiting for more feedback on #15440, I'm fine with any solution really, preferably one that minimizes headache. 04:18 < gribble> https://github.com/bitcoin/bitcoin/issues/15440 | RFC including boost-process · Issue #15440 · bitcoin/bitcoin · GitHub 04:19 < promag> kk 04:20 < wumpus> nice ! 04:20 < provoostenator> It seems boost::process is overkill for what I need it for (pass stuff into a command as arguments or stdin, consume its std::out) 04:20 < promag> overkill? how so? 04:21 < provoostenator> promag: as I explain in that Github issue, it's a _lot_ of code 04:21 < provoostenator> With dependencies all over Boost itself, unclear how much that overlap with what we already consume. 04:22 < provoostenator> But it does Work(tm) 04:22 < luke-jr> if something else better is made, we can always switch later 04:22 < provoostenator> And boost things often make it to c++ standards, although afaik there's not progress on that front for process. 04:22 < luke-jr> doubt there will be 04:22 < provoostenator> luke-jr: I'm not worried about switching cost, I'm worried about how much review work it takes to use this. 04:23 < luke-jr> processes are foreign to C at least 04:23 < wumpus> "But it does Work(tm)" this part is usually undersnowed 04:23 < promag> provoostenator: I'll rework #13339 (maybe a different branch) to also use boost::process 04:23 < gribble> https://github.com/bitcoin/bitcoin/issues/13339 | wallet: Replace %w by wallet name in -walletnotify script by promag · Pull Request #13339 · bitcoin/bitcoin · GitHub 04:23 < luke-jr> promag: why? 04:23 < wumpus> so much talk about which dependency to use and so little about the actual feature :( 04:23 < luke-jr> that is working fine, except for escaping stuff, which boost::process doesn't add afaiki 04:24 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 04:24 < gmaxwell> I thougth the plan of record we to just get it working however and worry about the exact mechenism to use fork() later? 04:25 < wumpus> yes ^^ 04:25 < promag> luke-jr: ok, another branch then.. I think %w is kind of lame, I want to try env var instead 04:25 < gmaxwell> certantly we _can_ solve this, one way or another. 04:26 < provoostenator> gmaxwell: that's my plan as well, I'll just keep working on the hardware wallet support stuff 04:29 < provoostenator> And I made a seperate PR & issue for the boost:process stuff in order to deflect that discussion away from the feature. 04:30 < provoostenator> I wish there was an easier way to do nested PRs, but otherwise it's not blocking. 04:30 < wumpus> thanks, makes sense 04:35 -!- OneFive_ [~OneFive@cpc87991-haye25-2-0-cust817.17-4.cable.virginm.net] has quit [Ping timeout: 255 seconds] 04:36 -!- zhangzf [~zhangzf@223.72.36.250] has joined #bitcoin-core-dev 04:38 < wumpus> okay I'm lost now, what causes the gitian descriptor to stop building? does a command failing even do that? I had a typo in my descriptor causing find to *completely fail* (find: missing argument to `-exec') and it still continued building 04:39 < gmaxwell> IT CANNOT BE STOPPED. RUN RUN AND HIDE 04:40 < wumpus> now you're saying, CTRL-C didn't stop it either. OH NO I think you're right! 04:40 < provoostenator> Yeah, the unstoppable nature of Gitian builds has been noticed before. Resetting the VM helps :-) 04:42 < luke-jr> is it a bug that the "rc1" was added to zips, but not installer exes? 04:50 < wumpus> luke-jr: I think that's a bug 04:50 -!- IGHOR [~quassel@93.178.216.72] has quit [Ping timeout: 245 seconds] 04:51 -!- IGHOR [~quassel@93.178.216.72] has joined #bitcoin-core-dev 04:52 < wumpus> provoostenator: well it was almost done; most shocking to me was that a failing command didn't cause it to stop, it still built *some* output 04:54 < provoostenator> luke-jr: for which distro? Afaik bitcoind and bitcoin-cli never include a version number. 04:55 < wumpus> I think he means to the filenames? 04:55 < provoostenator> The tar.gz names? 04:55 -!- promag [~promag@83.223.250.247] has quit [Remote host closed the connection] 04:56 < luke-jr> bitcoin-0.18.0-win32-setup-unsigned.exe bitcoin-0.18.0rc1-win32.zip bitcoin-0.18.0-win64-setup-unsigned.exe bitcoin-0.18.0rc1-win64.zip 04:56 < wumpus> no, the installer exe names 04:56 < provoostenator> File naming has some other issues too, in some places it doesn't include the patch version. See: https://github.com/bitcoin-core/docs/issues/18 04:57 < provoostenator> (but that's another issue that the installers) 04:57 < wumpus> I vaguely rememebr that one was fixed, not 100% sure though 04:58 < luke-jr> same 04:58 < luke-jr> pretty sure that was what fixed the rcN being added too 04:58 < provoostenator> What was fixed was a bug with the sub patch version, e.g. 0.17.0.1 04:58 < luke-jr> I had to modify my build scripts not to rename.. 04:59 < provoostenator> (I guess we use semver differently, with the second digit being called the major version) 05:00 < provoostenator> 0.MAJOR.MINOR.PATCH, so the issue we fixed was that the patch version was ignored in 0.17.0.1. We still have an issue with missing minor version in some Gitian path names. 05:01 < wumpus> I've never heard of that one 05:01 < wumpus> you'd say being unable to distinguish minor versions would be extremely apparent 05:01 < luke-jr> the caches intentionally don't use MINOR.PATCH .. 05:01 < provoostenator> #14612 05:01 < gribble> https://github.com/bitcoin/bitcoin/issues/14612 | Include full version number in released file names by achow101 · Pull Request #14612 · bitcoin/bitcoin · GitHub 05:03 < provoostenator> The unsolved one is that we still use "bitcoin-linux-0.18-build.assert.sig" instead of "bitcoin-linux-0.18.0-build.assert.sig" 05:03 < luke-jr> #15546 should probably get a 0.18 tag 05:03 < gribble> https://github.com/bitcoin/bitcoin/issues/15546 | gitian: Windows installer EXE filenames lack "rcN" suffix · Issue #15546 · bitcoin/bitcoin · GitHub 05:03 < luke-jr> provoostenator: that's not a problem 05:03 < provoostenator> luke-jr: it's marginally annoying, but I agree not really a problem. 05:04 < provoostenator> I just need to brush up my bash to take only the first two digits from $VERSION in https://github.com/bitcoin-core/docs/issues/18 05:06 < luke-jr> I don't think --output is needed at all? and you can just use *.assert 05:06 < luke-jr> also, is there a reason you're leaving off the last character in --detach-sign ? 05:13 -!- tferghrt [01c8cb48@gateway/web/freenode/ip.1.200.203.72] has joined #bitcoin-core-dev 05:38 -!- elichai2 [uid212594@gateway/web/irccloud.com/x-scrrbfxilpuezfuz] has joined #bitcoin-core-dev 05:46 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 05:46 < bitcoin-git> [bitcoin] instagibbs opened pull request #15547: Switch wallet default to reject too-long transaction chains for mempool (master...walletreject_true) https://github.com/bitcoin/bitcoin/pull/15547 05:46 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 05:47 < wumpus> okay, phew, at least putting random garbage into the descriptor script at the top causes it to fail the build, maybe it's something with the for loop over platforms that causes the error to be ignored 05:52 < fanquake> ignoring errors :o 05:56 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 244 seconds] 05:57 -!- jonatack [6dca6b0f@gateway/web/freenode/ip.109.202.107.15] has quit [Ping timeout: 256 seconds] 05:57 < wumpus> fanquake: yes; while editing the descriptor I made a typo in the find syntax, I'm sure that returns error status, but the build kept continuing, trying to figure out why now (I really want the build to stop on errors, even minor ones) 05:58 < wumpus> this is taking 10x as much time as it should because of gitian's VM setup overhead... 05:59 < fanquake> :/ 05:59 < wumpus> hm I guess it's possible to re-use the image if the output doesn't matter 06:02 -!- jonatack [6dca6b0f@gateway/web/freenode/ip.109.202.107.15] has joined #bitcoin-core-dev 06:03 < wumpus> OHHHHH I see the problem. `find -exec | xargs -0` returns exec status 0 despite find's error, after all, a pipe will return the exit status of the last command 06:03 < wumpus> *cries* 06:05 < wumpus> so what I managed to do: failures in the 'split-debug.sh' script will now make it upstream and cause the build to stop 06:06 < wumpus> what I managed to mess up: failures in the find itself will no longer be propagated 06:06 < wumpus> welcome to shell hell, one step forward, one step backward ... 06:07 < fanquake> Don't worry, deterministic building is "easy" 06:07 < wumpus> yesss, only a matter of setting time to 0 right 06:09 < fanquake> Nice quote from HN: "One has to step back and ask: "What made you decide to introduce non-determinism into your compilation process in the first place?"" 06:09 < fanquake> ... 06:10 < wumpus> ha 06:12 < wumpus> "One has to step back and ask: what made you decide to let water into your boat in the first place?" 06:18 < wumpus> anyhow, with this in place I'm going to do the full linux build again, hopefully the problem will have magically disappeared (heisenbug), or it will exit due to an error in objcopy 06:20 < fanquake> sounds good, maybe a quick fix then 06:21 < wumpus> hopefully 06:35 -!- shesek [~shesek@141.226.146.161] has joined #bitcoin-core-dev 06:35 -!- shesek [~shesek@141.226.146.161] has quit [Changing host] 06:35 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 06:37 < wumpus> TIL bash has `set -o pipefail` to fail a command if any of the stages of the pipe fails 06:38 < provoostenator> luke-jr: good catch re "--detach-sig", will fix now and then test when the signed binaries are out 06:43 < provoostenator> luke-jr: TIL gpg on macOS accepts --detach-sig as an alias for --detach-sign . Undocumented and seems to be left over from older versions. 06:48 < luke-jr> probably backdoored too 06:49 < luke-jr> gpg seems to accept --anything if it's an unambiguous prefix 07:03 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [] 07:15 -!- jonatack [6dca6b0f@gateway/web/freenode/ip.109.202.107.15] has quit [Ping timeout: 256 seconds] 07:28 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 07:29 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 07:30 -!- ExtraCrispy [~ExtraCris@gateway/tor-sasl/extracrispy] has joined #bitcoin-core-dev 07:36 -!- zhangzf [~zhangzf@223.72.36.250] has quit [Remote host closed the connection] 07:37 -!- Skirmant [~Skirmant@78-62-14-181.static.zebra.lt] has joined #bitcoin-core-dev 07:40 -!- zhangzf [~zhangzf@223.72.49.142] has joined #bitcoin-core-dev 07:41 -!- d_t [~d_t@108-65-77-11.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev 07:49 -!- promag [~promag@195.54.168.134] has joined #bitcoin-core-dev 08:00 -!- kexkey [~kexkey@68.168.122.228] has joined #bitcoin-core-dev 08:10 < wumpus> so… it all turned out to be a VM disk space issue: https://github.com/bitcoin/bitcoin/issues/15541#issuecomment-470160960 08:16 -!- jarthur [~jarthur@207.114.244.5] has joined #bitcoin-core-dev 08:24 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has joined #bitcoin-core-dev 08:25 -!- ArdeshirV [~Ardeshir@37.59.65.0] has joined #bitcoin-core-dev 08:26 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #bitcoin-core-dev 08:30 -!- kexkey [~kexkey@68.168.122.228] has quit [Quit: Scaling pentatonically] 08:31 -!- kexkey [~kexkey@68.168.122.228] has joined #bitcoin-core-dev 08:31 -!- jarthur [~jarthur@207.114.244.5] has quit [Quit: brb] 08:34 < andytoshi> i'd like to start a wiki page or github issue or something to collect a wishlist for a bip174/psbt extension BIP draft. where is the best place to do that? 08:45 -!- kexkey [~kexkey@68.168.122.228] has quit [Quit: Scaling pentatonically] 08:54 -!- ArdeshirV [~Ardeshir@37.59.65.0] has quit [Quit: Leaving] 08:55 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 240 seconds] 08:55 -!- ArdeshirV [~Ardeshir@37.59.65.0] has joined #bitcoin-core-dev 08:56 -!- ArdeshirV [~Ardeshir@37.59.65.0] has quit [Max SendQ exceeded] 08:57 -!- ArdeshirV [~Ardeshir@37.59.65.0] has joined #bitcoin-core-dev 08:58 -!- kexkey [~kexkey@68.168.122.228] has joined #bitcoin-core-dev 08:58 -!- jonatack [b9cee13b@gateway/web/freenode/ip.185.206.225.59] has joined #bitcoin-core-dev 08:59 -!- ArdeshirV [~Ardeshir@37.59.65.0] has left #bitcoin-core-dev [] 09:00 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 240 seconds] 09:05 -!- jarthur [~jarthur@207.114.244.5] has joined #bitcoin-core-dev 09:05 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 09:13 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev 09:23 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 09:23 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #15548: build: use full version string in setup.exe (master...1903-winVer) https://github.com/bitcoin/bitcoin/pull/15548 09:23 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 09:28 -!- zhangzf [~zhangzf@223.72.49.142] has quit [Remote host closed the connection] 09:29 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 09:29 < bitcoin-git> [bitcoin] laanwj opened pull request #15549: gitian: Improve error handling (master...2019_03_gitian_error_handling) https://github.com/bitcoin/bitcoin/pull/15549 09:29 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 09:30 < wumpus> #15549 09:30 < gribble> https://github.com/bitcoin/bitcoin/issues/15549 | gitian: Improve error handling by laanwj · Pull Request #15549 · bitcoin/bitcoin · GitHub 09:31 < wumpus> andytoshi: that's a good question, normally the bitcoin-dev mailing list would be the best place to solicit feedback like that, but now that it's not working I don't really know 09:33 < sipa> wumpus: it's working again 09:33 < sipa> i think? 09:37 < andytoshi> cool, if it's working i'll use the ML 09:38 < wumpus> but you could also ask in the meeting tomorrow, for example 09:38 < andytoshi> I think i'll be in flight during the meeting unfortunately 09:38 < wumpus> or some other week 09:42 -!- pinheadmz [~matthewzi@96-82-67-198-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 09:47 -!- gleb_ is now known as gleb 09:55 -!- kexkey [~kexkey@68.168.122.228] has quit [Quit: Scaling pentatonically] 09:56 -!- kexkey [~kexkey@68.168.122.228] has joined #bitcoin-core-dev 10:03 -!- setpill [~setpill@unaffiliated/setpill] has quit [Quit: o/] 10:12 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 10:13 -!- rh0nj [~rh0nj@88.99.167.175] has joined #bitcoin-core-dev 10:20 -!- jungly [~quassel@79.8.200.97] has quit [Remote host closed the connection] 10:34 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has joined #bitcoin-core-dev 10:35 -!- jonatack [b9cee13b@gateway/web/freenode/ip.185.206.225.59] has left #bitcoin-core-dev [] 10:36 -!- promag [~promag@195.54.168.134] has quit [Read error: Connection reset by peer] 10:38 -!- promag [~promag@195.54.168.134] has joined #bitcoin-core-dev 10:40 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 245 seconds] 10:40 -!- jonatack [58aba822@gateway/web/freenode/ip.88.171.168.34] has joined #bitcoin-core-dev 10:43 -!- promag [~promag@195.54.168.134] has quit [Ping timeout: 252 seconds] 10:45 -!- kexkey [~kexkey@68.168.122.228] has quit [Quit: Scaling pentatonically] 10:50 -!- noxx_ [~noxx@p57A6109A.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 10:51 -!- noxx__ [~noxx@p57A6109A.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 10:51 -!- timothy [~tredaelli@redhat/timothy] has quit [Remote host closed the connection] 10:57 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Quit: https://www.Quanto.ga/ -- Immutable state trading system in Clojure] 11:01 -!- lnostdal [~lnostdal@77.70.119.51] has joined #bitcoin-core-dev 11:11 -!- eo [~eo@2a02:810b:1040:28cc:d6de:7b47:7a78:f755] has joined #bitcoin-core-dev 11:11 -!- eo [~eo@2a02:810b:1040:28cc:d6de:7b47:7a78:f755] has quit [Remote host closed the connection] 11:13 -!- eo [~eo@2a02:810b:1040:28cc:d6de:7b47:7a78:f755] has joined #bitcoin-core-dev 11:14 -!- tferghrt [01c8cb48@gateway/web/freenode/ip.1.200.203.72] has quit [Quit: Page closed] 11:20 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 11:20 < bitcoin-git> [bitcoin] fametrano opened pull request #15550: [trivial] fixed path (master...patch-1) https://github.com/bitcoin/bitcoin/pull/15550 11:20 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 11:22 -!- eo [~eo@2a02:810b:1040:28cc:d6de:7b47:7a78:f755] has quit [Remote host closed the connection] 11:36 -!- Medea [4fd8b8ad@gateway/web/freenode/ip.79.216.184.173] has joined #bitcoin-core-dev 11:38 -!- bitjson [~bitjson@66.115.169.202] has joined #bitcoin-core-dev 11:47 -!- Medea [4fd8b8ad@gateway/web/freenode/ip.79.216.184.173] has quit [Ping timeout: 256 seconds] 11:50 -!- kexkey [~kexkey@68.168.122.228] has joined #bitcoin-core-dev 11:58 -!- mn949588 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has quit [Remote host closed the connection] 11:59 -!- mn949588 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has joined #bitcoin-core-dev 11:59 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 11:59 < cfields_> gitian builders: detached sigs for v0.18.0rc1 are up. 12:00 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev 12:09 -!- noxx__ [~noxx@p57A6109A.dip0.t-ipconnect.de] has quit [Ping timeout: 245 seconds] 12:09 -!- noxx_ [~noxx@p57A6109A.dip0.t-ipconnect.de] has quit [Ping timeout: 245 seconds] 12:14 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection] 12:15 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev 12:16 -!- kexkey [~kexkey@68.168.122.228] has quit [Read error: Connection reset by peer] 12:17 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 12:17 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 12:17 < bitcoin-git> [bitcoin] MarcoFalke pushed 5 commits to master: https://github.com/bitcoin/bitcoin/compare/4952a953585e...df36ddf9ce8a 12:17 < bitcoin-git> bitcoin/master fab2daa MarcoFalke: test: Add missing LIBBITCOIN_ZMQ to test_test_bitcoin_LDADD 12:17 < bitcoin-git> bitcoin/master fa02b22 MarcoFalke: test: Remove useless test_bitcoin_main.cpp 12:17 < bitcoin-git> bitcoin/master fa85468 MarcoFalke: test: Move main_tests to validation_tests 12:17 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 12:18 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 12:18 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #15504: fuzz: Link BasicTestingSetup (shared with unit tests) (master...1903-testMain) https://github.com/bitcoin/bitcoin/pull/15504 12:18 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 12:35 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has quit [Ping timeout: 258 seconds] 12:37 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has joined #bitcoin-core-dev 12:40 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 12:40 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev 12:40 -!- mmgen [~mmgen@gateway/tor-sasl/mmgen] has quit [Quit: (https://github.com/mmgen) leaving] 12:44 -!- Zenton [~user@unaffiliated/vicenteh] has joined #bitcoin-core-dev 12:56 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev 12:57 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 13:00 -!- kexkey [~kexkey@68.168.122.228] has joined #bitcoin-core-dev 13:10 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 13:10 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev 13:14 -!- elichai2 [uid212594@gateway/web/irccloud.com/x-scrrbfxilpuezfuz] has quit [Quit: Connection closed for inactivity] 13:16 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds] 13:25 -!- BobStone_ [5284e24f@gateway/web/freenode/ip.82.132.226.79] has joined #bitcoin-core-dev 13:35 -!- BobStone_ [5284e24f@gateway/web/freenode/ip.82.132.226.79] has quit [Quit: Page closed] 13:49 -!- promag [~promag@bl23-83-33.dsl.telepac.pt] has joined #bitcoin-core-dev 13:55 -!- OneFive_ [~OneFive@cpc87991-haye25-2-0-cust817.17-4.cable.virginm.net] has joined #bitcoin-core-dev 13:56 -!- OneFive__ [~OneFive@cpc87991-haye25-2-0-cust817.17-4.cable.virginm.net] has joined #bitcoin-core-dev 14:00 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 14:00 < bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/df36ddf9ce8a...3515612e069e 14:00 < bitcoin-git> bitcoin/master fa5dc35 MarcoFalke: rpc: Pass mempool into MempoolToJSON 14:00 < bitcoin-git> bitcoin/master fa38535 MarcoFalke: bench: Benchmark MempoolToJSON 14:00 < bitcoin-git> bitcoin/master 3515612 MarcoFalke: Merge #15473: bench: Benchmark MempoolToJSON 14:00 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 14:00 -!- OneFive_ [~OneFive@cpc87991-haye25-2-0-cust817.17-4.cable.virginm.net] has quit [Ping timeout: 255 seconds] 14:00 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 14:00 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #15473: bench: Benchmark MempoolToJSON (master...Mf1902-benchRpcMempool) https://github.com/bitcoin/bitcoin/pull/15473 14:01 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 14:02 -!- promag_ [~promag@bl23-83-33.dsl.telepac.pt] has joined #bitcoin-core-dev 14:06 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 14:07 -!- MTennis [~Tennis@unaffiliated/tennis] has joined #bitcoin-core-dev 14:08 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 14:10 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 14:10 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #15552: 0.18: Granular invalidateblock and RewindBlockIndex (0.18...201902_limitrewindinvalidate) https://github.com/bitcoin/bitcoin/pull/15552 14:10 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 14:31 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 15:03 -!- bitjson [~bitjson@66.115.169.202] has quit [Remote host closed the connection] 15:05 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 252 seconds] 15:05 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 15:06 < fanquake> cfields_ Thanks, I've pushed up some signed sigs 15:06 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev 15:07 -!- jarthur [~jarthur@207.114.244.5] has quit [] 15:08 < cfields_> fanquake: Thanks :) 15:17 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 15:17 -!- booyah [~bb@193.25.1.157] has quit [Ping timeout: 240 seconds] 15:22 -!- booyah [~bb@193.25.1.157] has joined #bitcoin-core-dev 15:29 -!- MTennis [~Tennis@unaffiliated/tennis] has quit [Quit: Leaving] 15:48 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [] 15:53 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Read error: Connection reset by peer] 15:53 -!- Zenton [~user@unaffiliated/vicenteh] has joined #bitcoin-core-dev 15:55 -!- OneFive__ [~OneFive@cpc87991-haye25-2-0-cust817.17-4.cable.virginm.net] has quit [Quit: Leaving] 16:22 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 16:29 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 16:29 < bitcoin-git> [bitcoin] fanquake closed pull request #15544: Comment typo "iff" (master...master) https://github.com/bitcoin/bitcoin/pull/15544 16:29 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 16:53 < wumpus> cfields_: thanks! 16:55 <@gwillen> does anybody with QT magic want to talk to me about the label used for alerts in overviewpage.ui 16:55 <@gwillen> I want something similar (a label that appears when I want to put text in it, and disappears otherwise) 16:56 <@gwillen> and I can't really figure out how you did it, and also when I try to edit the label in QT creator it gets ... glitchy, so I wonder if you edited the XML. 16:57 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has quit [Remote host closed the connection] 16:57 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has joined #bitcoin-core-dev 17:02 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has quit [Ping timeout: 245 seconds] 17:06 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [] 17:10 -!- zhangzf [~zhangzf@106.38.157.147] has joined #bitcoin-core-dev 17:18 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-core-dev 17:25 -!- makey40 [~jodie@24.215.123.241] has quit [Ping timeout: 255 seconds] 17:26 < promag_> gwillen: what's the purpose? 17:26 -!- makey40 [~jodie@24.215.123.241] has joined #bitcoin-core-dev 17:28 <@gwillen> hmm, maybe I should just use a modal instead 17:28 <@gwillen> I think I am being too web-influenced 17:29 <@gwillen> (this is for messages like "successfully signed" and "successfully broadcast" 17:30 < achow101> gwillen: wouldn't a dialog box work better for that? 17:34 <@gwillen> like I said, perhaps I am being too web-influenced 17:40 < promag_> agree :) 17:41 <@gwillen> I think the web-influenced version is _nicer_ 17:42 <@gwillen> but it's not really in keeping with the bitcoin-qt aesthetic 17:44 -!- echeveria [~echeveria@unaffiliated/echeveria] has quit [Ping timeout: 250 seconds] 17:48 -!- echeveria [~echeveria@unaffiliated/echeveria] has joined #bitcoin-core-dev 17:49 -!- promag [~promag@bl23-83-33.dsl.telepac.pt] has quit [Remote host closed the connection] 17:50 -!- promag_ [~promag@bl23-83-33.dsl.telepac.pt] has quit [Remote host closed the connection] 17:51 -!- alexalex [~imalex@67.129.13.34] has joined #bitcoin-core-dev 17:52 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 250 seconds] 18:01 -!- alexalex [~imalex@67.129.13.34] has quit [Quit: Leaving] 18:03 -!- pinheadmz [~matthewzi@96-82-67-198-static.hfc.comcastbusiness.net] has quit [Quit: pinheadmz] 18:19 -!- millerti [~millerti@cpe-66-24-91-119.stny.res.rr.com] has quit [Ping timeout: 255 seconds] 18:21 -!- promag [~promag@bl23-83-33.dsl.telepac.pt] has joined #bitcoin-core-dev 18:26 -!- promag [~promag@bl23-83-33.dsl.telepac.pt] has quit [Ping timeout: 240 seconds] 18:28 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 18:44 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 18:59 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 19:10 -!- fcc977 [6d759d65@gateway/web/freenode/ip.109.117.157.101] has joined #bitcoin-core-dev 19:13 -!- fcc977 [6d759d65@gateway/web/freenode/ip.109.117.157.101] has quit [Client Quit] 19:14 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz] 19:21 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 19:24 -!- mn9495881 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has joined #bitcoin-core-dev 19:24 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Remote host closed the connection] 19:25 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev 19:39 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz] 19:44 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 20:00 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz] 20:06 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 20:07 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev 20:26 -!- Netsplit *.net <-> *.split quits: nodweber2, molz, rockhouse, Sentineo, @gwillen, BGL, eenoch, sturles, da2ce7, bashco, (+2 more, use /NETSPLIT to show all of them) 20:28 -!- Netsplit over, joins: gwillen 20:29 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has quit [Ping timeout: 255 seconds] 20:31 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has joined #bitcoin-core-dev 20:32 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection] 20:36 -!- irc_viewer_test [irc_viewer@gateway/vpn/privateinternetaccess/ircviewertest/x-06412631] has joined #bitcoin-core-dev 20:41 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 20:44 -!- irc_viewer_test [irc_viewer@gateway/vpn/privateinternetaccess/ircviewertest/x-06412631] has quit [Quit: irc_viewer_test] 20:44 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds] 20:53 -!- promag [~promag@bl23-83-33.dsl.telepac.pt] has joined #bitcoin-core-dev 20:53 -!- Sentineo [~Undefined@unaffiliated/sentineo] has joined #bitcoin-core-dev 20:53 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 20:53 -!- rockhouse [~rockhouse@unaffiliated/rockhouse] has joined #bitcoin-core-dev 20:53 -!- bashco [~bashco@unaffiliated/bashco] has joined #bitcoin-core-dev 20:53 -!- jimpo [~jimpo@ec2-13-57-39-52.us-west-1.compute.amazonaws.com] has joined #bitcoin-core-dev 20:53 -!- nodweber2 [~nodweber@unaffiliated/nodweber] has joined #bitcoin-core-dev 20:53 -!- BGL [fifty@75-149-171-58-Washington.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 20:53 -!- molz [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 20:53 -!- eenoch [~eenoch@unaffiliated/eenoch] has joined #bitcoin-core-dev 20:53 -!- sturles [~sturles@unaffiliated/sturles] has joined #bitcoin-core-dev 20:53 -!- da2ce7 [~da2ce7@opentransactions/dev/da2ce7] has joined #bitcoin-core-dev 20:58 -!- promag [~promag@bl23-83-33.dsl.telepac.pt] has quit [Ping timeout: 250 seconds] 21:08 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz] 21:09 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 21:21 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 21:22 -!- rh0nj [~rh0nj@88.99.167.175] has joined #bitcoin-core-dev 21:30 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has quit [Remote host closed the connection] 21:30 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has joined #bitcoin-core-dev 21:42 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev 21:46 -!- promag [~promag@bl23-83-33.dsl.telepac.pt] has joined #bitcoin-core-dev 22:15 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz] 22:17 -!- nullptr| [~nullptr|@ip-94-112-134-45.net.upcbroadband.cz] has quit [Ping timeout: 244 seconds] 22:25 -!- nullptr| [~nullptr|@ip-94-112-134-45.net.upcbroadband.cz] has joined #bitcoin-core-dev 22:49 -!- spinza [~spin@155.93.246.187] has quit [Ping timeout: 246 seconds] 22:49 -!- promag [~promag@bl23-83-33.dsl.telepac.pt] has quit [Ping timeout: 245 seconds] 23:09 < luke-jr> ├─sshd(941)─┬─sshd(3366)───bash(3459)───apt-get(3464)───dpkg(6288)───linux-firmware.(9226)───update-initramf(9227)───update-initramf(17424)───m+ 23:09 < luke-jr> wumpus: ^ what is slowing the gitian system update for me 23:09 < gmaxwell> /join #bitcoin 23:23 -!- d_t [~d_t@108-65-77-11.lightspeed.sntcca.sbcglobal.net] has quit [Ping timeout: 252 seconds] 23:24 -!- mildly_risky [~~mildly_r@14-0-224-106.static.pccw-hkt.com] has joined #bitcoin-core-dev 23:25 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 23:27 -!- mildly_risky [~~mildly_r@14-0-224-106.static.pccw-hkt.com] has quit [Client Quit] 23:27 -!- mildly_risky [~~mildly_r@14-0-224-106.static.pccw-hkt.com] has joined #bitcoin-core-dev 23:32 -!- mildly_risky [~~mildly_r@14-0-224-106.static.pccw-hkt.com] has quit [Remote host closed the connection] 23:44 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [] --- Log closed Thu Mar 07 00:00:08 2019