--- Log opened Thu May 02 00:00:01 2019 00:17 < wumpus> no problem, which repo/tag is that? 00:20 < luke-jr> wumpus: will announce here when tagged, thanks ☺ (probably an hour or so) 00:23 -!- zakk [~zakk@184.75.223.195] has joined #bitcoin-core-dev 00:29 < luke-jr> hrm, Launchpad is timing out trying to get PPA download counts for Core - hopefully it will get fixed before Matt pushes 0.18 XD 00:46 -!- ccdle12 [~ccdle12@113x38x63x74.ap113.ftth.ucom.ne.jp] has joined #bitcoin-core-dev 00:46 -!- laptop_ [~laptop@host86-166-172-184.range86-166.btcentralplus.com] has joined #bitcoin-core-dev 00:51 -!- Randolf [~randolf@96.53.47.42] has quit [Remote host closed the connection] 00:51 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 00:53 -!- ccdle12 [~ccdle12@113x38x63x74.ap113.ftth.ucom.ne.jp] has quit [Ping timeout: 250 seconds] 01:00 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds] 01:00 -!- RandolfR [~randolf@96.53.47.38] has joined #bitcoin-core-dev 01:02 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 250 seconds] 01:13 -!- Guest42 [~textual@n11211983102.netvigator.com] has joined #bitcoin-core-dev 01:16 < luke-jr> hmm 01:16 < luke-jr> the big "Download Bitcoin Core" button on the website links ot the non-existent win32 :/ 01:17 -!- cepinheiro [~cepinheir@200-53-16-246.acessoline.net.br] has quit [Remote host closed the connection] 01:17 < luke-jr> wumpus: can you fix that quickly? otherwise it may skew our goal of finding out who cares 01:17 -!- cepinheiro [~cepinheir@200-53-16-246.acessoline.net.br] has joined #bitcoin-core-dev 01:17 < luke-jr> (ie, people may care that the default doesn't work, even if they don't necessarily care about win32 specifically) 01:18 < wumpus> I don't really know how to do website stuff 01:18 < wumpus> surprised anyone's default would be win32 though 01:18 < wumpus> ping @ harding 01:20 < luke-jr> probably just need to change win32exe to win64exe on line 21 01:20 < luke-jr> of _includes/templates/download.html 01:21 < wumpus> so this means *everyone* with windows was suggested the 32-bit download? ouch 01:21 < wumpus> will change 01:21 < gmaxwell> ugh 01:21 < luke-jr> wumpus: does it try to detect even? I got that link on Linux 01:22 < luke-jr> looks like it's a win32 link for everyone 01:22 < wumpus> it used to detect, maybe no more 01:23 < gmaxwell> maybe it correctly detects 64 bits on win64 but elsewhere just does 32bits? 01:23 < luke-jr> gmaxwell: i don't see any conditional logic 01:23 < luke-jr> bet it was lost with bitcoin.org -> bitcoincore.org 01:23 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev 01:24 < wumpus> https://github.com/bitcoin-core/bitcoincore.org/pull/650 01:24 < wumpus> luke-jr: oh good point, I guess the bitcoin.org PR will fail because it's missing the 32-bit windows files 01:28 < luke-jr> bitcoin.org indeed has OS detection Javascript 01:28 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has quit [Ping timeout: 258 seconds] 01:28 -!- promag_ [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 01:37 -!- jarthur [~jarthur@2605:6000:1019:41ab:c158:9a7c:c875:49f5] has quit [] 01:40 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has joined #bitcoin-core-dev 01:40 -!- promag_ [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 01:41 -!- promag_ [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 01:56 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 02:00 -!- zakk [~zakk@184.75.223.195] has quit [] 02:03 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 02:20 -!- miyamofigo_ [7ee9a9c2@gateway/web/freenode/ip.126.233.169.194] has joined #bitcoin-core-dev 02:21 < luke-jr> wumpus: nevermind, it'll be a while. something broke with the power64 gitian builds :/ 02:22 -!- miyamofigo_ [7ee9a9c2@gateway/web/freenode/ip.126.233.169.194] has quit [Client Quit] 02:41 < luke-jr> apparently a bug with Ubuntu's GCC 8 for older ppc64 02:41 * luke-jr ponders whether to bump up the ppc64 -mcpu, or drop to GCC 7 02:53 < wumpus> bumping the cpu sounds better, at least if it's still suppported on the TALOS 02:54 < luke-jr> yeah, it needs power7 for __float128, which glibcxx's headers assume is available 02:55 -!- promag_ [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 02:56 < gmaxwell> forcing down to older power probably hurts performance in any case, is anyone running this on anything less than power9? 02:57 < luke-jr> gmaxwell: awilfox was pushing for 970 (G5) 02:58 < luke-jr> gmaxwell: and ironically, it performs better on POWER9 with an older target, than if targetting power9 02:59 < wumpus> that's interesting 03:00 -!- jonatack [6d0d4c36@gateway/web/freenode/ip.109.13.76.54] has joined #bitcoin-core-dev 03:00 < wumpus> FWIW I'm surprised how good recent gcc's risc-v code generation is, it took ages to get to that level for ARM, for a long time it did kind of dumb things like juggle results between registers and memory unnecessarily 03:00 < luke-jr> it's -misel that makes the performance hit specifically 03:01 < gmaxwell> wumpus: might help that GCC is presumably the compiler the risc-v designers use, while arm was focused on their own toolchain for a long time 03:01 < wumpus> gmaxwell: yup 03:02 < gmaxwell> luke-jr: IIRC isel is some predicated execution thing? it might want branch profiling... 03:03 < wumpus> gcc is the only feasible toolchain for RISC-V at the moment, clang doesn't support everything yet for full linux rv64gc 03:06 < luke-jr> gmaxwell: well, supposedly POWER8 had it, but it performed worse, so GCC disabled it by default.. I imagine they'll end up doing the same for POWER9 03:07 < gmaxwell> Predication like features can result in big performance gains, but only when they're used on frequently executed low predictability branches, if you use it on a branch that always goes the right way on many that are rarely executed they hurt performance.... This was a super big deal on itanium. 03:08 < gmaxwell> without profiles GCC has some guesses, e.g. exceptions are rare... malloc failures seldom happen, etc. 03:10 < luke-jr> should we begin littering our code with likely()/unlikely()? :P 03:12 < wumpus> luke-jr: the performance critical parts, maybe yes, that'll also help for other platforms 03:12 -!- Guest11323 [~mengu@192.145.126.244] has joined #bitcoin-core-dev 03:12 < gmaxwell> Littering, probably not, but there might be a couple places where they make sense... but PGO is better from a maintance perspective! 03:12 < wumpus> although I've never seen those in c++ code, only c code 03:13 < luke-jr> PGO? 03:13 < gmaxwell> profile guided optimization. 03:13 < wumpus> e.g. MESA is littered with them (but that makes sense, almost everything in GPU drivers is perf critical that's the whole reason they exist) 03:13 < gmaxwell> I think for C++ you can't manage to likely tag all the important stuff... 03:14 < wumpus> the problem with PGO in our case might be reproducibility 03:14 < gmaxwell> luke-jr: -fprofile-generate and then run -fprofile-use. 03:14 < wumpus> yes, I also suspect it's more difficult due to more implicit behavior 03:14 < luke-jr> does PGO do cross anyway? 03:14 < gmaxwell> I believe mozilla has addressed PGO + reproducability. 03:15 < gmaxwell> but I'm not sure where that stands, in theory you should just be able to ship the profiles as side information along with the source. 03:15 < gmaxwell> in any case, might be worth benchmarking, if just to know even if its too much trouble to use. 03:16 < wumpus> right 03:16 < gmaxwell> If it gets a big speedup anywhere that might suggest likely() usage and/or refactoring to avoid confusing compiler hurestics. 03:17 < gmaxwell> (we do use builtin_expect in secp256k1, but mostly just around error handling code to get it to turn those into distant jumps) 03:19 -!- rockhouse [~rockhouse@unaffiliated/rockhouse] has quit [Ping timeout: 252 seconds] 03:20 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 03:20 -!- rockhouse [~rockhouse@unaffiliated/rockhouse] has joined #bitcoin-core-dev 03:25 -!- timothy [~tredaelli@redhat/timothy] has quit [Remote host closed the connection] 03:25 -!- promag_ [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 03:31 -!- Skirmant [~Skirmant@78-62-14-181.static.zebra.lt] has quit [Quit: (。-ω-) zzz..] 03:45 -!- b10c [~b10c@2001:16b8:2e00:4700:4f02:c9b2:c734:65df] has joined #bitcoin-core-dev 03:46 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 03:51 < harding> wumpus: did you get the win32/64 thing for the website sorted out? (Sorry; I thought I tested that for the removal.) 03:52 < luke-jr> harding: looks like it 03:53 < harding> luke-jr: cool. Thanks for noticing it was broken. 03:59 < gmaxwell> achow101: awake? time for a new bitcoin release thread on bitcointalk 04:07 -!- Guest42 [~textual@n11211983102.netvigator.com] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 04:13 < gmaxwell> achow101: you snooze you loose, https://bitcointalk.org/index.php?topic=5138532.0 04:14 < luke-jr> lol 04:17 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 04:18 < wumpus> harding: I think so, made a minimal change to fix the broken link, suggested by luke-jr 04:23 -!- Guest42 [~textual@n11211983102.netvigator.com] has joined #bitcoin-core-dev 04:24 -!- Guest42 [~textual@n11211983102.netvigator.com] has quit [Client Quit] 04:27 -!- Guest42 [~textual@n11211983102.netvigator.com] has joined #bitcoin-core-dev 04:29 < harding> wumpus: thanks! Sorry I missed that in the release PR. 04:30 < wumpus> no problem 04:31 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 04:32 -!- jonatack [6d0d4c36@gateway/web/freenode/ip.109.13.76.54] has quit [Ping timeout: 256 seconds] 04:33 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev 04:33 < Lauda> IsBerkeleyBtree: The system cannot find the file specified D:\Disk 1\Bitcoin\blocks\wallet.dat 04:33 < Lauda> is this intended in 18? 04:33 < Lauda> Seems to go through all folders looking for wallet.dat 04:34 < luke-jr> Lauda: that looks weird 04:34 < luke-jr> maybe trying to build the wallet list? 04:35 < Lauda> follow up is remaining folders 04:35 < Lauda> well it sounds weird 'find the file specified' 04:35 < Lauda> I didn't specify anything 04:41 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 04:48 < wumpus> bitcoin_test is really noisy on 0.18.0 RISC-V "Error: Specified -walletdir "/tmp/test_bitcoin/1556792182_943311758/tempdir/path_does_not_exist" does not exist" a zillion times, but the tests pass OK so I suppose these are expected errors 04:49 -!- jonatack [6d0d4c36@gateway/web/freenode/ip.109.13.76.54] has joined #bitcoin-core-dev 04:49 < luke-jr> also on x86_64 IIRC 04:50 < wumpus> on master x86_64 it prints three errors, which is better, but still not ideal 04:59 -!- promag_ [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 05:00 -!- Guest11323 [~mengu@192.145.126.244] has quit [] 05:00 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 05:03 -!- jtimon [~quassel@181.61.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 05:03 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Read error: Connection reset by peer] 05:03 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 05:09 -!- b10c [~b10c@2001:16b8:2e00:4700:4f02:c9b2:c734:65df] has quit [Ping timeout: 276 seconds] 05:09 -!- jonatack [6d0d4c36@gateway/web/freenode/ip.109.13.76.54] has quit [Ping timeout: 256 seconds] 05:21 -!- scoop [~scoop@205.178.77.52] has joined #bitcoin-core-dev 05:36 -!- b10c [~b10c@2001:16b8:2e00:4700:4f02:c9b2:c734:65df] has joined #bitcoin-core-dev 05:37 -!- b10c [~b10c@2001:16b8:2e00:4700:4f02:c9b2:c734:65df] has quit [Client Quit] 05:41 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 05:41 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #15939: gitian: Remove Windows 32 bit build (master...1904-GitianWin) https://github.com/bitcoin/bitcoin/pull/15939 05:41 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 05:42 -!- promag_ [~promag@a89-153-67-150.cpe.netcabo.pt] has joined #bitcoin-core-dev 05:45 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 05:45 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/0936f35f65ad...c4560a7dfee9 05:45 < bitcoin-git> bitcoin/master 5d35ae3 Luca Venturini: Handle the result of posix_fallocate system call 05:45 < bitcoin-git> bitcoin/master c4560a7 MarcoFalke: Merge #15650: Handle the result of posix_fallocate system call 05:45 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 05:46 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 05:46 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #15650: Handle the result of posix_fallocate system call (master...handle-posix-fallocate) https://github.com/bitcoin/bitcoin/pull/15650 05:46 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 05:50 -!- Y_Ichiro [~Y_Ichiro@165.84.231.15] has joined #bitcoin-core-dev 05:53 -!- wbnns [sid105317@21/bitcoin/binns] has joined #bitcoin-core-dev 06:04 -!- hashist [~hashist@157.157.113.191] has joined #bitcoin-core-dev 06:05 -!- hashist [~hashist@157.157.113.191] has left #bitcoin-core-dev [] 06:16 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 06:16 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/c4560a7dfee9...c1ba1182eb43 06:16 < bitcoin-git> bitcoin/master beb42d7 practicalswift: Silence GCC 7 warning "control reaches end of non-void function" (-Wreturn... 06:16 < bitcoin-git> bitcoin/master c1ba118 MarcoFalke: Merge #15938: refactor: Silence "control reaches end of non-void function"... 06:16 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 06:16 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 06:16 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #15938: refactor: Silence "control reaches end of non-void function" (-Wreturn-type) in psbt.cpp (master...psbt-return-type-warning) https://github.com/bitcoin/bitcoin/pull/15938 06:16 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 06:17 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 06:23 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #bitcoin-core-dev 06:26 -!- promag_ [~promag@a89-153-67-150.cpe.netcabo.pt] has quit [Remote host closed the connection] 06:35 -!- sdaftuar [~sdaftuar@gateway/tor-sasl/sdaftuar] has quit [Ping timeout: 256 seconds] 06:36 -!- alex___ [5d51bda4@gateway/web/freenode/ip.93.81.189.164] has joined #bitcoin-core-dev 06:37 -!- sdaftuar [~sdaftuar@gateway/tor-sasl/sdaftuar] has joined #bitcoin-core-dev 06:37 -!- alex___ [5d51bda4@gateway/web/freenode/ip.93.81.189.164] has quit [Client Quit] 06:38 -!- ccdle12 [~ccdle12@113x38x63x74.ap113.ftth.ucom.ne.jp] has joined #bitcoin-core-dev 06:39 -!- ossifrage_ [~ossifrage@unaffiliated/ossifrage] has joined #bitcoin-core-dev 06:41 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has quit [Ping timeout: 268 seconds] 06:50 -!- ossifrage_ [~ossifrage@unaffiliated/ossifrage] has quit [Ping timeout: 245 seconds] 06:50 -!- ossifrage_ [~ossifrage@unaffiliated/ossifrage] has joined #bitcoin-core-dev 07:02 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds] 07:02 -!- scoop [~scoop@205.178.77.52] has quit [Remote host closed the connection] 07:08 -!- baldur [~baldur@pool-72-69-148-126.nycmny.fios.verizon.net] has quit [Ping timeout: 246 seconds] 07:11 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 07:11 < bitcoin-git> [bitcoin] laanwj opened pull request #15941: doc: Add historical release notes for 0.18.0 (master...2019_05_historical_release_notes) https://github.com/bitcoin/bitcoin/pull/15941 07:11 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 07:14 -!- Guest42 [~textual@n11211983102.netvigator.com] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 07:15 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 07:15 < bitcoin-git> [bitcoin] laanwj pushed 1 commit to 0.18: https://github.com/bitcoin/bitcoin/compare/2472733a24a9...be92be5644a7 07:15 < bitcoin-git> bitcoin/0.18 be92be5 Wladimir J. van der Laan: doc: Clean out release notes post-0.18.0 07:15 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 07:16 -!- Guest42 [~textual@n11211983102.netvigator.com] has joined #bitcoin-core-dev 07:18 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 258 seconds] 07:19 < achow101> gmaxwell: 7 am is too early for me 07:20 -!- scoop [~scoop@50-77-133-26-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 07:21 -!- baldur [~baldur@pool-72-69-148-126.nycmny.fios.verizon.net] has joined #bitcoin-core-dev 07:23 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 07:24 -!- scoop [~scoop@50-77-133-26-static.hfc.comcastbusiness.net] has quit [Ping timeout: 246 seconds] 07:24 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 07:24 < bitcoin-git> [bitcoin] laanwj pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/c1ba1182eb43...24dfcf3a56f9 07:24 < bitcoin-git> bitcoin/master da9f1ac Wladimir J. van der Laan: doc: Add historical release notes for 0.18.0 07:24 < bitcoin-git> bitcoin/master 24dfcf3 Wladimir J. van der Laan: Merge #15941: doc: Add historical release notes for 0.18.0 07:24 -!- Tralfaz [~none@178.128.106.205] has joined #bitcoin-core-dev 07:25 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 07:25 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev 07:25 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 07:25 < bitcoin-git> [bitcoin] laanwj merged pull request #15941: doc: Add historical release notes for 0.18.0 (master...2019_05_historical_release_notes) https://github.com/bitcoin/bitcoin/pull/15941 07:25 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 07:26 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 07:27 -!- davterra [~none@94.100.23.163] has quit [Ping timeout: 246 seconds] 07:30 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 258 seconds] 07:31 -!- davterra [~none@94.100.23.163] has joined #bitcoin-core-dev 07:32 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 246 seconds] 07:33 -!- Tralfaz [~none@178.128.106.205] has quit [Ping timeout: 252 seconds] 07:40 -!- ossifrage_ [~ossifrage@unaffiliated/ossifrage] has quit [Ping timeout: 245 seconds] 07:41 -!- ossifrage_ [~ossifrage@unaffiliated/ossifrage] has joined #bitcoin-core-dev 08:00 -!- Y_Ichiro [~Y_Ichiro@165.84.231.15] has quit [] 08:02 -!- jimmysong [~jimmysong@65-36-83-142.static.grandenetworks.net] has quit [Read error: Connection reset by peer] 08:04 -!- furkanmustafa [~furkanmus@185.5.172.147] has joined #bitcoin-core-dev 08:09 -!- WarrenBuffet [~ident@c-71-238-229-151.hsd1.ar.comcast.net] has joined #bitcoin-core-dev 08:09 < hebasto> wumpus: #15940 "for 0.18.0" - typo? 08:09 < gribble> https://github.com/bitcoin/bitcoin/issues/15940 | Release schedule for 0.19.0 · Issue #15940 · bitcoin/bitcoin · GitHub 08:11 -!- Guest42 [~textual@n11211983102.netvigator.com] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 08:14 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Remote host closed the connection] 08:21 -!- shivendra [~shivendra@175.100.148.77] has joined #bitcoin-core-dev 08:25 < wumpus> hebasto: yes, thanks, updated 08:26 -!- _Sam-- [~greybits@unaffiliated/greybits] has joined #bitcoin-core-dev 08:29 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev 08:30 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds] 08:32 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-core-dev 08:35 -!- ccdle12 [~ccdle12@113x38x63x74.ap113.ftth.ucom.ne.jp] has quit [Remote host closed the connection] 08:38 -!- scoop [~scoop@ip-174-152-170-33.chcgil.spcsdns.net] has joined #bitcoin-core-dev 08:41 -!- jimmysong [~jimmysong@65-36-83-142.static.grandenetworks.net] has joined #bitcoin-core-dev 08:44 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev 08:50 -!- setpill [~setpill@unaffiliated/setpill] has quit [Quit: o/] 09:11 -!- ossifrage_ [~ossifrage@unaffiliated/ossifrage] has quit [Ping timeout: 252 seconds] 09:12 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 246 seconds] 09:20 -!- cepinheiro [~cepinheir@200-53-16-246.acessoline.net.br] has quit [Remote host closed the connection] 09:26 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has joined #bitcoin-core-dev 09:28 -!- shivendra [~shivendra@175.100.148.77] has quit [Ping timeout: 250 seconds] 09:28 -!- scoop [~scoop@ip-174-152-170-33.chcgil.spcsdns.net] has quit [Remote host closed the connection] 09:36 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection] 09:42 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has quit [Quit: bbl] 09:56 -!- afk11 [~afk11@unaffiliated/afk11] has quit [Ping timeout: 258 seconds] 10:18 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 10:18 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #15942: tests: Use BOOST_CHECK_EQUAL for verbose prints on fail (master...1905-testCryptoEqual) https://github.com/bitcoin/bitcoin/pull/15942 10:18 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 10:34 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Ping timeout: 256 seconds] 10:35 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-core-dev 10:47 < luke-jr> apparently GCC 8.2 is broken on PPC in other ways too so just reverting to GCC 7 10:47 < luke-jr> (has anyone checked that 8.2 isn't broken on other platforms we support?) 10:48 < luke-jr> wumpus: ^ 10:53 < wumpus> no problems with it for risc-v nor x86 10:59 -!- timothy [~tredaelli@redhat/timothy] has quit [Ping timeout: 255 seconds] 11:00 -!- furkanmustafa [~furkanmus@185.5.172.147] has quit [] 11:01 -!- nullptr| [~nullptr|@ip-94-112-134-45.net.upcbroadband.cz] has quit [Ping timeout: 245 seconds] 11:05 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 11:07 -!- nullptr| [~nullptr|@ip-94-112-134-45.net.upcbroadband.cz] has joined #bitcoin-core-dev 11:08 -!- Victorsueca is now known as Tipper 11:08 -!- Tipper is now known as Victorsueca 11:22 -!- perrito6661 [~perrito66@165.84.231.15] has joined #bitcoin-core-dev 11:28 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev 11:33 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds] 11:51 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 11:51 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #15942: tests: Use BOOST_CHECK_EQUAL for verbose prints on fail (master...1905-testCryptoEqual) https://github.com/bitcoin/bitcoin/pull/15942 11:51 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 12:01 < wumpus> #startmeeting 12:01 < lightningbot> Meeting started Thu May 2 19:01:08 2019 UTC. The chair is wumpus. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:01 < lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic. 12:01 < sipa> hi 12:01 < luke-jr> hi 12:01 < kanzure> hi 12:01 < jnewbery> hi 12:01 < wumpus> #bitcoin-core-dev Meeting: wumpus sipa gmaxwell jonasschnelli morcos luke-jr sdaftuar jtimon cfields petertodd kanzure bluematt instagibbs phantomcircuit codeshark michagogo marcofalke paveljanik NicolasDorier jl2012 achow101 meshcollider jnewbery maaku fanquake promag provoostenator aj Chris_Stewart_5 dongcarl gwillen jamesob ken281221 ryanofsky gleb moneyball 12:02 < sdaftuar> hi 12:02 < achow101> hi 12:02 < wumpus> congrats on release 0.18.0 everyone ! 12:02 < sipa> indeed! 12:02 < jamesob> hi 12:02 < jonasschnelli> hi 12:02 < sdaftuar> \o/ 12:03 < jtimon> still not sure what I did for this release exactly...but thanks, I guess :) 12:03 < wumpus> I've created an issue with the release schedule for 0.19: #15940 12:03 < gribble> https://github.com/bitcoin/bitcoin/issues/15940 | Release schedule for 0.19.0 · Issue #15940 · bitcoin/bitcoin · GitHub 12:04 < wumpus> any proposed topics? nothing on moneyball's list this week 12:05 < instagibbs> \o/ 12:05 < wumpus> #topic high priority for review 12:05 < sipa> i've been busy with some other things, i'll be more active soon 12:05 < phantomcircuit> hi 12:06 < wumpus> currently on the list: #15427 #15024 #15006 #15141 #15512 12:06 < gribble> https://github.com/bitcoin/bitcoin/issues/15427 | Add support for descriptors to utxoupdatepsbt by sipa · Pull Request #15427 · bitcoin/bitcoin · GitHub 12:06 < gribble> https://github.com/bitcoin/bitcoin/issues/15024 | Allow specific private keys to be derived from descriptor by meshcollider · Pull Request #15024 · bitcoin/bitcoin · GitHub 12:06 < gribble> https://github.com/bitcoin/bitcoin/issues/15006 | Add option to create an encrypted wallet by achow101 · Pull Request #15006 · bitcoin/bitcoin · GitHub 12:06 < wumpus> sipa: good to know! 12:06 < gribble> https://github.com/bitcoin/bitcoin/issues/15512 | Add ChaCha20 encryption option (XOR) by jonasschnelli · Pull Request #15512 · bitcoin/bitcoin · GitHub 12:06 < gribble> https://github.com/bitcoin/bitcoin/issues/15141 | Rewrite DoS interface between validation and net_processing by sdaftuar · Pull Request #15141 · bitcoin/bitcoin · GitHub 12:06 < wumpus> anything to add/remove? 12:07 < jonasschnelli> If you want progress on the p2p encryption, review the ChaCha20 stuff in #15512 () 12:07 < gribble> https://github.com/bitcoin/bitcoin/issues/15512 | Add ChaCha20 encryption option (XOR) by jonasschnelli · Pull Request #15512 · bitcoin/bitcoin · GitHub 12:07 < wumpus> right! 12:07 -!- promag_ [~promag@bl16-114-47.dsl.telepac.pt] has joined #bitcoin-core-dev 12:07 < sipa> jonasschnelli: will do, promise 12:07 < jonasschnelli> thanks 12:07 < jamesob> psa: going to be putting up the first of the assumeutxo-related PRs in the next few days; if you're interested and haven't reviewed the general proposal you can do so here: https://github.com/jamesob/assumeutxo-docs/pull/1 12:08 < wumpus> jamesob: yes, some context is always useful 12:10 < wumpus> any other topics? (or, more to discuss about assumeutxo) 12:10 < jamesob> not on my end, though happy to chat about assumeutxo if anyone has questions 12:11 -!- joe___ [d826964a@gateway/web/freenode/ip.216.38.150.74] has joined #bitcoin-core-dev 12:12 < wumpus> okay 12:13 < wumpus> a short meeting then, I guess 12:13 < jonasschnelli> new record 12:13 < jnewbery> short meetings are good meetings 12:13 < wumpus> very efficient 12:14 < wumpus> #endmeeting 12:14 < lightningbot> Meeting ended Thu May 2 19:14:00 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 12:14 < lightningbot> Minutes: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2019/bitcoin-core-dev.2019-05-02-19.01.html 12:14 < lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/bitcoin-core-dev/2019/bitcoin-core-dev.2019-05-02-19.01.txt 12:14 < lightningbot> Log: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2019/bitcoin-core-dev.2019-05-02-19.01.log.html 12:15 < MarcoFalke> Oh, I missed it 12:15 < sipa> MarcoFalke: you didn't miss much :p 12:15 < MarcoFalke> heh 12:15 < luke-jr> we need to have another meeting for MarcoFalke 12:16 < MarcoFalke> can I add #15870? 12:16 < gribble> https://github.com/bitcoin/bitcoin/issues/15870 | wallet: Only fail rescan when blocks have actually been pruned by MarcoFalke · Pull Request #15870 · bitcoin/bitcoin · GitHub 12:16 < MarcoFalke> to high priority? 12:20 < wumpus> MarcoFalke :sure 12:20 < MarcoFalke> cool thx 12:20 * MarcoFalke #end meeting for MarcoFalke 12:30 -!- promag_ [~promag@bl16-114-47.dsl.telepac.pt] has quit [Remote host closed the connection] 12:32 -!- promag_ [~promag@bl16-114-47.dsl.telepac.pt] has joined #bitcoin-core-dev 12:34 -!- promag_ [~promag@bl16-114-47.dsl.telepac.pt] has quit [Remote host closed the connection] 12:36 -!- promag_ [~promag@bl16-114-47.dsl.telepac.pt] has joined #bitcoin-core-dev 12:39 < jtimon> jamesob: reading the proposal, looks very nice 12:39 < jamesob> jtimon: cool, thanks! 12:41 -!- promag_ [~promag@bl16-114-47.dsl.telepac.pt] has quit [Remote host closed the connection] 12:42 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 244 seconds] 12:43 -!- joe___ [d826964a@gateway/web/freenode/ip.216.38.150.74] has quit [Ping timeout: 256 seconds] 12:43 -!- promag_ [~promag@bl16-114-47.dsl.telepac.pt] has joined #bitcoin-core-dev 12:47 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 13:03 -!- stephan3000 [55c3eb12@gateway/web/freenode/ip.85.195.235.18] has joined #bitcoin-core-dev 13:08 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 13:09 < phantomcircuit> sipa, the CAddrMan Unserialize method trusts that the nSize parameter isn't corrupted, is there an upper bound for that we could set to prevent an infinite loop on disk corruption? 13:11 < sipa> phantomcircuit: the total number of entries is capped by the number and size of the buckets, so yes 13:11 < sipa> though we may want to set the limit a small factor higher to permit downgrading if the bucket layout ever changes 13:12 < phantomcircuit> sipa, line 423 in addrman.h , so it's the "new" table 13:12 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-core-dev 13:12 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Read error: Connection reset by peer] 13:13 -!- promag_ [~promag@bl16-114-47.dsl.telepac.pt] has quit [Remote host closed the connection] 13:13 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-core-dev 13:16 -!- user2019 [55c3eb12@gateway/web/freenode/ip.85.195.235.18] has joined #bitcoin-core-dev 13:16 -!- davterra [~none@94.100.23.163] has quit [Ping timeout: 245 seconds] 13:19 -!- stephan3000 [55c3eb12@gateway/web/freenode/ip.85.195.235.18] has quit [Ping timeout: 256 seconds] 13:27 -!- promag_ [~promag@bl16-114-47.dsl.telepac.pt] has joined #bitcoin-core-dev 13:32 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 13:32 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #15943: tests: Fail if RPC has been added without tests (master...1905-testFailNoRpcCov) https://github.com/bitcoin/bitcoin/pull/15943 13:32 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 13:33 < phantomcircuit> sipa, i guess it mostly doesn't matter cause the stream will probably fault before it loops for too long 13:35 < sipa> phantomcircuit: i think there are at most 64*1024 entries in the 'new' table 13:35 < sipa> #define ADDRMAN_NEW_BUCKET_COUNT_LOG2 10 13:35 < sipa> #define ADDRMAN_BUCKET_SIZE_LOG2 6 13:54 < sipa> MarcoFalke: that sha256d64 test failing is scary 14:00 -!- perrito6661 [~perrito66@165.84.231.15] has quit [] 14:00 < phantomcircuit> sipa, thinking about it more i dont think it really matters cause the stream reads will just throw an exception once it's past the end of the file 14:00 < sipa> yes 14:01 < sipa> phantomcircuit: i guess the only thing to worry about is if a garbage file can cause us to allocate a ginormous amount of memory immediately 14:01 < sipa> but the normal vector serialization functions allocate incrementally to prevent that 14:01 < sipa> *deserialization 14:02 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 14:03 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-core-dev 14:03 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Read error: Connection reset by peer] 14:04 -!- davec [~davec@cpe-24-243-249-218.hot.res.rr.com] has quit [Ping timeout: 258 seconds] 14:04 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection] 14:05 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-core-dev 14:08 -!- mryandao_ [~mryandao@gateway/tor-sasl/mryandao] has joined #bitcoin-core-dev 14:09 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has quit [Ping timeout: 256 seconds] 14:10 -!- brantje [~brantje@165.84.231.15] has joined #bitcoin-core-dev 14:12 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 250 seconds] 14:12 -!- reardencode [~reardenco@shrugged.reardencode.com] has quit [Ping timeout: 250 seconds] 14:15 < phantomcircuit> sipa, and this is just reading integers so it cant be more than 32bits at a time 14:22 < MarcoFalke> yeah, indeed scary 14:22 < MarcoFalke> So bitcoind is using a different sha than the tests do? 14:23 < MarcoFalke> Otherwise, how could it sync 14:25 < sipa> MarcoFalke: how many times do you get the "check memcmp(...) == 0 has failed" ? 14:25 < MarcoFalke> 32 14:26 < sipa> what happens if you add a SHA256AutoDetect() call in the test? 14:28 < MarcoFalke> Same 14:28 < MarcoFalke> I guess it is already called in BasicTestingSetup() 14:29 < sipa> ok, what if you comment out the "if (have_avx2 && have_avx && enabled_avx) {" block in crpyto/sha256.cpp ? 14:32 < MarcoFalke> Same with if (true||have_avx2 && have_avx && enabled_avx) { 14:33 -!- davec [~davec@cpe-24-243-249-218.hot.res.rr.com] has joined #bitcoin-core-dev 14:33 < sipa> what if you disable it entirely (as in: don't use avx2) 14:33 < MarcoFalke> still fails 14:34 < sipa> what if you comment out the "TransformD64_4way = sha256d64_sse41::Transform_4way" line and the "TransformD64_8way = sha256d64_avx2::Transform_8way;" line? 14:34 * sipa is baffled 14:35 < MarcoFalke> same 14:35 * MarcoFalke yes I double checked that I compiled it again 14:37 < MarcoFalke> 2019-05-02T21:37:33Z Using the 'standard' SHA256 implementation 14:38 < sipa> sense, it makes none. 14:38 < luke-jr> NSA disagrees 14:38 < sipa> can you add an assert inside the avx2/sse4 implementations to make sure they're not invoked? 14:40 -!- michaelfolkson [~textual@85.211.233.88] has joined #bitcoin-core-dev 14:41 -!- promag_ [~promag@bl16-114-47.dsl.telepac.pt] has quit [Remote host closed the connection] 14:44 < MarcoFalke> I think it calls TransformD64 14:45 < MarcoFalke> and Transform 14:46 < MarcoFalke> sha256_sse4::Transform and Transform_8way have an assert(false) 14:48 < sipa> what if you set TransformD64 to TransformD64Wrapper (and make SHA256AutoDetect a no-op)? 14:49 < sipa> in the initializer 14:51 -!- reardencode [~reardenco@shrugged.reardencode.com] has joined #bitcoin-core-dev 14:53 < MarcoFalke> still fails 15:01 < luke-jr> MarcoFalke: what GCC version? 15:01 < MarcoFalke> $ gcc --version === gcc (GCC) 9.0.1 20190312 (Red Hat 9.0.1-0.10) 15:05 < luke-jr> hrm, I'd guess probably not the issue, but it might indicate GCC has been playing with memory stuff? https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88273 15:06 < luke-jr> might be worth recompiling with GCC 7 just to see if it's compiler-dependent 15:07 < MarcoFalke> Someone else reported it with fedora 29, which has gcc8? 15:07 < MarcoFalke> But I will try with clang 15:07 < MarcoFalke> Might take a while since 32 bit only gives me 2gb of ram 15:07 < sipa> MarcoFalke: does compiling with ubsan or asan give any interesting results 15:07 < sipa> ? 15:08 < MarcoFalke> rip ram 15:08 < MarcoFalke> will have results in an hour earliest 15:08 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 15:09 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-core-dev 15:09 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Read error: Connection reset by peer] 15:10 -!- sdaftuar [~sdaftuar@gateway/tor-sasl/sdaftuar] has quit [Ping timeout: 256 seconds] 15:10 < luke-jr> MarcoFalke: since this is a not-very-likely cause, I'd suggest continuing to troubleshoot with sipa while it builds 15:10 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-core-dev 15:10 < luke-jr> although I guess rebuilding with sanitizers are going to take just as long :x 15:10 < luke-jr> I would be surprised if asan supported x86_32 since it requires so much virtual memory space 15:10 -!- sdaftuar [~sdaftuar@gateway/tor-sasl/sdaftuar] has joined #bitcoin-core-dev 15:10 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Read error: Connection reset by peer] 15:11 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #bitcoin-core-dev 15:13 < MarcoFalke> So just to confirm this should be the call stack? 15:13 < MarcoFalke> https://pastebin.ubuntu.com/p/tSVxBJvTZy/ 15:14 < MarcoFalke> SHA256D64 calls Transform? 15:14 < sipa> yeah, that looks right 15:14 < sipa> it calls TransformD64, which is a function pointer to a wrapper function that invokes Transform 15:19 < MarcoFalke> ok, building on clang with sanitizers = address,undefined 15:22 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 15:23 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 15:25 -!- RandolfR [~randolf@96.53.47.38] has quit [Ping timeout: 268 seconds] 15:25 -!- user2019 [55c3eb12@gateway/web/freenode/ip.85.195.235.18] has quit [Ping timeout: 256 seconds] 15:32 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 15:35 -!- laptop_ [~laptop@host86-166-172-184.range86-166.btcentralplus.com] has quit [Ping timeout: 246 seconds] 15:42 -!- Guest42 [~textual@n11211983102.netvigator.com] has joined #bitcoin-core-dev 15:44 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 245 seconds] 15:58 < phantomcircuit> so apparently GetTimeMillis() can throw an exception, which isn't handled like anywhere 15:58 < sipa> phantomcircuit: define 'can' 15:58 < phantomcircuit> actually it can't nvm 15:58 < phantomcircuit> sorry 15:58 < phantomcircuit> boost::gregorian::date can but not with the constants we use 15:59 < MarcoFalke> So it passes with clang and address sanitizer 15:59 < MarcoFalke> !? 15:59 < gribble> (misc help [] []) -- This command gives a useful description of what does. is only necessary if the command is in more than one plugin. 15:59 < sipa> MarcoFalke: gcc 9 bug? 15:59 * MarcoFalke off 15:59 < MarcoFalke> Maybe. 15:59 < MarcoFalke> Could also be 8 16:00 < MarcoFalke> Will update the issue tomorrow 16:00 < luke-jr> hopefully not 8, as we just shipped built with 8 :x 16:00 < MarcoFalke> luke-jr: The issue is there since 0.17.1 16:00 < MarcoFalke> So yes, likely also gcc 8 16:01 < luke-jr> :| 16:02 -!- scoop [~scoop@static-108-30-224-244.nycmny.fios.verizon.net] has joined #bitcoin-core-dev 16:04 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 252 seconds] 16:05 < booyah> on limited memory maybe just run in valgrind, if you have memory problems? (though always few false positives) 16:19 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 16:19 -!- Skirmant [~Skirmant@78-62-14-181.static.zebra.lt] has joined #bitcoin-core-dev 16:20 < sipa> MarcoFalke: i can reproduce 16:55 * luke-jr looks forward to the day he can do these gitian builds on ppc64 17:00 -!- brantje [~brantje@165.84.231.15] has quit [] 17:01 -!- scoop [~scoop@static-108-30-224-244.nycmny.fios.verizon.net] has quit [Remote host closed the connection] 17:04 -!- mathepauker [~mathepauk@184.75.223.195] has joined #bitcoin-core-dev 17:10 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 17:21 -!- ccdle12 [~ccdle12@113x38x63x74.ap113.ftth.ucom.ne.jp] has joined #bitcoin-core-dev 17:26 -!- WarrenBuffet [~ident@c-71-238-229-151.hsd1.ar.comcast.net] has quit [Quit: —I-n-v-i-s-i-o-n— 3.3 (November '11)] 17:26 -!- jtimon [~quassel@181.61.134.37.dynamic.jazztel.es] has quit [Quit: gone] 17:32 < sipa> MarcoFalke: f*cking heisenbug 17:33 < sipa> if i even just add a printf of the input to the hash functions in the test, it goes away 17:36 < fanquake> >.> 17:39 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [] 17:42 < luke-jr> sipa: what if you nexti through it? 18:01 -!- mryandao_ is now known as mryandao 18:11 -!- scoop [~scoop@rrcs-67-251-196-106.nyc.biz.rr.com] has joined #bitcoin-core-dev 18:12 -!- RandolfR [~randolf@96.53.47.38] has joined #bitcoin-core-dev 18:12 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 246 seconds] 18:14 -!- scoop [~scoop@rrcs-67-251-196-106.nyc.biz.rr.com] has quit [Remote host closed the connection] 18:15 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 255 seconds] 18:15 -!- scoop [~scoop@rrcs-67-251-196-106.nyc.biz.rr.com] has joined #bitcoin-core-dev 18:16 -!- scoop_ [~scoop@rrcs-67-251-196-106.nyc.biz.rr.com] has joined #bitcoin-core-dev 18:16 -!- scoop [~scoop@rrcs-67-251-196-106.nyc.biz.rr.com] has quit [Read error: Connection reset by peer] 18:26 -!- scoop [~scoop@ip-184-248-104-109.nymnny.spcsdns.net] has joined #bitcoin-core-dev 18:28 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 18:30 -!- scoop_ [~scoop@rrcs-67-251-196-106.nyc.biz.rr.com] has quit [Ping timeout: 255 seconds] 18:32 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev 18:33 -!- michaelfolkson [~textual@85.211.233.88] has quit [Quit: Sleep mode] 18:34 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 18:42 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 18:43 < sipa> MarcoFalke: every time line 551 in crypto_tests.cpp executes, it overwrites the first 64 bytes of the "in" array (regardless of the value of j, always the first 64 bytes...) 18:43 < sipa> this makes no sense whatsoever 18:44 < sipa> perhaps the intermediary sha256 result (created in CHash256::Finalize) somehow is places on the stack there 18:46 -!- Guest42 [~textual@n11211983102.netvigator.com] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 18:49 < sipa> oh no, just the first 32 bytes 18:49 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 18:56 -!- scoop [~scoop@ip-184-248-104-109.nymnny.spcsdns.net] has quit [Remote host closed the connection] 19:04 -!- dviola [~diego@unaffiliated/dviola] has quit [Ping timeout: 245 seconds] 19:10 -!- chainhead_ [~chainhead@2001:19f0:5:e14:5400:ff:fe77:e3d4] has quit [Ping timeout: 258 seconds] 19:10 -!- chainhead [~chainhead@108.61.159.53] has joined #bitcoin-core-dev 19:17 -!- qrestlove [~qrestlove@2601:446:c201:f560:d017:6afc:79e9:5f15] has quit [Ping timeout: 276 seconds] 19:17 -!- dviola [~diego@177.34.230.167] has joined #bitcoin-core-dev 19:18 -!- dviola [~diego@177.34.230.167] has left #bitcoin-core-dev [] 19:19 -!- dviola [~diego@unaffiliated/dviola] has joined #bitcoin-core-dev 19:20 -!- Skirmant [~Skirmant@78-62-14-181.static.zebra.lt] has quit [Ping timeout: 246 seconds] 19:22 -!- Skirmant [~Skirmant@78-62-14-181.static.zebra.lt] has joined #bitcoin-core-dev 19:23 -!- scoop [~scoop@207.237.79.202] has joined #bitcoin-core-dev 19:26 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 268 seconds] 19:29 -!- qrestlove [~qrestlove@2601:446:c201:f560:c0c3:719d:1cdc:f73d] has joined #bitcoin-core-dev 19:31 < luke-jr> * [new tag] v0.18.0.knots20190502 -> v0.18.0.knots20190502 on https://github.com/bitcoinknots/bitcoin/ 19:31 < luke-jr> wumpus: ^ 19:33 -!- scoop [~scoop@207.237.79.202] has quit [Remote host closed the connection] 19:34 -!- ccdle12 [~ccdle12@113x38x63x74.ap113.ftth.ucom.ne.jp] has quit [Remote host closed the connection] 19:35 -!- scoop [~scoop@207.237.79.202] has joined #bitcoin-core-dev 20:00 -!- mathepauker [~mathepauk@184.75.223.195] has quit [] 20:00 -!- scoop [~scoop@207.237.79.202] has quit [Remote host closed the connection] 20:05 -!- scoop [~scoop@207.237.79.202] has joined #bitcoin-core-dev 20:05 -!- scoop [~scoop@207.237.79.202] has quit [Remote host closed the connection] 20:05 -!- scoop [~scoop@207.237.79.202] has joined #bitcoin-core-dev 20:07 -!- scoop [~scoop@207.237.79.202] has quit [Remote host closed the connection] 20:09 -!- matael1 [~matael@185.204.1.185] has joined #bitcoin-core-dev 20:23 -!- scoop [~scoop@207.237.79.202] has joined #bitcoin-core-dev 20:38 < roconnor> Is https://github.com/bitcoin/bitcoin/blob/master/doc/dependencies.md upto date? 20:42 -!- ctrlbreak [~ctrlbreak@142.162.20.53] has quit [Read error: Connection reset by peer] 20:43 -!- ctrlbreak [~ctrlbreak@142.162.20.53] has joined #bitcoin-core-dev 21:00 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Ping timeout: 246 seconds] 21:00 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 21:16 < luke-jr> why isn't https://bitcoincore.org/en/2019/05/02/release-0.18.0/ linked from the main webpage? 21:16 < luke-jr> roconnor: if not, open an issue 21:17 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev 21:27 < roconnor> Heh I'm not sure I could tell if it were out of date or not. 21:40 < luke-jr> hmm, I got a build mismatch on bitcoin-0.18.0-osx-unsigned.tar.gz 21:46 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds] 21:59 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev 22:32 -!- Kvaciral [~Kvaciral@94-214-185-162.cable.dynamic.v4.ziggo.nl] has quit [Ping timeout: 246 seconds] 22:39 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 245 seconds] 22:54 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Ping timeout: 245 seconds] 22:57 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 22:58 -!- rh0nj [~rh0nj@88.99.167.175] has joined #bitcoin-core-dev 22:58 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 22:59 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 23:00 -!- matael1 [~matael@185.204.1.185] has quit [] 23:00 -!- rh0nj [~rh0nj@88.99.167.175] has joined #bitcoin-core-dev 23:06 -!- btc_thc [annalee@5.135.12.125] has joined #bitcoin-core-dev 23:17 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Ping timeout: 255 seconds] 23:20 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 23:20 < fanquake> dongcarl: Had a quick look at guix 1.0.0, my current build setup (swapping 0.16.0 with 1.0.0) breaks with something locale related. Have you had a chance to look at 1.0.0? 23:24 -!- binbasti [~binbasti@89.238.178.75] has joined #bitcoin-core-dev 23:24 -!- pinheadmz [~matthewzi@c-73-92-181-51.hsd1.ca.comcast.net] has quit [Quit: pinheadmz] 23:40 -!- scoop [~scoop@207.237.79.202] has quit [Remote host closed the connection] 23:42 -!- ccdle12 [~ccdle12@113x38x63x74.ap113.ftth.ucom.ne.jp] has joined #bitcoin-core-dev --- Log closed Fri May 03 00:00:01 2019