--- Log opened Fri Aug 17 00:00:43 2018
00:29 < jonasschnelli> ken2812221, fanquake: you are using LXC, right? Docker uses LXC as well, right?
00:54 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev
01:05 -!- csknk [~csknk@unaffiliated/csknk] has joined #bitcoin-core-dev
01:36 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection]
01:37 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev
01:41 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
01:46 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds]
02:05 < ken2812221> jonasschnelli: yes, I'm using LXC
02:06 -!- promag [~promag@83.223.235.194] has joined #bitcoin-core-dev
02:08 < promag> should #13501 be tagged bugfix?
02:08 < gribble> https://github.com/bitcoin/bitcoin/issues/13501 | Correctly terminate HTTP server by promag · Pull Request #13501 · bitcoin/bitcoin · GitHub
02:18 -!- reallll [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
02:18 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev
02:39 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
02:43 < fanquake> yes, also LXC
03:44 -!- Krellan [~Krellan@2601:640:4000:9258:8d13:3cc8:d32c:a57c] has quit [Read error: Connection reset by peer]
03:44 -!- Krellan [~Krellan@2601:640:4000:9258:8d13:3cc8:d32c:a57c] has joined #bitcoin-core-dev
03:59 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]
03:59 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev
04:01 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
04:02 -!- Aaronva__ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
04:04 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds]
04:05 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds]
04:12 -!- Krellan [~Krellan@2601:640:4000:9258:8d13:3cc8:d32c:a57c] has quit [Ping timeout: 260 seconds]
04:14 -!- HoMM [~homm@unaffiliated/homm] has joined #bitcoin-core-dev
04:17 -!- Krellan [~Krellan@2601:640:4000:9258:8d13:3cc8:d32c:a57c] has joined #bitcoin-core-dev
04:21 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
04:23 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev
04:38 -!- prod_ [~prod@rrcs-67-251-193-154.nyc.biz.rr.com] has quit [Ping timeout: 256 seconds]
04:50 -!- itaseski [~itaseski@213.135.176.216] has joined #bitcoin-core-dev
05:00 -!- promag [~promag@83.223.235.194] has quit [Remote host closed the connection]
05:02 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
05:07 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection]
05:08 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev
05:09 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection]
05:10 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev
05:11 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection]
05:12 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev
05:18 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
05:18 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev
05:58 -!- brianhoffman [~brianhoff@pool-108-31-201-103.washdc.fios.verizon.net] has joined #bitcoin-core-dev
06:01 -!- brianhoffman_ [~brianhoff@185.94.31.80] has joined #bitcoin-core-dev
06:03 -!- brianhoffman [~brianhoff@pool-108-31-201-103.washdc.fios.verizon.net] has quit [Ping timeout: 244 seconds]
06:03 -!- brianhoffman_ is now known as brianhoffman
06:18 -!- rex4539 [~rex4539@2a02:587:3516:600:84d8:144d:6ace:febc] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:54 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 260 seconds]
06:56 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev
07:13 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds]
07:26 < wumpus> I'm also using LXC
07:30 -!- promag [~promag@83.223.249.206] has joined #bitcoin-core-dev
07:30 -!- michaelsdunn1 [~michaelsd@38.126.31.226] has joined #bitcoin-core-dev
07:31 -!- csknk [~csknk@unaffiliated/csknk] has quit [Quit: leaving]
07:38 < promag> wumpus: is there a way to compare case insensitive in the code?
07:40 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 260 seconds]
07:45 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev
07:47 < promag> ken2812221: would you mind testing #13501 in windows?
07:47 < gribble> https://github.com/bitcoin/bitcoin/issues/13501 | Correctly terminate HTTP server by promag · Pull Request #13501 · bitcoin/bitcoin · GitHubAsset 1Asset 1
07:48 < ken2812221> promag: Sure
07:48 < promag> thanks! I don't have access to one atm
07:50 < promag> wumpus: ^ no need to backport right?
07:51 < sipa> promag: convert both sides to lowercase and then compare? :)
07:52 < promag> sipa: yap, that's what I'm doing
07:52 < promag> sipa: I'll add an utility function
07:53 < promag> not sure if in util.h or utilstrencodings.h
07:53 < promag> suggestion?
07:53 < wumpus> promag: no, no need to backport, it's a very rare problem and not a regression -- would be great to solve it for 0.18
07:53 < promag> wumpus: agree
07:54 < ken2812221> promag: How about using regex?
07:54 < wumpus> promag: we'll need a locale-independent case conversion function, I guess
07:55 < wumpus> otherwise, this is going to do something different based on the user's language, which you don't want in http header handling
07:56 < promag> wumpus: like evutil_ascii_strcasecmp?
07:56 < wumpus> I guess you can use the libevent code, but only in code that already uses libevent directly
07:57 < wumpus> not in, say, utilstrencodings or util
07:58 < promag> maybe static bool HTTPRequest::CompareHeaders(a, b)?
07:59 < wumpus> promag: or make the headers function return the headers already lowercased
08:00 < promag> libevent doesn't expose that, and I'd like to dump what the client sends
08:00 < wumpus> ok, yes in that case a static function on HTTPRequest makes sense I suppose... I think it's somewhat hacky, implementing our own case-insensitive comparision function sounds super easy
08:02 < wumpus> now you convert from libevent string to std::string, then back to C string to pass it back for comparison...
08:02 < promag> wumpus: right, prefer that than own implementation
08:02 < wumpus> starting to think all of this isn't worth it just for some diagnostic logging
08:02 < wumpus> how many times do you really need to know the headers?
08:03 < wumpus> and you can't, say, start up wireshark or tcpdump
08:03 < wumpus> that has always worked great for me FWIW
08:05 < promag> sure, the idea is to have a out of the box way of seeing the requests
08:05 < promag> *headers
08:05 < wumpus> but why?
08:05 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev
08:05 < wumpus> what was your motivation for this?
08:05 < wumpus> from my own experience at least I'm usually interested inthe request contents, not the headers
08:06 < promag> in 13501, I was puzzled to know why bitcoin-cli worked differently than AuthProxy
08:07 -!- nullptr| [~nullptr|@ip-94-113-103-134.net.upcbroadband.cz] has quit [Ping timeout: 248 seconds]
08:07 < promag> anyway, I'll finish the implementation and then close it
08:07 < wumpus> well other people might reasonably disagree
08:08 < promag> what if we dump it only if `-debug` is on?
08:08 < wumpus> it's just that personally, I think this is a rabbit hole not venturing into
08:08 < wumpus> worth*
08:09 < wumpus> I add debug code like this all the time to diagnose specific issues, but never even consider upstreaming it, because it served its purpose
08:10 < wumpus> and making it production-friendly implies "censoring" sensitive headers and all that
08:10 < wumpus> which in turn brings in utiltiy functions we don't need right now for other things
08:13 < wumpus> and then the new string sanitization issues that this brings
08:13 < wumpus> I'm sorry
08:14 -!- nullptr| [~nullptr|@ip-94-113-103-134.net.upcbroadband.cz] has joined #bitcoin-core-dev
08:14 < promag> lol
08:15 < promag> don't be, I'll just finish and close it because I agree with you
08:17 < wumpus> thanks
08:21 -!- HoMM [~homm@unaffiliated/homm] has quit [Quit: sleep]
08:34 -!- Krellan [~Krellan@2601:640:4000:9258:8d13:3cc8:d32c:a57c] has quit [Read error: Connection reset by peer]
08:35 -!- Krellan [~Krellan@2601:640:4000:9258:8d13:3cc8:d32c:a57c] has joined #bitcoin-core-dev
08:43 -!- rex4539 [~rex4539@ppp-2-87-178-187.home.otenet.gr] has joined #bitcoin-core-dev
08:56 < cfields_> catching up. I understand there is/was an issue with determinism with the gitian build. Resolved, or is that still the case?
09:07 < cfields_> I see, it's the Linux build.  have
09:07 < cfields_> er
09:08 < cfields_> achow101 / jonasschnelli / ken2812221 / MarcoFalke / wumpus: can any of you share the gitian Linux output for comparison?
09:16 < cfields_> http://changelogs.ubuntu.com/changelogs/pool/main/g/glibc/glibc_2.27-3ubuntu1/changelog
09:18 < ken2812221> cfields: https://0bin.net/paste/Tae5ifPLYebHiKTi#uyXDywq91FOahuh+lc2E76cS9Qu-uINxkpxAHiL33BL
09:19 < ken2812221> This is lxc
09:19 < cfields_> ken2812221: thanks!
09:20 < cfields_> comparing now
09:21 < ken2812221> The difference is on bitcoin-qt, I've compared it before but I deleted the docker one.
09:21 -!- promag [~promag@83.223.249.206] has quit [Remote host closed the connection]
09:23 < cfields_> ah, ok
09:27 -!- csknk [~csknk@unaffiliated/csknk] has joined #bitcoin-core-dev
09:38 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit []
09:51 < MarcoFalke> Thanks for the lxc gitian results. Will also take a look here...
10:05 -!- jhfrontz [~Adium@cpe-184-57-118-36.columbus.res.rr.com] has quit [Quit: Leaving.]
10:18 -!- jhfrontz [~Adium@cpe-184-57-118-36.columbus.res.rr.com] has joined #bitcoin-core-dev
10:41 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
10:42 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev
10:47 < achow101> jonasschnelli: docker doesn't use lxc as the backend anymore
10:47 < wumpus> achow101: but it uses the same kind of kernel namespacing that lxc uses, doesn't it?
10:48 < wumpus> (maybe in a slightly different way)
10:49 < achow101> wumpus: I think so?
10:51 < wumpus> it's somewhat surprising for that to cause a difference in build result!
10:52 -!- Krellan [~Krellan@2601:640:4000:9258:8d13:3cc8:d32c:a57c] has quit [Ping timeout: 260 seconds]
10:52 < wumpus> bitcoin-qt only suggests to me it's another non-determinism thing with the qt tooling, maybe file ordering or date/time in metadata in the qrc archives
10:55 < MarcoFalke> I made it use --jobs 16, if that helps
10:56 < achow101> I thought the non-determinism was with all of them
10:56 < achow101> MarcoFalke: did you use docker?
10:56 < MarcoFalke> jup
10:56 < MarcoFalke> diffoscope spits out a trillion lines ...
10:57 -!- Krellan [~Krellan@2601:640:4000:9258:8d13:3cc8:d32c:a57c] has joined #bitcoin-core-dev
10:57 < achow101> oh, nvm, i see what you meant by bitcoin-qt being the non-deterministic one
10:59 < achow101> cfields_: here are my binaries https://github.com/achow101/bitcoin/releases/tag/v0.17.0rc1
11:00 -!- jtimon [~quassel@213.28.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev
11:01 < MarcoFalke> diffoscope: https://transfer.sh/8q9rT/diffoscope_51eb52972b_2_c7c606df_bitcoin-0.17.0-x86_64-linux-gnu.tar.gz.1
11:02 < MarcoFalke> only difference in qt
11:04 < gmaxwell> cmp the binaries and see if the difference is just a timestamp or something?
11:05 -!- jhfrontz [~Adium@cpe-184-57-118-36.columbus.res.rr.com] has quit [Quit: Leaving.]
11:06 < MarcoFalke> They have different sizes: 28286668 vs 28287142
11:08 < gmaxwell> pretty big difference in fact.
11:09 < wumpus> could still be a timestamp difference in compressed resource data
11:11 -!- vexbuy [~vexbuy@147.red-83-47-212.dynamicip.rima-tde.net] has joined #bitcoin-core-dev
11:11 -!- jeremyrubin [~jr@2601:645:4201:6086:6928:3a9a:99af:4891] has quit [Ping timeout: 265 seconds]
11:14 -!- jhfrontz [~Adium@cpe-184-57-118-36.columbus.res.rr.com] has joined #bitcoin-core-dev
11:16 < wumpus> gah for some reason I deleted the gitian output, need to rebuild before I can take a look
11:16 < gmaxwell> or a difference in file order
11:17 < jonasschnelli> gmaxwell: what do you think about the rekey not being a real rekey, I mean 'e' lives basically forever (until the connection dies). Would redoing the handshake (generate a new 'e') not make more sense?
11:17 < gmaxwell> No, it would just waste cpu time.
11:18 < gmaxwell> I'm not sure what 'e' refers to here, specifically. 
11:18 < jonasschnelli> ephemeral key 
11:19 < gmaxwell> The ephemeral key shouldn't even be remembered after the handshake is complete.
11:19 < gmaxwell> The hand shake computes an ephemeral key and outputs a session id, and encrypt and auth keys in each direction and forgets the ephemeral key.
11:20 < jonasschnelli> Yes. Right. Makes sense.
11:20 < gmaxwell> Rekey replaces the encrypt and auth keys with new ones derrived one way, so a host compromise can't go back and get old ones.
11:25 < gmaxwell> Rekey serves the purpose of limiting the amount of data that goes through the AEAD with a static key, since it's limited to 2^32 blocks by design, and as an additional benefit gets is some protection against being able to compromise a host in order to decrypt its past communications-- a kind of perfect forward secrecy which is relevant to us because we tend to have super long lived connections.
11:26 < jonasschnelli> ack
11:26 < jonasschnelli> Though 2^31 now with the rekey bit. :)
11:27 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection]
11:27 < jonasschnelli> ah. you meant the ChaChaPoly1305, nm then
11:27 < gmaxwell> right.
11:27 < gmaxwell> running the DH again wouldn't actually accompish anything but be slow, so we'd have to worry about DOS attacks from rekeying too often-- which basically cannot happen when rekey is just a cheap one way function.
11:28 < jonasschnelli> Sorry for brining other wild ideas in: what about using UDP (long term)?
11:28 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev
11:29 < sipa> that's a lot more complicated
11:29 < sipa> as our protocol is inherently ordered
11:30 -!- Emcy_ [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 240 seconds]
11:30 < gmaxwell> It's very difficult to use UDP as a general thing because you have to have _working_ nat traversal. it's easy to traverse 50% of nats, but to get to 99.999% is very hard. webrtc in firefox has hundreds of thousands of lines of code related to nat traversal.
11:30 < sipa> you'd need to invent your own message based protocol with retransmissions and ordering
11:30 < gmaxwell> And as sipa notes, you also have to implement your own TCP analog, complete with flow control and ordering.
11:30 < jonasschnelli> i see
11:31 < gmaxwell> it think it would be really neat for someone to implement a UDP protocol for bitcoin that just runs as a proxy in another process.
11:32 -!- Krellan [~Krellan@2601:640:4000:9258:8d13:3cc8:d32c:a57c] has quit [Ping timeout: 265 seconds]
11:32 < gmaxwell> it's also possible to do UDP for a narrow subset of use pretty easily.  E.g. block relay between hosts that do not require nat traversal (either no nat, or manually portmapped udp)--  fibre does that and it's relatively straight forward.
11:34 -!- Krellan [~Krellan@2601:640:4000:9258:8d13:3cc8:d32c:a57c] has joined #bitcoin-core-dev
11:36 < gmaxwell> Basically the things we know we can gain from using UDP:   (1) better low priority congestion control for low priority traffic, e.g. support peers IBDing without impacting the local network,  (2) avoiding head of line blocking e.g. a peer requesting a 100k transaction from us stops us from sending them a 10kb compact block until the 100k transaction is done. (3) avoiding retransmission head of l
11:36 < gmaxwell> ine blocking, where a single dropped packet delays communicating a block by at least one whole round trip. (4) better access to inbound peers due to nat hole punching.
11:36 -!- Krellan [~Krellan@2601:640:4000:9258:8d13:3cc8:d32c:a57c] has quit [Remote host closed the connection]
11:36 < gmaxwell> 2/3 are basically block transmission specific and don't apply to the rest of our protocol.
11:37 < gmaxwell> Which means they can be solved with a thing that only does blocks.
11:37 < gmaxwell> 4 is super hard because getting nat traversal working for the billion and one psycho devices out there is really complicated.
11:39 < gmaxwell> 1. is hard because it requires effectively a userspace TCP stack optimized for low priority.. all of it having a big network attack surface.
11:40 < gmaxwell> stuff like 1/4 don't need to be addressed from scratch, e.g. https://github.com/bittorrent/libutp 
11:43 < gmaxwell> in terms of effort&risk vs reward, it's kind of crazy that we haven't done a NAT-PMP/NAT-PCP implementation. 
11:44 -!- grafcaps [~haroldbr@104.137.194.255] has joined #bitcoin-core-dev
12:03 < jonasschnelli> The current signal-rekey-in-length bit has one problem, time based rekeys would need an artificial message,... or maybe it's okay to wait for the next ping
12:04 < jonasschnelli> Because the signal is for : "next message will use the new key"
12:05 < jonasschnelli> No message == no way to signal the bit
12:07 < gmaxwell> I think it's fine to just wait for the next message for bitcoin core, since we ping with a perfectly fine interval.
12:07 < gmaxwell> For some other kind of client that didn't ping as often, they could trigger a ping at the relevant time.
12:14 < jonasschnelli> petertodd: did you post to the ML or did someone impersonates you?
12:17 < MarcoFalke> jonasschnelli: The mail is missing the typical sig he puts on, so clearly fake unless proven otherwise
12:18 < jonasschnelli> yes. He posts sometimes without GPG, but never without his text sig
12:18 < gmaxwell> Who cares?
12:18 < jonasschnelli> Indeed,.. maybe kanzure (the mod)
12:18 < gmaxwell> yet another dumb offtopic post, out of many. :)
12:19 < jonasschnelli> I thought it's a moderated list?!
12:20 < gmaxwell> I believe regular posters are whitelisted to bypass the moderation.
12:20 < jonasschnelli> by smtp from:? hell please no. :)
12:22 < gmaxwell> seems like it!
12:25 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has quit [Read error: Connection reset by peer]
12:25 -!- aLK-[i] [sixty@75-149-171-58-Washington.hfc.comcastbusiness.net] has quit [Read error: Connection reset by peer]
12:25 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has joined #bitcoin-core-dev
12:30 -!- Aaronva__ [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
12:31 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
12:33 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Read error: Connection reset by peer]
12:33 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 240 seconds]
12:34 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Remote host closed the connection]
12:34 < MarcoFalke> The gitian issue is likely something with depends
12:34 < MarcoFalke> Anyone happen to have a gitian-builder/cache/* for lxc?
12:34 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev
12:34  * gmaxwell wonders if someday we're going to find a compromised dependency this way.
12:34 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev
12:35 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev
12:35 < MarcoFalke> gitian-builder/cache/bitcoin-linux-0.17/x86_64-linux-gnu/* I meant
12:35 -!- cfields [~quassel@unaffiliated/cfields] has joined #bitcoin-core-dev
12:37 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Read error: Connection reset by peer]
12:39 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev
12:40 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection]
12:45 -!- ken2812221_ [~androirc@2001-b400-e28f-9c9b-60f1-1b5a-b7fe-3f56.emome-ip6.hinet.net] has joined #bitcoin-core-dev
12:47 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev
12:53 -!- ken2812221_ [~androirc@2001-b400-e28f-9c9b-60f1-1b5a-b7fe-3f56.emome-ip6.hinet.net] has quit [Remote host closed the connection]
12:53 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 240 seconds]
12:56 -!- cfields [~quassel@unaffiliated/cfields] has quit [Remote host closed the connection]
12:57 -!- cfields [~quassel@unaffiliated/cfields] has joined #bitcoin-core-dev
12:59 -!- cfields [~quassel@unaffiliated/cfields] has quit [Remote host closed the connection]
12:59 -!- csknk [~csknk@unaffiliated/csknk] has quit [Quit: leaving]
13:01 -!- cfields [~quassel@unaffiliated/cfields] has joined #bitcoin-core-dev
13:01 -!- cfields [~quassel@unaffiliated/cfields] has quit [Remote host closed the connection]
13:02 < jonasschnelli> MarcoFalke: creating a tar.bz....
13:02 -!- cfields [~quassel@unaffiliated/cfields] has joined #bitcoin-core-dev
13:10 < MarcoFalke> jonasschnelli: thx
13:12 < jonasschnelli> MarcoFalke: https://bitcoin.jonasschnelli.ch/x86_64-linux-gnu.tar.bz
13:29 -!- vexbuy [~vexbuy@147.red-83-47-212.dynamicip.rima-tde.net] has quit []
13:32 < MarcoFalke> docker deps: https://transfer.sh/f6AG9/x86_64-linux-gnu.tar.xz
13:32 < MarcoFalke> diffoscope says it is qt
13:33 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 272 seconds]
13:33 < jonasschnelli> as always. :)
13:36 < MarcoFalke> https://transfer.sh/JN68e/qt_diffoscope
13:42 < MarcoFalke> .rodata.str1.1 has the size difference
13:43 < MarcoFalke> caused by "/usr/share/X11/xkb", it seems
13:44 -!- jhfrontz [~Adium@cpe-184-57-118-36.columbus.res.rr.com] has quit [Quit: Leaving.]
13:48 < cfields> MarcoFalke: thanks! is that the only difference?
13:48 < MarcoFalke> I think so
13:49 < MarcoFalke> The other changes seem due to the two rodata offsets
13:51 < cfields> hmm, I wonder if qt picked up a system xcb
13:52 -!- xHire [~xHire@kos.paskuli.cz] has quit [Ping timeout: 256 seconds]
13:54 < MarcoFalke> Are these are sting literals in translation units?
13:54 -!- BGL [ninety@75-149-171-58-Washington.hfc.comcastbusiness.net] has joined #bitcoin-core-dev
13:58 < cfields> MarcoFalke: I think I've got it, sec
13:59 < MarcoFalke> Ah it is in src/gui/configure.pri
14:01 < cfields> yea, it's a hard-coded thing that comes from configure
14:02 < cfields> MarcoFalke: are all arches non-deterministic?
14:02 < MarcoFalke> jup
14:03 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
14:03 < cfields> ok
14:04 -!- xHire [~xHire@kos.paskuli.cz] has joined #bitcoin-core-dev
14:04 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev
14:12 < cfields> MarcoFalke: you happen to have a build.log for one of your linux builds?
14:13 -!- treyzania [~treyzania@paphos.tr3y.io] has joined #bitcoin-core-dev
14:13 < kanzure> hmmmm wtf smtp from: is whitelisted?
14:13 < MarcoFalke> overwritten by my 0.16.2 build
14:13 < MarcoFalke> Maybe drahtbot has one
14:13 < kanzure> *what*?
14:15 < achow101> cfields: I have one
14:16 < MarcoFalke> cfields: Maybe https://drahtbot.space/gitian/bitcoin/bitcoin/885a45e323e900535ede2036b91a9118f12eb52b/bitcoin-linux-build.log
14:16 < MarcoFalke> for commit https://github.com/bitcoin/bitcoin/commit/885a45e323e900535ede2036b91a9118f12eb52b
14:16 < achow101> nvm, I don't
14:17 < cfields> MarcoFalke: yep! there's the problem! thanks.
14:17 < cfields> test config.gui.tests.xkbconfigroot gave result /usr/share/X11/xkb
14:17 < cfields> vs
14:17 < cfields> test config.gui.tests.xkbconfigroot gave result 
14:18 < cfields> qt's stupid check assumes a native build.
14:18 -!- xHire [~xHire@kos.paskuli.cz] has quit [Remote host closed the connection]
14:18 < MarcoFalke> Can we force the thing to an empty string?
14:20 < MarcoFalke> My suggested fix would be to remove the for loop in src/gui/configure.pri:47
14:20 < cfields> I think we want to hard-code it to the most likely strong. Otherwise I would assume it may affect keyboard layout/bindings
14:22 < MarcoFalke> Thoug, both of the dirs are missing on the docker?
14:22 < cfields> MarcoFalke: we should just be able to set "-xkb-config-root=/usr/share/X11/xkb"
14:23 < cfields> MarcoFalke: I assume some people have that dir due to other installed packages
14:23 < MarcoFalke> Ah, I didn't understand. Yeah, set it to the most likely one
14:25 < cfields> sec, let's see what this path is actually used for
14:30 < cfields> yea, keymap stuff. And it looks like the path is hit.
14:30 < cfields> We should just use whatever value the previous binaries have used.
14:31 < cfields> rebuilding 0.16 to see what it did.
14:32 < MarcoFalke> cfields: 0.16.2 linux-build.log on docker trusty: https://transfer.sh/b8srP/build.log
14:33 < cfields> MarcoFalke: thanks!
14:33 < cfields> QMAKE_XKB_CONFIG_ROOT = /usr/share/X11/xkb
14:36 -!- jhfrontz [~Adium@cpe-184-57-118-36.columbus.res.rr.com] has joined #bitcoin-core-dev
14:37 < cfields> MarcoFalke: PR incoming. I'm just doing a quick local build with a phony value to make sure that it gets inserted even if the path doesn't exist.
14:37 < MarcoFalke> ok
14:37 < MarcoFalke> will be offline for about 40 mins
14:47 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]
14:47 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
14:58 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev
15:00 -!- itaseski [~itaseski@213.135.176.216] has quit [Ping timeout: 268 seconds]
15:01 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
15:01 -!- rls [~rls@69.197.143.181] has joined #bitcoin-core-dev
15:03 < achow101> cfields: do you know why this wasn't a problem for earlier releases?
15:03 < achow101> I used the docker method for 0.16.2 and 0.16.1
15:03 < cfields> achow101: qt reworked their entire build-system for 5.8 iirc.
15:04 < cfields> I assume this is a regression
15:05 < cfields> https://bugreports.qt.io/browse/QTBUG-60005
15:06 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.1]
15:06 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
15:07 < cfields> yea, the -xkb-config-root switch is broken as well, we'll have to patch :(
15:12 -!- michaelsdunn1 [~michaelsd@38.126.31.226] has quit [Remote host closed the connection]
15:41 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:297a:85e5:a0ce:a2df] has joined #bitcoin-core-dev
15:45 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:297a:85e5:a0ce:a2df] has quit [Ping timeout: 255 seconds]
15:45 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev
15:52 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 260 seconds]
15:55 -!- murrayn [~dafuq@unaffiliated/murrayn] has quit [Read error: Connection reset by peer]
16:03 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:297a:85e5:a0ce:a2df] has joined #bitcoin-core-dev
16:04 < cfields> MarcoFalke: See #14000
16:04 < gribble> https://github.com/bitcoin/bitcoin/issues/14000 | depends: fix qt determinism by theuni · Pull Request #14000 · bitcoin/bitcoin · GitHub
16:26 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev
16:29 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #bitcoin-core-dev
16:36 -!- rls [~rls@69.197.143.181] has quit [Ping timeout: 240 seconds]
16:47 -!- harding [quassel@2600:3c03::f03c:91ff:fe7b:78d1] has quit [Ping timeout: 265 seconds]
17:13 -!- harrymm [~harrymm@69.161.195.103] has quit []
17:17 -!- harrymm [~harrymm@223.206.102.206] has joined #bitcoin-core-dev
17:20 -!- unholymachine [~quassel@2601:8c:c003:9f16:f9cb:95da:f0c0:8e79] has joined #bitcoin-core-dev
17:21 -!- harrymm [~harrymm@223.206.102.206] has quit [Ping timeout: 272 seconds]
17:30 -!- IGHOR [~quassel@93.178.216.72] has quit [Quit: http://quassel-irc.org ? ??????????? ?????????. ????-??.]
17:32 -!- IGHOR [~quassel@93.178.216.72] has joined #bitcoin-core-dev
17:33 -!- harrymm [~harrymm@69.161.195.103] has joined #bitcoin-core-dev
17:51 -!- unixb0y [~unixb0y@p2E55553B.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
17:51 < unixb0y> .
17:51 < unixb0y> HI guys, I have a little issue with the initial Bitcoin Core setup. 
17:52 < unixb0y> After around 7GB an error appeared, saying the wallet file is corrupted. 
17:52 < unixb0y> So I moved the file to a different location assuming it would just create a new file on the next startup and so it was. 
17:53 < unixb0y> Then of course it had to reindex and when it was almost finished, it made my computer crash. 
17:55 < unixb0y> Now I’ve “deleted” (renamed) all logfiles as well as  the last blk and rev files from the blocks folder as I’ve read that somewhere 
17:55 < unixb0y> Any advice is appreciated!
17:55 < gmaxwell> get a computer that doesn't corrupt data under load. :(
17:55 < gmaxwell> run memtest x86.
17:55 < unixb0y> I’m actually doing it on my main machine
17:56 < gmaxwell> Unfortunately, Bitcoin actually makes quite full use of the computer and so if its flaky at all it'll croak out.  deleting blk and rev files is never going to help anything.
17:56 < unixb0y> It looks like after renaming the logfiles it does *not* re index, instead it downloads it again 
17:56 < unixb0y> :/
17:57 < sipa> you need to start with -reindex to make it reindex
17:57 < unixb0y> Thanks for the info regarding the blk/rev files. 
17:57 < gmaxwell> if you were almost finished it should continue where it left off when you crashed, depending on how almost.
17:57 < sipa> it won't just see "hey there are files with blocks i'm not using"
17:57 < unixb0y> sipa: I run bitcoin-qt tbh :P
17:57 < sipa> irrelevant.
17:57 < unixb0y> How would I start it from the command line?
17:58 < sipa> bitcoin-qt -reindex
17:58 < unixb0y> Ok
17:58 < unixb0y> Thx 
17:58 < sipa> this discussion should probably move to #bitcoin
17:58 < unixb0y> Ok 
18:12 -!- unixb0y [~unixb0y@p2E55553B.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds]
18:48 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection]
18:49 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev
18:53 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:297a:85e5:a0ce:a2df] has quit [Ping timeout: 265 seconds]
19:01 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit []
19:11 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has quit [Remote host closed the connection]
19:15 -!- jarthur [~jarthur@2605:6000:1019:41ab:4136:562d:a324:188f] has joined #bitcoin-core-dev
19:44 -!- rls [~rls@69.197.143.181] has joined #bitcoin-core-dev
20:13 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Quit: Leaving]
20:35 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev
21:16 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 244 seconds]
21:19 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev
21:33 -!- jarthur [~jarthur@2605:6000:1019:41ab:4136:562d:a324:188f] has quit [Remote host closed the connection]
21:41 -!- xHire [~xHire@kos.paskuli.cz] has joined #bitcoin-core-dev
21:45 -!- jarthur [~jarthur@2605:6000:1019:41ab:4136:562d:a324:188f] has joined #bitcoin-core-dev
22:25 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 240 seconds]
22:38 -!- jarthur [~jarthur@2605:6000:1019:41ab:4136:562d:a324:188f] has quit []
23:12 -!- jtimon [~quassel@213.28.134.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds]
23:31 -!- orion333 [4752f60a@gateway/web/freenode/ip.71.82.246.10] has joined #bitcoin-core-dev
23:49 -!- harrymm [~harrymm@69.161.195.103] has quit [Ping timeout: 240 seconds]
--- Log closed Sat Aug 18 00:00:43 2018