--- Log opened Tue Sep 18 00:00:12 2018 00:00 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 00:03 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev 00:08 -!- ken2812221_ [~ken281222@118-167-114-230.dynamic-ip.hinet.net] has quit [Ping timeout: 252 seconds] 00:17 -!- setpill [~setpill@unaffiliated/setpill] has quit [Quit: o/] 00:19 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev 00:24 -!- zndtoshi [6da3ea8c@gateway/web/freenode/ip.109.163.234.140] has joined #bitcoin-core-dev 00:25 -!- Krellan [~Krellan@2601:640:4000:9258:e039:953b:3d07:1ce8] has joined #bitcoin-core-dev 00:25 -!- pipp8 [~pipp8@unaffiliated/pipp8] has quit [Quit: Leaving] 00:27 -!- quer [~quer@unaffiliated/quer] has joined #bitcoin-core-dev 00:32 < wumpus> fanquake: great! 00:35 < wumpus> i've pushed 0.16.3 unsigned sigs to gitian.sigs 00:35 -!- rhavar [uid237883@gateway/web/irccloud.com/x-ealcdeabjnnkcsyi] has quit [Quit: Connection closed for inactivity] 00:37 < zndtoshi> Pierre Rochard explained in a presentation about Bitcoin Governance that consensus is reached similary to people meeting at the Schelling point: they know the city but not the location and hour to meet. They will think what the other would do and vice versa and in NY meet in Grand Central Station at noon without communicating. So conseus in Bitcoin is the same: everyone gravitates to the right software to use or the rig 00:37 < zndtoshi> miners. They have a veto option by signaling acceptance or not of a future softfork. But they should/will meet with everyone else at the Schelling point as well. Is there a REAL need for mining nodes to signal inside the Bitcoin Network? If not, are there any risks to remove mining node signaling? 00:37 -!- hebasto [~hebasto@195.60.70.234] has joined #bitcoin-core-dev 00:37 -!- hebasto [~hebasto@195.60.70.234] has quit [Client Quit] 00:38 -!- hebasto [~hebasto@195.60.70.234] has joined #bitcoin-core-dev 00:39 < echeveria> zndtoshi: this is more appropriate for #bitcoin, please ask it there. 00:40 < zndtoshi> Thought I would ask developers if there is contention about this. Sorry, will post there. 00:42 < fanquake> wumpus cool. Looks like yours match my in-progress 0.16.3. Just finishing the macOS build 00:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 00:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 00:53 -!- Krellan [~Krellan@2601:640:4000:9258:e039:953b:3d07:1ce8] has quit [Ping timeout: 250 seconds] 00:56 -!- ossifrage_ [~ossifrage@unaffiliated/ossifrage] has joined #bitcoin-core-dev 00:58 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has quit [Ping timeout: 260 seconds] 01:08 < wumpus> now building 0.17.0rc4 01:23 -!- vicenteH is now known as Zenton 01:27 -!- zndtoshi [6da3ea8c@gateway/web/freenode/ip.109.163.234.140] has quit [Quit: Page closed] 01:36 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Remote host closed the connection] 01:36 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 01:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 01:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 01:45 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 01:55 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 01:56 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 02:07 -!- pipp8 [~pipp8@unaffiliated/pipp8] has joined #bitcoin-core-dev 02:13 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 02:14 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 02:14 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 02:15 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 245 seconds] 02:15 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 02:18 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev 02:20 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Ping timeout: 264 seconds] 02:25 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-ibeexnmcgodgyroi] has joined #bitcoin-core-dev 02:27 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 02:31 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Ping timeout: 246 seconds] 02:34 -!- ken2812221 [~ken281222@180.217.128.66] has quit [Read error: Connection reset by peer] 02:35 -!- ken2812221 [~ken281222@180.217.128.66] has joined #bitcoin-core-dev 02:37 -!- TheCharlatan [~TheCharla@109.236.87.57] has joined #bitcoin-core-dev 02:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 02:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 03:01 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 03:05 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Ping timeout: 246 seconds] 03:32 -!- hebasto [~hebasto@195.60.70.234] has quit [Remote host closed the connection] 03:33 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 03:34 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 03:44 < harding> wumpus: 0.16.3 release PR for BitcoinCore.org for when the binaries are uploaded: https://github.com/bitcoin-core/bitcoincore.org/pull/596 03:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 03:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 03:48 -!- hebasto [~hebasto@195.60.70.234] has joined #bitcoin-core-dev 03:55 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 04:01 -!- setpill [~setpill@unaffiliated/setpill] has quit [Quit: o/] 04:02 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 04:05 < wumpus> harding: thank you, that's quick ! 04:17 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 04:18 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 04:24 < fanquake> wumpus 0.15 will need a build as well I guess, given it's maintenance period doesn't end until after 0.17 release? 04:25 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 252 seconds] 04:40 -!- treebeardd [~treebeard@2601:19b:c601:7cf4:90ae:d99e:a7af:8b2c] has joined #bitcoin-core-dev 04:40 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 04:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 04:44 -!- rex4539 [~rex4539@2a02:587:3508:a300:4c98:6f6:b19a:1e91] has quit [Quit: Textual IRC Client: www.textualapp.com] 04:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 04:47 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 04:49 -!- booyah is now known as [_D 04:59 -!- stevenroose [~steven@vps.weuste.club] has quit [Ping timeout: 264 seconds] 05:00 -!- rex4539 [~rex4539@2a02:587:3508:a300:a84e:c521:e26e:17a5] has joined #bitcoin-core-dev 05:04 -!- stevenroose [~steven@vps.weuste.club] has joined #bitcoin-core-dev 05:15 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 252 seconds] 05:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 05:44 -!- [_D is now known as booyah 05:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 05:50 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #bitcoin-core-dev 05:52 < wumpus> fanquake: yes, probably would make sense to tag a 0.15.x release as well 05:52 < wumpus> though that is less urgent, today I'd ideally like ot upload binaries for 0.17.0rc4 and 0.16.3 at least 05:55 < achow101> 0.14 isn't EOL yet too 05:57 < wumpus> the patch has been backported to both 0.14 and 0.15 06:00 < wumpus> making a release on those branches is pretty much only a matter of writing (short) release notes, if anyone wants to speed it up and have a go at those, be my guest 06:04 < fanquake> wumpus np. I've just merged achow's sigs. So we've got 3 builders for 0.16.3 and 4 for 0.17.0rc4 so far. 06:17 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 06:34 < luke-jr> FWIW, I got CVE-2018-17144 assigned for this 06:40 < wumpus> (and bumping the version, and bumping the mangpages maybe) 06:41 < wumpus> luke-jr: thanks 06:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 06:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 06:52 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 07:02 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 272 seconds] 07:04 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has quit [Quit: esoteric nonsense] 07:08 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev 07:19 -!- ovovo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 07:20 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 240 seconds] 07:30 < provoostenator> (building in progress for 0.17rc4, I'll do 0.16.3 too) 07:31 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [] 07:37 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 07:43 -!- jhfrontz [~Adium@cpe-184-57-118-36.columbus.res.rr.com] has joined #bitcoin-core-dev 07:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 07:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 07:46 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #bitcoin-core-dev 07:50 < luke-jr> trivial bug in release notes: wumpus didn't update translations :p 07:51 -!- jarthur [~jarthur@207.114.244.5] has joined #bitcoin-core-dev 08:28 -!- morcos [~morcos@gateway/tor-sasl/morcos] has quit [Remote host closed the connection] 08:28 -!- morcos [~morcos@gateway/tor-sasl/morcos] has joined #bitcoin-core-dev 08:31 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 08:39 -!- rex4539 [~rex4539@2a02:587:3508:a300:a84e:c521:e26e:17a5] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 08:43 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has joined #bitcoin-core-dev 08:44 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has quit [Client Quit] 08:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 08:44 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 08:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 08:46 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 08:48 -!- treebeardd [~treebeard@2601:19b:c601:7cf4:90ae:d99e:a7af:8b2c] has quit [Remote host closed the connection] 08:57 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has joined #bitcoin-core-dev 09:00 -!- Krellan [~Krellan@2601:640:4000:9258:e039:953b:3d07:1ce8] has joined #bitcoin-core-dev 09:02 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 09:13 -!- nullptr| [~nullptr|@ip-94-113-103-134.net.upcbroadband.cz] has quit [Ping timeout: 252 seconds] 09:15 -!- sfhi [~sfhi@91-152-138-47.elisa-laajakaista.fi] has joined #bitcoin-core-dev 09:18 < provoostenator> I'll tackle the 0.15.2 release notes if nobody else is already doing it. 09:18 -!- treebeardd [~treebeard@c-174-63-103-99.hsd1.vt.comcast.net] has joined #bitcoin-core-dev 09:20 -!- sfhi [~sfhi@91-152-138-47.elisa-laajakaista.fi] has quit [Quit: Leaving] 09:29 < provoostenator> Not that many commits so I can probably do it manually, but the release docs say "ping @wumpus on IRC, he has specific tooling to generate the list of merged pulls and sort them into categories based on labels" 09:30 < provoostenator> For backports, so I refer to the backport PR or to the original one? 09:31 -!- nullptr| [~nullptr|@ip-94-113-103-134.net.upcbroadband.cz] has joined #bitcoin-core-dev 09:33 < luke-jr> might be good to mention the CVE number in release notes yet-to-be-final 09:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 09:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 09:47 < provoostenator> luke-jr: I'll add that to #14262 now 09:47 < gribble> https://github.com/bitcoin/bitcoin/issues/14262 | 0.15.2 release notes by Sjors · Pull Request #14262 · bitcoin/bitcoin · GitHub 09:49 -!- promag [~promag@83.223.251.239] has joined #bitcoin-core-dev 09:56 < luke-jr> * [new tag] v0.16.3.knots20180918 -> v0.16.3.knots20180918 10:09 -!- leishman [~leishman@50.237.29.22] has joined #bitcoin-core-dev 10:09 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has quit [Quit: esoteric nonsense] 10:10 < leishman> https://lincolnloop.com/blog/saying-goodbye-botbotme/ 10:10 < leishman> "If you are a channel operator and would like to download a copy of the logs for your channel, please send a PM to ipmb on Freenode for more details." 10:10 < leishman> I find the bitcoin-core-dev irc logs on botbot super useful for following development progress and learning. Are there channel logs anywhere else? 10:11 < sipa> see topic :) 10:12 -!- promag [~promag@83.223.251.239] has quit [Remote host closed the connection] 10:12 -!- ovovo is now known as owowo 10:12 < leishman> oh haha. I may try to run a version of the botbot logger since it's open source and has a much better UI than the others 10:13 < echeveria> it however, does seem to have a crazy amount of deps. 10:14 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has joined #bitcoin-core-dev 10:15 < echeveria> I guess not too many, I thought foreman was ruby (along with go, python). 10:17 < leishman> yeah. shouldn't be too difficult to write a simple logger and put a UI on top of it either. 10:19 -!- timothy [~tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!] 10:30 -!- leishman [~leishman@50.237.29.22] has quit [Remote host closed the connection] 10:41 < provoostenator> FWIW gen-manpages.sh doesn't work on macOS because of sed issues. 10:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 10:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 10:58 -!- rex4539 [~rex4539@2a02:587:3508:a300:695d:3d5f:d60a:278] has joined #bitcoin-core-dev 10:58 -!- jarthur [~jarthur@207.114.244.5] has quit [Quit: BRB] 11:02 -!- csknk [~csknk@unaffiliated/csknk] has joined #bitcoin-core-dev 11:11 -!- shinohai [btcinfo@gateway/shell/xshellz/x-uzgxflnncphzskwv] has joined #bitcoin-core-dev 11:11 -!- Krellan [~Krellan@2601:640:4000:9258:e039:953b:3d07:1ce8] has quit [Read error: Connection reset by peer] 11:11 -!- Krellan [~Krellan@2601:640:4000:9258:e039:953b:3d07:1ce8] has joined #bitcoin-core-dev 11:19 -!- treebeardd [~treebeard@c-174-63-103-99.hsd1.vt.comcast.net] has quit [Remote host closed the connection] 11:24 -!- d_t [~d_t@108-65-77-11.lightspeed.sntcca.sbcglobal.net] has quit [Ping timeout: 244 seconds] 11:28 -!- Krellan [~Krellan@2601:640:4000:9258:e039:953b:3d07:1ce8] has quit [Remote host closed the connection] 11:31 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:828:347f:6a11:81df] has joined #bitcoin-core-dev 11:34 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:828:347f:6a11:81df] has quit [Client Quit] 11:40 -!- Krellan [~Krellan@2601:640:4000:9258:d06d:2c01:6637:4cde] has joined #bitcoin-core-dev 11:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 11:44 -!- Krellan [~Krellan@2601:640:4000:9258:d06d:2c01:6637:4cde] has quit [Ping timeout: 264 seconds] 11:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 11:46 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 264 seconds] 11:48 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev 11:48 < wumpus> luke-jr: I explicitly didn't update translations, because translations can contain 'bugs' and we're not following an rc process 11:49 < wumpus> but yes, not mentioning it in release notes makes sense 11:54 < wumpus> removed mention of translations from #14251 11:54 < gribble> https://github.com/bitcoin/bitcoin/issues/14251 | doc: Add historical release notes for 0.16.3 by laanwj · Pull Request #14251 · bitcoin/bitcoin · GitHub 11:56 < wumpus> provoostenator: yeah, it's more trouble than it's worth using the tooling in this case 12:07 < provoostenator> I'll remove the translation mention as well. 12:07 -!- jarthur [~jarthur@207.114.244.5] has joined #bitcoin-core-dev 12:18 < wumpus> I'll add in the CVE, good idea 12:31 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Ping timeout: 252 seconds] 12:33 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 12:33 -!- jarthur_ [~jarthur@207.114.244.5] has joined #bitcoin-core-dev 12:36 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 12:37 -!- jarthur [~jarthur@207.114.244.5] has quit [Ping timeout: 244 seconds] 12:43 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 12:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 12:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 12:46 < luke-jr> wumpus: sudo lxc-execute -n gitian -f var/lxc.config -- sudo -u root -i -- bash 12:46 < luke-jr> why is this line in your .assert? O.o 12:49 < provoostenator> I'm trying to build the man pages on a Gitian box, which doesn't have a display. Any idea how to get around "QXcbConnection: Could not connect to display" for "bitcoin-qt --help"? 12:52 < provoostenator> xvfb-run to the rescue 12:58 -!- csknk [~csknk@unaffiliated/csknk] has quit [Quit: leaving] 12:58 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 13:04 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 13:05 < cfields> gitian builders: v0.16.3 detached sigs are pushed 13:06 < gmaxwell> perhaps people that regularly build should get pinged directly? 13:07 < cfields> fanquake/achow101/jonasschnelli/provoostenator/luke-jr/wumpus/MarcoFalke/fivepiece: ^^ 13:07 < achow101> ok 13:07 < cfields> reused from last time 13:09 -!- quer [~quer@unaffiliated/quer] has quit [Ping timeout: 252 seconds] 13:09 -!- quer_ [~quer@unaffiliated/quer] has joined #bitcoin-core-dev 13:09 -!- theymos [~theymos@unaffiliated/theymos] has joined #bitcoin-core-dev 13:20 < wumpus> luke-jr: no idea! 13:21 < wumpus> luke-jr: oh, apparently I added an 'echo' line once 13:26 < wumpus> must have been while debugging some issue with lxc, didn't expect it to end up anywhere else but on my own screen; hope it doesn't cause problems with validation 13:27 -!- quer_ [~quer@unaffiliated/quer] has quit [Read error: Connection reset by peer] 13:27 -!- quer [~quer@unaffiliated/quer] has joined #bitcoin-core-dev 13:31 -!- charlieyou [17e284fb@gateway/web/freenode/ip.23.226.132.251] has joined #bitcoin-core-dev 13:37 -!- charlieyou [17e284fb@gateway/web/freenode/ip.23.226.132.251] has quit [Quit: Page closed] 13:39 -!- charlieyou [~charlieyo@23.226.132.251] has joined #bitcoin-core-dev 13:41 < luke-jr> XD 13:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 13:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 13:46 -!- charlieyou [~charlieyo@23.226.132.251] has quit [Quit: leaving] 13:47 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 13:48 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 13:49 < luke-jr> pushed my signed gitian sigs (3rd one) 13:50 < luke-jr> wumpus: I doubt the line should cause problems; I only noticed it because I was comparing 13:50 -!- charlieyou [~charlieyo@23.226.132.251] has joined #bitcoin-core-dev 13:57 < ossifrage_> gmaxwell, I was just building a fresh bitcoin and noticed I still had a madvise(MADV_RANDOM) when mmapping read only data in leveldb, Is this worth a PR? It seem to reduces the number of pages fetched, but I don't have a good way to show if it actually helps 13:57 -!- ossifrage_ is now known as ossifrage 13:58 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds] 13:58 < provoostenator> Updated man pages in #14263, anything else needed for a v0.15.2 tag? 13:58 < gribble> https://github.com/bitcoin/bitcoin/issues/14263 | Update manpages for 0.15.2 by Sjors · Pull Request #14263 · bitcoin/bitcoin · GitHub 13:58 < luke-jr> ossifrage: LevelDB changes should go upstream 13:58 < wumpus> ossifrage: I think doing optimization PRs only make sense if you can show it is a win 13:59 < wumpus> 0.16.3 binaries up: https://bitcoincore.org/bin/bitcoin-core-0.16.3/ 14:00 -!- charlieyou [~charlieyo@23.226.132.251] has quit [Ping timeout: 246 seconds] 14:00 < ossifrage> wumpus, it does reduce the working set of pages pulled (at least initially) if people actually care about that (I don't) 14:01 < wumpus> ossifrage: I care about it if it helps performance! 14:01 < luke-jr> might be more of a system performance thing than bitcoind performance 14:01 < luke-jr> (which IMO is still worth getting it merged upstream) 14:02 < ossifrage> luke-jr, yeah it is a system level issue, which makes it much harder to test 14:03 < luke-jr> run Chromium on the test system :P 14:03 < luke-jr> on btrfs 14:03 < luke-jr> lol 14:03 < ossifrage> It depends heavily on how much system level memory pressure you have and how fast your IO is 14:06 < ossifrage> luke-jr, g++ seems triggers way more violent page eviction then chrome does. chrome is a slow burn, g++ is a punch in the face 14:06 -!- jarthur_ [~jarthur@207.114.244.5] has quit [Remote host closed the connection] 14:07 -!- jarthur [~jarthur@207.114.244.5] has joined #bitcoin-core-dev 14:07 < luke-jr> ossifrage: well, Chromium seems to rewrite its state text files every second or two, and does fsync on that 14:11 -!- jarthur [~jarthur@207.114.244.5] has quit [Ping timeout: 240 seconds] 14:13 < provoostenator> Is there a way to curse blocks, i.e. the opposite of "preciousblock"? 14:13 < sipa> invalidateblock 14:14 < provoostenator> Thanks 14:14 < sipa> (which is more than cursing, it marks the block as unconditionally invalid) 14:14 < sipa> the oppposite of invalidateblock is reconsiderblock 14:14 < midnightmagic> and of course there's the ancillary haveteawithblock 14:15 < jamesob> any idea when bitcoincore.org is going to be updated with 0.16.3's release notes? 14:17 < theymos> How upgraded are miners right now? 14:17 < wumpus> you people really don't have a second of patience do you 14:17 < midnightmagic> I do! 14:17 < midnightmagic> \o/ 14:17 < luke-jr> lol 14:17 < jamesob> wumpus: sorry 14:18 < wumpus> jamesob: anyow you can find them here https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.16.3.md 14:20 < wumpus> theymos: some miners have already upgraded, don't know the % though 14:21 < theymos> Do you think that I mention in my bitcointalk.org announcement that a chain split is possible? 14:21 -!- jarthur [~jarthur@207.114.244.5] has joined #bitcoin-core-dev 14:22 < provoostenator> theymos: I don't think that's possible 14:23 < achow101> theymos: a chain split is not possible 14:23 < provoostenator> An invalid block could crash a node, but no node, patched or unpatched would accept such a block 14:23 < theymos> ok, thanks 14:24 < achow101> however, if you remove the assert that causes the crash, then you would accept an invalid block. but no release has that 14:28 < wumpus> bitcoincore.org and bitcoin.org PRs have both been merged, should be a matter of times before the sites update... 14:30 < gmaxwell> ossifrage: I should benchmark a reindex I guess. 14:37 -!- jarthur [~jarthur@207.114.244.5] has quit [Remote host closed the connection] 14:42 -!- jarthur [~jarthur@207.114.244.5] has joined #bitcoin-core-dev 14:44 -!- jarthur [~jarthur@207.114.244.5] has quit [Remote host closed the connection] 14:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 14:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 14:57 < wumpus> harding: for some reason, bitcoincore.org is not updating, travis shows build passing etc, any idea what coudl be wrong? 15:05 < wumpus> did anyone urge people to upgrade in #bitcoin yet? 15:08 < luke-jr> I announced Knots there, at least. echeveria changed the topic. don't see an actual Core ann tho 15:09 < wumpus> ok 15:15 < TD-Linux> gmaxwell, are there "standard" reindex benchmark settings? 15:16 < gmaxwell> TD-Linux: defaults, and dbcache=10000 (e.g. big enough that it never flushes) are the two cases that are most interesting. It's useful to -connect=0 to stay offline while benchmarking. 15:18 -!- opdenkamp [~opdenkamp@kodi/staff/dushmaniac] has quit [Ping timeout: 252 seconds] 15:19 < molz> wumpus, i got my nodes updated hours ago, now i'm announcing this on several forums, thanks for all your work and don't let it stress you out 15:28 -!- hebasto [~hebasto@195.60.70.234] has quit [Remote host closed the connection] 15:33 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 15:40 < TD-Linux> how does bitcoin decide how many threads to use? it seems to only be using 16 on my 32 core machine 15:42 -!- niftynei [~niftynei@104.131.77.55] has joined #bitcoin-core-dev 15:44 < fanquake> To set the number of script verification threads, we ultimately call std::thread::hardware_concurrency() 15:44 < luke-jr> TD-Linux: boost::thread::physical_concurrency() 15:44 < luke-jr> fanquake: only when compiling with an obsolete boost 15:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 15:45 < luke-jr> TD-Linux: are you sure it has 32 cores? not 16 + HT? 15:45 < TD-Linux> 64 counting HT 15:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 15:45 * luke-jr wonders what it uses on POWER9 15:45 < fanquake> luke-jr not since #10271 ? 15:45 < gribble> https://github.com/bitcoin/bitcoin/issues/10271 | Use std::thread::hardware_concurrency, instead of Boost, to determine available cores by fanquake · Pull Request #10271 · bitcoin/bitcoin · GitHub 15:46 < luke-jr> oh, didn't realise it changed recently; in any case, nobody should be running that yet 15:48 < luke-jr> TD-Linux: might be good to check if that PR fixes it for you 15:49 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 15:50 < TD-Linux> indeed boost's cpuinfo parsing won't work on my /proc/cpuinfo 15:50 < TD-Linux> it looks for the number of unique (physical id, core id) pairs but that is not a unique identifier on my machine 15:51 < luke-jr> I don't even have physical/core ids in mine XD 15:53 < TD-Linux> yeah so I'm running master for my benchmark 15:53 < TD-Linux> boost would actually say I only have 8 cores with its logic 15:54 < TD-Linux> I'll file a boost bug but I guess I also need a libstdc++ bug 15:54 < luke-jr> >_< 15:55 < luke-jr> does get_nprocs() work? 15:55 < luke-jr> I guess that doesn't try to de-HT 15:56 < TD-Linux> yes it does (returns 64) 15:57 < luke-jr> looks like boost's cpuinfo parsing would fallback to get_nprocs on POWER9 15:57 * TD-Linux kind of doubts that trying to not count HT cores is worth the pain 16:00 < luke-jr> std::thread::hardware_concurrency seems to just wrap get_nprocs on GCC 7.3 16:04 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 264 seconds] 16:07 < gmaxwell> TD-Linux: bitcoin caps at 16 because we measured previously and found that performance stops improving there and gets worse. 16:30 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 16:39 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 16:41 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 16:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 16:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 16:58 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [] 16:58 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 17:28 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [] 17:37 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Remote host closed the connection] 17:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 17:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 18:13 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00:949d:4d9c:a481:d85e] has quit [Remote host closed the connection] 18:15 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 18:19 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00:1039:46fe:92f0:1ffc] has joined #bitcoin-core-dev 18:19 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has quit [Ping timeout: 252 seconds] 18:32 -!- jarthur [~jarthur@2605:6000:1019:41ab:a933:2c9:bd9a:3799] has joined #bitcoin-core-dev 18:33 -!- ctrlbreak [~ctrlbreak@142.162.20.53] has joined #bitcoin-core-dev 18:33 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 18:35 < ctrlbreak> Need a reality check here... 18:35 < ctrlbreak> I just upgraded a bunch of my nodes, and the binaries report 0.16.3 with --version... 18:36 < ctrlbreak> if I check via 'getnetworkinfo'; 18:36 < ctrlbreak> "version": 160000, 18:36 < ctrlbreak> "subversion": "/Satoshi:0.16.0/", 18:36 < ctrlbreak> This typical? (I guess I've just never noticed before). 18:38 < sipa> ctrlbreak: it means you're running 0.16.0 18:38 < ctrlbreak> Oops! Sorry, this probably isn't the appropriate channel. ciao 18:38 < ctrlbreak> Should I head to #bitcoin to find out how I've screwed this up? 18:39 < ctrlbreak> bitcoind and bitcoin-cli report 18:39 < ctrlbreak> bitcoind --version 18:39 < ctrlbreak> Bitcoin Core Daemon version v0.16.3 18:39 < sipa> ctrlbreak: let's move to #bitcoin 18:43 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has quit [Ping timeout: 272 seconds] 18:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 18:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 18:50 -!- rex4539 [~rex4539@2a02:587:3508:a300:695d:3d5f:d60a:278] has quit [Ping timeout: 252 seconds] 19:17 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 245 seconds] 19:18 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev 19:26 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Remote host closed the connection] 19:26 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-core-dev 19:32 -!- Giszmo [~leo@pc-72-54-46-190.cm.vtr.net] has quit [Ping timeout: 244 seconds] 19:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 19:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 19:50 -!- Giszmo [~leo@ip-170-236-219-201.nextelmovil.cl] has joined #bitcoin-core-dev 20:01 -!- lesderid [~lesderid@2a03:b0c0:1:d0::2a5:4002] has quit [Ping timeout: 252 seconds] 20:02 -!- lesderid [~lesderid@2a03:b0c0:1:d0::2a5:4002] has joined #bitcoin-core-dev 20:10 -!- Giszmo [~leo@ip-170-236-219-201.nextelmovil.cl] has quit [Ping timeout: 252 seconds] 20:13 -!- infernix [nix@unaffiliated/infernix] has quit [Ping timeout: 252 seconds] 20:29 -!- Giszmo [~leo@pc-72-54-46-190.cm.vtr.net] has joined #bitcoin-core-dev 20:35 -!- ken2812221_ [~ken281222@36-226-68-170.dynamic-ip.hinet.net] has joined #bitcoin-core-dev 20:40 -!- bralyclow [~bralyclow@76-202-84-204.lightspeed.tukrga.sbcglobal.net] has quit [Ping timeout: 252 seconds] 20:41 -!- infernix [nix@unaffiliated/infernix] has joined #bitcoin-core-dev 20:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 20:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 20:45 -!- bralyclow [~bralyclow@76-202-84-204.lightspeed.tukrga.sbcglobal.net] has joined #bitcoin-core-dev 20:49 -!- Giszmo [~leo@pc-72-54-46-190.cm.vtr.net] has quit [Quit: Leaving.] 20:55 -!- bralyclow [~bralyclow@76-202-84-204.lightspeed.tukrga.sbcglobal.net] has quit [Read error: Connection reset by peer] 21:32 -!- adiabat [~adiabat@63.209.32.102] has quit [Ping timeout: 272 seconds] 21:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 21:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 22:11 -!- hebasto [~hebasto@195.60.70.234] has joined #bitcoin-core-dev 22:22 -!- jarthur [~jarthur@2605:6000:1019:41ab:a933:2c9:bd9a:3799] has quit [Remote host closed the connection] 22:22 -!- jarthur [~jarthur@2605:6000:1019:41ab:a933:2c9:bd9a:3799] has joined #bitcoin-core-dev 22:37 -!- pipp8 [~pipp8@unaffiliated/pipp8] has quit [Ping timeout: 252 seconds] 22:37 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 22:38 -!- pipp8 [~pipp8@unaffiliated/pipp8] has joined #bitcoin-core-dev 22:39 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 22:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 22:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 22:51 -!- hebasto [~hebasto@195.60.70.234] has quit [Remote host closed the connection] 22:51 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 22:56 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 246 seconds] 22:58 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev 23:31 -!- ken2812221_ [~ken281222@36-226-68-170.dynamic-ip.hinet.net] has quit [Ping timeout: 240 seconds] 23:39 -!- grubles [~grubles@gateway/tor-sasl/grubles] has quit [Remote host closed the connection] 23:40 -!- grubles [~grubles@gateway/tor-sasl/grubles] has joined #bitcoin-core-dev 23:44 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 23:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev --- Log closed Wed Sep 19 00:00:13 2018