--- Log opened Sat Mar 16 00:00:17 2019
00:23 -!- rex4539 [~rex4539@ppp-2-84-169-44.home.otenet.gr] has joined #bitcoin-core-dev
00:33 -!- d_t [~d_t@108-65-77-11.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev
00:38 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has joined #bitcoin-core-dev
00:40 < provoostenator> The MVSC (debug) build bitcoind.exe has a weird habit of occasionally pausing. E.g. in the middle of IBD I have to hit space and then it continues.
00:40 < provoostenator> Maybe it's a PowerShell issue? I don't really feel like going down that rabbit hole though...
00:45 -!- d_t [~d_t@108-65-77-11.lightspeed.sntcca.sbcglobal.net] has quit [Ping timeout: 255 seconds]
01:34 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
01:38 -!- d_t [~d_t@108-65-77-11.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev
02:00 -!- mmgen [~mmgen@gateway/tor-sasl/mmgen] has joined #bitcoin-core-dev
02:04 -!- kexkey [~kexkey@139.28.218.6] has quit [Ping timeout: 246 seconds]
03:14 -!- schnerchi [~schnerchi@p54A797C5.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
03:17 -!- ExtraCrispy [~ExtraCris@gateway/tor-sasl/extracrispy] has quit [Ping timeout: 256 seconds]
03:17 -!- schnerchi [~schnerchi@p54A797C5.dip0.t-ipconnect.de] has quit [Client Quit]
03:27 -!- mn9495881 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has quit [Remote host closed the connection]
03:28 -!- mn949588 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has joined #bitcoin-core-dev
03:51 -!- ExtraCrispy [~ExtraCris@gateway/tor-sasl/extracrispy] has joined #bitcoin-core-dev
03:55 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
04:04 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
04:15 -!- jonatack [d598a295@gateway/web/freenode/ip.213.152.162.149] has joined #bitcoin-core-dev
04:24 -!- zhangzf [~zhangzf@223.72.87.57] has quit [Remote host closed the connection]
04:24 -!- zhangzf [~zhangzf@223.72.84.190] has joined #bitcoin-core-dev
04:25 -!- zhangzf [~zhangzf@223.72.84.190] has quit [Remote host closed the connection]
04:25 -!- zhangzf [~zhangzf@223.72.87.47] has joined #bitcoin-core-dev
04:25 -!- zhangzf [~zhangzf@223.72.87.47] has quit [Remote host closed the connection]
04:26 -!- zhangzf [~zhangzf@223.72.40.132] has joined #bitcoin-core-dev
04:26 -!- zhangzf [~zhangzf@223.72.40.132] has quit [Remote host closed the connection]
04:27 -!- zhangzf [~zhangzf@223.72.87.233] has joined #bitcoin-core-dev
04:27 -!- zhangzf [~zhangzf@223.72.87.233] has quit [Remote host closed the connection]
04:27 -!- zhangzf [~zhangzf@223.72.87.57] has joined #bitcoin-core-dev
04:28 -!- zhangzf [~zhangzf@223.72.87.57] has quit [Remote host closed the connection]
04:38 -!- jonatack [d598a295@gateway/web/freenode/ip.213.152.162.149] has quit [Ping timeout: 256 seconds]
04:49 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has joined #bitcoin-core-dev
05:00 < wumpus> hebasto: I didn't change anything with regard to cache settings from the default
05:01 < wumpus> provoostenator: I vaguely remember this, no idea why though
05:01 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has quit [Remote host closed the connection]
05:01 < wumpus> I guess as MSVC has a pretty good debugger it should be possible to find out where it's hanging by breaking when it happens
05:20 < fanquake> evening wumpus
05:20 < wumpus> hello fanquake 
05:21 < fanquake> If you're doing any merging, #15609 and #15604 could go in. Probably don't really have to get the gitian build on the first pr.
05:21 < gribble> https://github.com/bitcoin/bitcoin/issues/15609 | scripts and tools: Set distro explicitly by hebasto · Pull Request #15609 · bitcoin/bitcoin · GitHub
05:21 < gribble> https://github.com/bitcoin/bitcoin/issues/15604 | [docs] release note for disabling reject messages by default by jnewbery · Pull Request #15604 · bitcoin/bitcoin · GitHub
05:22 < fanquake> given that we should have always been getting set to "ubuntu" anyways.
05:22 -!- JackH [~laptop@185.155.119.193] has quit [Ping timeout: 250 seconds]
05:25 < wumpus> yes
05:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
05:27 < bitcoin-git> [bitcoin] laanwj pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/118a5c8d94de...cede01b41668
05:27 < bitcoin-git> bitcoin/master b8705a0 Hennadii Stepanov: Set 'distro' explicitly
05:27 < bitcoin-git> bitcoin/master cede01b Wladimir J. van der Laan: Merge #15609: scripts and tools: Set 'distro' explicitly
05:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
05:28 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
05:28 < bitcoin-git> [bitcoin] laanwj pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/cede01b41668...165ea14efeda
05:28 < bitcoin-git> bitcoin/master 92f3e80 John Newbery: [docs] release note for disabling reject messages by default
05:28 < bitcoin-git> bitcoin/master 165ea14 Wladimir J. van der Laan: Merge #15604: [docs] release note for disabling reject messages by default...
05:28 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
05:28 < fanquake> There is such a long lag between the bot reporting a PR merged and GH's UI actually updating to the merged state..
05:28 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
05:28 < bitcoin-git> [bitcoin] laanwj merged pull request #15604: [docs] release note for disabling reject messages by default (master...release_notes_bip61) https://github.com/bitcoin/bitcoin/pull/15604
05:28 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
05:28 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
05:28 < bitcoin-git> [bitcoin] laanwj merged pull request #15609: scripts and tools: Set 'distro' explicitly (master...20190314-set-distro) https://github.com/bitcoin/bitcoin/pull/15609
05:28 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
05:37 -!- jonatack [b9cee133@gateway/web/freenode/ip.185.206.225.51] has joined #bitcoin-core-dev
05:57 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 245 seconds]
06:46 < Sentineo> gitian build PR created, hope it is ok. I found several stuff that I was not sure what to do, so I had to guess :P 
06:48 < fanquake> Sentineo the sigs look ok. What issues did you run into?
06:52 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
06:53 < Sentineo> I used docker as someone suggested, but had no idea how to use it. so first had to consult help of the gitian build script. Then I had trouble cloning the gitian.sigs repo (as I have no ssh key uploaded to github, that might have been the issue, but cloned it from the github page). Then the signing part of the docs was confusing. As some parts were not defined at all (e.g. $VERSION) and some 
06:53 < Sentineo> were static and had to remove them. But not big issue, but I guess the goal is to make it perhaps very user friendly to run, so I can create a PR for a more detailed steps, e.g. for docker.
06:53 < Sentineo> I used https://github.com/bitcoin-core/docs/blob/master/gitian-building.md
06:54 < Sentineo> the question is who is the target. If a developer, then the docs are fine, if a more novice user it makes a lot of assumptions about prior knowledge.
06:56 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
06:58 < fanquake> Sentineo if you have suggestions on how to make the documentation more user friendly, PRs are definitely welcome
06:58 < fanquake> There is a base level of knowledge assumed, i.e cloning repositories.
06:59 < fanquake> If there inconsistencies with usage of $VERSION that should be fixed up.
06:59 -!- brianhoffman [~brianhoff@pool-72-83-155-130.washdc.fios.verizon.net] has quit [Ping timeout: 272 seconds]
06:59 -!- brianhoffman [~brianhoff@pool-72-83-155-130.washdc.fios.verizon.net] has joined #bitcoin-core-dev
07:40 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev
07:44 -!- mn949588 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has quit [Ping timeout: 244 seconds]
07:47 -!- rex4539 [~rex4539@ppp-2-84-169-44.home.otenet.gr] has quit [Read error: Connection reset by peer]
07:51 -!- jonatack [b9cee133@gateway/web/freenode/ip.185.206.225.51] has quit []
07:53 -!- DougieBot5000_ [~DougieBot@unaffiliated/dougiebot5000] has joined #bitcoin-core-dev
07:54 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev
07:56 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has quit [Ping timeout: 244 seconds]
07:59 -!- mmgen [~mmgen@gateway/tor-sasl/mmgen] has quit [Remote host closed the connection]
08:00 -!- ovovo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 246 seconds]
08:01 -!- mmgen [~mmgen@gateway/tor-sasl/mmgen] has joined #bitcoin-core-dev
08:03 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds]
08:05 -!- profmac [~ProfMac@2001:470:1f0f:226:15de:f544:f5f5:a0e7] has quit [Ping timeout: 240 seconds]
08:07 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
08:09 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
08:12 -!- OneFive [~OneFive@cpc87991-haye25-2-0-cust817.17-4.cable.virginm.net] has joined #bitcoin-core-dev
08:13 -!- OneFive_ [~OneFive@cpc87991-haye25-2-0-cust817.17-4.cable.virginm.net] has joined #bitcoin-core-dev
08:14 -!- OneFive__ [~OneFive@cpc87991-haye25-2-0-cust817.17-4.cable.virginm.net] has joined #bitcoin-core-dev
08:15 -!- dviola [~diego@unaffiliated/dviola] has joined #bitcoin-core-dev
08:15 -!- OneFive_ [~OneFive@cpc87991-haye25-2-0-cust817.17-4.cable.virginm.net] has quit [Client Quit]
08:16 -!- OneFive [~OneFive@cpc87991-haye25-2-0-cust817.17-4.cable.virginm.net] has quit [Ping timeout: 245 seconds]
08:17 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
08:19 -!- profmac [~ProfMac@2001:470:1f0f:226:f17f:7c88:dd21:684a] has joined #bitcoin-core-dev
08:24 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 252 seconds]
08:25 < fanquake> carldong warren Some initial Alpine / Guix Docker instructions up here https://github.com/fanquake/core-review/blob/master/guix/guix.md
08:26 < fanquake> Seems to setup ok. depends currently fails building fontconfig. Looks like maybe a permissions issue not solved by --no-same-owner ? Need to investigate some more.
08:27 < fanquake> I put more info into 15277 anyways.
08:32 -!- stepa[m] [stepamatri@gateway/shell/matrix.org/x-caxdcwofaxxgbnuz] has quit [Remote host closed the connection]
08:32 -!- TheFuzzStone[m] [thefuzzsto@gateway/shell/matrix.org/x-uiwhflvpjsxxcvvm] has quit [Remote host closed the connection]
08:32 -!- ajtowns[m] [ajtownsmat@gateway/shell/matrix.org/x-gdqwdpsjrmdmlnow] has quit [Remote host closed the connection]
08:32 -!- kewde[m] [kewdematri@gateway/shell/matrix.org/x-deebqwmpdnzmkire] has quit [Remote host closed the connection]
08:33 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has joined #bitcoin-core-dev
08:35 -!- rev_strangehope [~revstrang@ec2-13-115-230-7.ap-northeast-1.compute.amazonaws.com] has quit [Ping timeout: 246 seconds]
08:37 -!- rev_strangehope [~revstrang@ec2-13-115-230-7.ap-northeast-1.compute.amazonaws.com] has joined #bitcoin-core-dev
08:41 -!- Inaltoasinistra [~jonathan@93-40-7-67.ip36.fastwebnet.it] has joined #bitcoin-core-dev
08:42 -!- ajtowns[m] [ajtownsmat@gateway/shell/matrix.org/x-eeopasfxickwsmdz] has joined #bitcoin-core-dev
08:43 -!- Inaltoasinistra [~jonathan@93-40-7-67.ip36.fastwebnet.it] has quit [Client Quit]
08:46 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has quit [Remote host closed the connection]
09:04 -!- rex4539 [~rex4539@ppp-2-84-169-44.home.otenet.gr] has joined #bitcoin-core-dev
09:05 -!- kewde[m] [kewdematri@gateway/shell/matrix.org/x-bibcagbijlgdajea] has joined #bitcoin-core-dev
09:05 -!- TheFuzzStone[m] [thefuzzsto@gateway/shell/matrix.org/x-fmqzyhplnzzogdcv] has joined #bitcoin-core-dev
09:05 -!- stepa[m] [stepamatri@gateway/shell/matrix.org/x-wvrnvmqhphzzexam] has joined #bitcoin-core-dev
09:12 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
09:12 < bitcoin-git> [bitcoin] laanwj pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/165ea14efeda...2f501fb5c68d
09:12 < bitcoin-git> bitcoin/master c7ea8d3 practicalswift: Add sizeof(size_t) assumptions
09:12 < bitcoin-git> bitcoin/master c7a7250 practicalswift: Document assumptions about C++ compiler
09:12 < bitcoin-git> bitcoin/master 2f501fb Wladimir J. van der Laan: Merge #15522: Document sizeof(size_t) assumptions and compiler assumptions...
09:12 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
09:13 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
09:13 < bitcoin-git> [bitcoin] laanwj merged pull request #15522: Document sizeof(size_t) assumptions and compiler assumptions in assumptions.h (master...size_t-assumptions) https://github.com/bitcoin/bitcoin/pull/15522
09:13 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
09:26 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev
09:38 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
10:00 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz]
10:18 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
10:24 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 246 seconds]
10:26 -!- afk11 [~afk11@79.97.107.223] has joined #bitcoin-core-dev
10:26 -!- afk11 [~afk11@79.97.107.223] has quit [Changing host]
10:26 -!- afk11 [~afk11@unaffiliated/afk11] has joined #bitcoin-core-dev
10:27 -!- afk11 [~afk11@unaffiliated/afk11] has quit [Client Quit]
10:27 -!- afk11 [~afk11@79.97.107.223] has joined #bitcoin-core-dev
10:32 -!- Bullitje [~Bullit01@042-236-158-163.dynamic.caiway.nl] has quit [Ping timeout: 246 seconds]
10:36 -!- Bullit [~Bullit01@042-236-158-163.dynamic.caiway.nl] has joined #bitcoin-core-dev
10:40 -!- DougieBot5000_ is now known as DougieBot5000
10:42 < provoostenator> Fwiw I succesfully used fanquake's Gitian Docker instructions on my Mac. Ideally those instructions would be added to the gitian-builder script.
10:44 < provoostenator> If that script also handles the signing and pushing signatures to Github, then it might be able to catch configuration mistakes like not having an SSH setup or missing dependencies. Generally those checks are added as people run into problems themselves :-)
10:47 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has joined #bitcoin-core-dev
10:51 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has quit [Ping timeout: 245 seconds]
10:53 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev
10:55 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
10:58 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds]
11:13 -!- kexkey [~kexkey@139.28.218.6] has joined #bitcoin-core-dev
11:44 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds]
11:47 -!- dviola [~diego@unaffiliated/dviola] has quit [Quit: WeeChat 2.4]
11:48 -!- afk11 [~afk11@79.97.107.223] has quit [Remote host closed the connection]
12:00 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
12:00 -!- rex4539 [~rex4539@ppp-2-84-169-44.home.otenet.gr] has quit [Read error: Connection reset by peer]
12:01 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Client Quit]
12:03 -!- jonatack [58aba822@gateway/web/freenode/ip.88.171.168.34] has joined #bitcoin-core-dev
12:05 -!- rex4539 [~rex4539@ppp-2-84-169-44.home.otenet.gr] has joined #bitcoin-core-dev
12:07 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has quit [Remote host closed the connection]
12:16 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Ping timeout: 244 seconds]
12:18 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
12:32 < dongcarl> fanquake: I think tar is trying to set the mtime of the extracted file, but doesn’t have permission? I’m afk but there’s probably a flag to disable that
12:32 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has joined #bitcoin-core-dev
12:34 -!- mn949588 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has joined #bitcoin-core-dev
12:42 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 255 seconds]
12:44 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz]
12:46 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has quit [Remote host closed the connection]
12:59 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 268 seconds]
13:01 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
13:05 -!- mn949588 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has quit [Remote host closed the connection]
13:05 -!- mn949588 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has joined #bitcoin-core-dev
13:05 -!- mn949588 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has quit [Remote host closed the connection]
13:06 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]
13:06 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev
13:12 -!- ExtraCrispy [~ExtraCris@gateway/tor-sasl/extracrispy] has quit [Ping timeout: 256 seconds]
13:23 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz]
13:26 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
13:28 -!- obsrver [~quassel@p4FF16E4D.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
13:31 < gmaxwell> brought up a node on a new IP, within 5 minutes I has 12 inbound connections... all of them were mass connectors on my published banlists...
13:31 < gmaxwell> so are mass connectors chewing up >10% of inbound port capacity?
13:40 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has joined #bitcoin-core-dev
13:47 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has joined #bitcoin-core-dev
13:48 -!- dviola [~diego@unaffiliated/dviola] has joined #bitcoin-core-dev
13:51 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has quit [Ping timeout: 255 seconds]
13:53 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds]
13:59 -!- Licoche [~Licoche@pc-207-155-164-190.cm.vtr.net] has joined #bitcoin-core-dev
14:13 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev
14:17 -!- Licoche [~Licoche@pc-207-155-164-190.cm.vtr.net] has quit [Remote host closed the connection]
14:18 -!- obsrver [~quassel@p4FF16E4D.dip0.t-ipconnect.de] has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
14:20 -!- d_t [~d_t@108-65-77-11.lightspeed.sntcca.sbcglobal.net] has quit [Ping timeout: 246 seconds]
14:28 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has quit [Remote host closed the connection]
14:28 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
14:36 -!- DM21 [~dm21@2604:2000:1343:8b42:2422:5c8e:cc07:1533] has joined #bitcoin-core-dev
14:36 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection]
14:36 -!- DM21 [~dm21@2604:2000:1343:8b42:2422:5c8e:cc07:1533] has quit [Client Quit]
14:38 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has joined #bitcoin-core-dev
14:44 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 272 seconds]
14:46 -!- dviola [~diego@unaffiliated/dviola] has quit [Quit: WeeChat 2.4]
14:47 -!- d_t [~d_t@108-65-77-11.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev
14:48 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
14:54 < provoostenator> Feedback on the (de)serialization code in #15487 would be quite useful, if anyone has time in the next couple of days.
14:54 < gribble> https://github.com/bitcoin/bitcoin/issues/15487 | [WIP] descriptor based wallet serialization and import by Sjors · Pull Request #15487 · bitcoin/bitcoin · GitHub
14:56 -!- jonatack [58aba822@gateway/web/freenode/ip.88.171.168.34] has quit [Ping timeout: 256 seconds]
14:56  * provoostenator goes off to unfry brain...
14:59 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev
15:04 -!- mmgen [~mmgen@gateway/tor-sasl/mmgen] has quit [Quit: (https://github.com/mmgen) leaving]
15:07 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
15:07 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has joined #bitcoin-core-dev
15:08 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
15:08 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
15:14 < gmaxwell> Does "bitcoin core" sound like "bitcoin bark" in chinese or something? https://bitcoin.stackexchange.com/questions/84185/i-was-tasked-with-installing-a-bitcoin-kernel-on-ubuntu-and-i-had-questions
15:15 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
15:15 < sipa> lol
15:19 < gmaxwell> Googling shows one or two other pages also saying "bitcoin bark" but it doesn't appear to be an altcoin.
15:24 < gmaxwell> okay an estonian word for "bark" is "koor"  (and presumably other languages have a similar mapping)
15:25 < gmaxwell> thats kinda confusing since bark and core have sort of opposite meanings (like tree bark vs tree core)
15:28 < gmaxwell> (I guess finish would be a likely candidate)
15:29 -!- jonatack [52661bab@gateway/web/freenode/ip.82.102.27.171] has joined #bitcoin-core-dev
15:30 < gmaxwell> (and indeed google translate says that "tree bark" is "puun kuori" in finnish)
15:31 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
15:31 < luke-jr> I know of Karna, but not bark :P
15:48 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has joined #bitcoin-core-dev
16:06 < promag> any reason to not tag #15313 0.18?
16:06 < gribble> https://github.com/bitcoin/bitcoin/issues/15313 | Qt: avoid AskPassphraseDialog synchronous QDialog.exec() calls by jonasschnelli · Pull Request #15313 · bitcoin/bitcoin · GitHub
16:07 < gmaxwell> it's incomplete. :(
16:07 < gmaxwell> 0.18 tagging will force another RC and add weeks to the release, but won't fix the other cases where the same bug exists.
16:08 < promag> fixes the reported bug
16:09 < promag> but yeah, no need to delay 0.18
16:09 < gmaxwell> read the rest of the bug, it points out that a bunch of other versions of the same thing exists
16:09 < gmaxwell> I think for 0.18 it might be better to revert #14941 which I believe introduced the crash.
16:09 < gribble> https://github.com/bitcoin/bitcoin/issues/14941 | rpc: Make unloadwallet wait for complete wallet unload by promag · Pull Request #14941 · bitcoin/bitcoin · GitHub
16:10 < gmaxwell> Shipping with a known easily triggerable crash isn't ideal (in partiular because the crash can corrupt your blockchain state e.g. if you do it during IBD)
16:11 < gmaxwell> or alternatively disable wallet unloading with the gui up in 0.18.0.
16:11 < promag> QDialog blocking calls are not recommended
16:11 < promag> you can always console->unloadwallet
16:12 < gmaxwell> Sure. I'm not saying that that sort of thing is a good long term fix.
16:12 < promag> for RPC clients 14941 is more important IMO
16:13 < gmaxwell> But in general when we find new functionality causes crashes shortly before a release we should probably favor reverting-- or applying blunt workaround like disabling a non-criticial feature-- rather than making more changes which could introduce their own bugs.
16:14 < promag> true, jonas fix "looks harmless" but indeed it's too late for that
16:14 < promag> I'm afraid reverting that one can open other problems
16:17 < promag> btw, I meant to ask this before, but is a "-experimental=foo" option reasonable?
16:18 < gmaxwell> the idea behind a reverting preference is that /generally/ whatever problems existed with the old behavior aren't that fatal-- since we have thousands and thousands of users running with them already.  this is obviously not always the case, e.g. for changes that have been in the codebase for 7 months which interact with other features...
16:19 < gmaxwell> promag: maybe? depends on the thing. We've pretty commonly added new functionality and defaulted it to disabled, then enabled it in a later release, and even in some cases later removed the configuration setting.. which is functionally equivilent.  'Nesting options' is probably not ideal.
16:20 < promag> or just -experimental, where a bunch of "experimental" stuff is enabled
16:20 < luke-jr> promag: IMO it sounds like you're thinking of "just merge it into Knots for now" ;)
16:20 < gmaxwell> I'd rather see -experimental-foo=1 than -experimental=foo.  also, I don't think we should be shipping a "bunch" of expiremental stuff generally.
16:21 < promag> luke-jr: is that officially supported here?
16:22 < gmaxwell> usage by users of optional features is very low from what I've seen, and they carry risk.  I think the reason we end up with stuff default off in an initial release is often when functionality was intended to get turned on but didn't quite reach enough maturity (or even when it turned out to have shortcomings at the last minute)
16:23 < gmaxwell> or when it has interop impact and we want people to test with it before defaulting it on...
16:23 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has quit [Remote host closed the connection]
16:25 < luke-jr> promag: each person can decide what they will support as usual; complicating Core with a -experimental mode wouldn't reasonably increase support though
16:26 < luke-jr> (as for "here": this isn't a support channel in the first place)
16:29 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
16:30 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Client Quit]
16:30 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
16:31 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
16:31 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds]
16:34 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
16:34 < bitcoin-git> [bitcoin] droark opened pull request #15611: Add Gitian key for droark (master...master-keys-update) https://github.com/bitcoin/bitcoin/pull/15611
16:34 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
16:35 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has joined #bitcoin-core-dev
16:39 < promag> gmaxwell: reverting 14941 requires rc3?
16:50 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 245 seconds]
16:52 < promag> gmaxwell: btw, 14941 fixes #14917
16:52 < gribble> https://github.com/bitcoin/bitcoin/issues/14917 | wallet_multiwallet --usecli fails with "Duplicate -wallet filename specified" · Issue #14917 · bitcoin/bitcoin · GitHub
16:57 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has quit [Remote host closed the connection]
16:58 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has joined #bitcoin-core-dev
17:02 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has quit [Ping timeout: 246 seconds]
17:02 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has joined #bitcoin-core-dev
17:07 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has quit [Ping timeout: 245 seconds]
17:17 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has quit [Remote host closed the connection]
17:40 < gmaxwell> promag: right, but we shouldn't introduce a user exposed crasher over a spurrious test failure...
17:40 < gmaxwell> in any case, I'm not married to the idea of reverting it,  but that should be our _default_ response to serious bugs found in an RC esp when there isn't a really straight forward and clear fix.
17:48 -!- ap4lmtree [ap4lmtree@unaffiliated/ap4lmtree] has quit [Ping timeout: 246 seconds]
17:50 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has joined #bitcoin-core-dev
17:51 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev
17:56 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has quit [Ping timeout: 255 seconds]
17:58 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 268 seconds]
18:08 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
18:14 -!- ap4lmtree [ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev
18:31 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
19:00 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
19:01 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
19:09 -!- d_t [~d_t@108-65-77-11.lightspeed.sntcca.sbcglobal.net] has quit [Read error: Connection reset by peer]
19:50 -!- Taek [~quassel@2001:41d0:1:472e::] has quit [Quit: No Ping reply in 180 seconds.]
19:50 -!- Taek [~quassel@2001:41d0:1:472e::] has joined #bitcoin-core-dev
20:01 -!- harrymm [~harrymm@69.161.195.103] has quit []
20:33 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds]
20:36 < fanquake> dongcarl Looks like it's not permissions, but related to the fact that inside depends/x86_64-pc-linux-gnu/lib, libexpat.so & libfreetype.so are symlinks
20:36 < fanquake> libexpat.so: symbolic link to libexpat.so.1.6.8
20:36 < fanquake> libexpat.so.1.6.8: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, not stripped
20:37 < dongcarl> fanquake: Okay thanks, I’ll take a look on when back behind keyboard. Your setup is documented in the link you sent?
20:39 < fanquake> dongcarl no worries. Yea, and I'll update my comment here: https://github.com/bitcoin/bitcoin/pull/15277#issuecomment-473539212, with some more info.
20:45 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz]
20:47 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has joined #bitcoin-core-dev
20:52 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has quit [Ping timeout: 246 seconds]
21:17 -!- harrymm [~harrymm@69.161.195.103] has joined #bitcoin-core-dev
21:18 -!- qrestlove [~qrestlove@2601:446:c201:f560:1194:3875:20cc:e764] has quit [Ping timeout: 252 seconds]
21:25 -!- tieppv [7b108a94@gateway/web/freenode/ip.123.16.138.148] has joined #bitcoin-core-dev
21:25 < tieppv> hello
21:31 -!- qrestlove [~qrestlove@2601:446:c201:f560:4166:2e20:21a6:3912] has joined #bitcoin-core-dev
21:54 -!- tieppv [7b108a94@gateway/web/freenode/ip.123.16.138.148] has quit [Ping timeout: 256 seconds]
22:27 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
22:41 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz]
22:48 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has joined #bitcoin-core-dev
22:53 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has quit [Ping timeout: 246 seconds]
23:59 -!- TheHoliestRoger [~TheHolies@unaffiliated/theholiestroger] has quit [Quit: Find me in #TheHolyRoger or https://theholyroger.com]
--- Log closed Sun Mar 17 00:00:18 2019