--- Log opened Sun Mar 24 00:00:24 2019
00:02 -!- TheHoliestRoger [~TheHolies@unaffiliated/theholiestroger] has joined #bitcoin-core-dev
00:03 -!- harrymm [~harrymm@43.249.37.7] has joined #bitcoin-core-dev
00:04 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
00:08 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev
00:21 -!- wzhroho [~robino@195.91.48.199] has joined #bitcoin-core-dev
00:24 -!- zhangzf_ [~zhangzf@223.72.39.108] has quit [Remote host closed the connection]
00:25 -!- zhangzf [~zhangzf@223.72.85.76] has joined #bitcoin-core-dev
00:28 -!- rex4539 [~rex4539@ppp-2-84-169-44.home.otenet.gr] has quit [Quit: rex4539]
00:29 -!- zhangzf [~zhangzf@223.72.85.76] has quit [Ping timeout: 250 seconds]
00:30 -!- wzhroho [~robino@195.91.48.199] has quit [Ping timeout: 246 seconds]
00:47 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
01:18 -!- zhangzf [~zhangzf@223.72.55.1] has joined #bitcoin-core-dev
01:24 -!- wzhroho [~robino@195.91.48.199] has joined #bitcoin-core-dev
01:25 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz]
01:46 -!- wzhroho [~robino@195.91.48.199] has quit [Ping timeout: 246 seconds]
01:46 -!- rex4539 [~rex4539@ppp-2-84-169-44.home.otenet.gr] has joined #bitcoin-core-dev
01:48 -!- harrymm [~harrymm@43.249.37.7] has quit [Ping timeout: 272 seconds]
02:00 -!- harrymm [~harrymm@43.249.37.7] has joined #bitcoin-core-dev
02:22 -!- mn949588 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has joined #bitcoin-core-dev
02:22 -!- mn94958850 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has joined #bitcoin-core-dev
02:25 -!- mn94958853 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has quit [Ping timeout: 250 seconds]
02:26 -!- mn94958849 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has quit [Ping timeout: 250 seconds]
03:14 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
03:20 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
03:20 < bitcoin-git> [bitcoin] promag closed pull request #13189: Remove 2nd mapTx lookup in CTxMemPool::removeForBlock (master...2018-05-txmempool-removeforblock) https://github.com/bitcoin/bitcoin/pull/13189
03:20 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
03:23 -!- obsrver [~quassel@p5DC6B61C.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
03:42 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
04:38 -!- Ocsivit [bc06188a@gateway/web/freenode/ip.188.6.24.138] has joined #bitcoin-core-dev
04:45 -!- jonatack [6d0d4c36@gateway/web/freenode/ip.109.13.76.54] has joined #bitcoin-core-dev
05:17 -!- jonatack [6d0d4c36@gateway/web/freenode/ip.109.13.76.54] has quit [Ping timeout: 256 seconds]
05:21 -!- Ocsivit [bc06188a@gateway/web/freenode/ip.188.6.24.138] has quit [Ping timeout: 256 seconds]
05:43 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
05:47 -!- jonatack [d598a119@gateway/web/freenode/ip.213.152.161.25] has joined #bitcoin-core-dev
06:13 -!- zhangzf [~zhangzf@223.72.55.1] has quit [Remote host closed the connection]
06:17 -!- zhangzf [~zhangzf@120.244.116.206] has joined #bitcoin-core-dev
06:22 -!- zhangzf [~zhangzf@120.244.116.206] has quit [Ping timeout: 272 seconds]
06:24 -!- zhangzf [~zhangzf@223.72.39.108] has joined #bitcoin-core-dev
06:39 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev
06:47 < fanquake_> "Shutdown hangs a bit in IBD"
06:47 < promag> yes?
06:47 < fanquake_> very technical promag :p
06:47 < promag> :D
06:47 < promag> you tell me :p
06:48 < promag> fanquake_: in the 1st log you see it hangs for 19 seconds
06:49 < promag> something is blocking the shutdown
06:49 < echeveria> isn't that expected, to flush the cache to disk? 
06:50 < promag> from a clean datadir, launch and wait for some connections, then ctrl-c
06:51 < promag> echeveria: I don't think it could take 20 seconds, especially right on the begin
06:52 < promag> echeveria: my system is also quite fast
06:55 < harding> Took 8 seconds here from after initial connections established but before the first updatetip, on a fresh datadir with master.
06:56 < promag> harding: thanks
06:56 < echeveria> promag: I mean, I can get it to take like 4 seconds to shut down if I attempt a connection, SIGINT, and then it waits briefly for the timeout. 
06:57 < harding> Here's the big gap in my log: 2019-03-24T13:54:31Z msghand thread exit
06:57 < harding> 2019-03-24T13:54:39Z opencon thread exit
06:57 < promag> I don't see a reason to hold that long
06:57 < echeveria> 2019-03-24T13:56:37.732765Z Shutdown: In progress...
06:57 < echeveria> 2019-03-24T13:56:41.248476Z Shutdown: done
06:58 < echeveria> sort of pales in comparison to most people's time to dump to disk. unless its holding up tests or hitting systemd timeouts I don't see it as an issue particularly. 
07:00 < promag> echeveria: if this happens in travis/appveyor then I think it could be improved
07:01 < promag> there are at least 2 "interruptNet.sleep_for(std::chrono::seconds" in the code
07:03 -!- zhangzf_ [~zhangzf@223.72.85.76] has joined #bitcoin-core-dev
07:03 -!- zhangzf [~zhangzf@223.72.39.108] has quit [Ping timeout: 245 seconds]
07:10 -!- jonatack [d598a119@gateway/web/freenode/ip.213.152.161.25] has quit [Ping timeout: 256 seconds]
07:16 < gmaxwell> promag: travis storage is insanely slow, flushing takes forever.
07:16 < gmaxwell> taking 19 seconds is expected.
07:16 < promag> I'm seeing this locally
07:17 < promag> but not always, I'm trying to figure out what is causing it
07:17 < gmaxwell> turn debug=1 and see if you can see the cause from that?
07:17 < promag> yap
07:18 < promag> but sometimes in travis/appveyor there are random failures when stopping test nodes
07:18 < gmaxwell> your statement about it doing to right away surprises me, but if you said you waited log enough for dbcache to fill I wouldn't be shocked if it took minutes.
07:20 < promag> gmaxwell: first of all, I only observe this in mainnet
07:21 < promag> clear datadir etc
07:21 < promag> bitcoind -debug
07:21 < gmaxwell> promag: thats consistent with it being actual flushing that makes it take time.
07:21 < gmaxwell> (and the assc. fsyncs)
07:22 -!- zhangzf_ [~zhangzf@223.72.85.76] has quit [Read error: Connection reset by peer]
07:23 -!- zhangzf [~zhangzf@223.72.54.252] has joined #bitcoin-core-dev
07:24 < promag> gmaxwell: see https://github.com/bitcoin/bitcoin/issues/15657#issuecomment-475964106
07:25 < gmaxwell> so it was waiting on the dnsseed lookups to finish.
07:30 < promag> gmaxwell: oh, but is it LookupHost that takes so long?
07:32 < gmaxwell> It certantly can, it waits on the network.
07:43 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 244 seconds]
07:48 < gmaxwell> has anyone noticed the github web ui being a lot slower recently or is it just me?
07:51 < gmaxwell> harding: re your question on the mailing list about the transport BIP:   it's hard to coordinate ID assignment.   The initial BIP obviously can just do so.
07:51 < harding> gmaxwell: yeah, that's what I didn't understand, why the initial BIP doesn't just do it.
07:52 < harding> (Especially since it is doing it for three of the messages.)
07:52 < gmaxwell> harding: one alternative would be that any further assignments are negoiated at connect time, then variable length could be ignored... but expecting all future messages to get static one byte asignments wouldn't be realistic.
07:58 < harding> I guess.  I know there's been some contention over things like getdata msg_type between different node implementations before, but 200+ free values seems like enough space that everyone could just get along (or at least specify what they expect via version messages).  Perhaps I'm being too optimistic though.
08:02 < harding> Oh, I guess with encryption and, hopefully, subsequent authentication, we could be expecting to see private extensions to P2P, which could significantly increase the number of message types.  Maybe then it does make more sense to have negotiation.
08:02 < echeveria> is there any actually used implementation of a bitcoin node other than btcd and bitcoin core?
08:05 < gmaxwell> harding: it's just too hard process wise to allocate ids.
08:05 < gmaxwell> like even just cordinating expiremental use...
08:05 < harding> echeveria: not that I'm aware of at the moment.  I was thinking about 2015-17 contention between Bitcoin Core and some of the stuff Unlimited was doing.  Also XT had BIP64 support and a different protocol version.
08:06 < gmaxwell> but negoiation is probably sufficient, I don't really see needing to have more than 256 message types, esp since a message type can be an extended-type-message 
08:06 < harding> gmaxwell: fair enough.  I've seen enough food fights about BIP numbers.
08:07 < gmaxwell> But I can see an argument that the complexity of variable types would better be spent on negoiation, since thats eventually needed in any case... but like consider a message like "sendheaders" ... there is really no reason to give it a shortid.
08:08 < gmaxwell> so even if there were no variable length types, I think there would need to be one or more "option messages" that could be used for things like send headers, and then thats just introducing a variable length type, but maybe at a different 'layer'
08:09 < gmaxwell> (and maybe making it a different layer is a good idea)
08:11 < echeveria> harding: the only other one I was thinking of was Parity Bitcoin, and they seemed to have only been funded to create that for a very short period. 
08:15 < gmaxwell> harding: aside, I kinda worry that too much debate about the shortids will just get them dropped from the protocol... because they're not that important.  But I think that would be a bit sad.
08:15 < harding> gmaxwell: thanks for explaining.  It looked to me like unnecessary complexity, but as long as there's a reasonable use for it (eliminating developer time wasted coordinating allocation), I'm fine with it.
08:16 < gmaxwell> harding: yeah, I think that serves a purpose.
08:16 < gmaxwell> (you might want to follow up on the list, I'm not on it anymore)
08:16 < harding> :-(  Ok.
08:17 < gmaxwell> (ironically, one of the relatively few cases where I think replying would be useful happens shortly after I unsub :P )
09:21 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev
09:31 -!- zhangzf [~zhangzf@223.72.54.252] has quit [Remote host closed the connection]
09:43 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
09:52 -!- jonatack [58aba822@gateway/web/freenode/ip.88.171.168.34] has joined #bitcoin-core-dev
10:39 -!- Randolf [~randolf@96.53.47.42] has quit [Quit: Leaving]
10:40 -!- wzhroho [~robino@195.91.48.99] has joined #bitcoin-core-dev
10:40 -!- dario_ [~dario@220.158.6.85.dynamic.wline.res.cust.swisscom.ch] has joined #bitcoin-core-dev
10:50 -!- wzhroho [~robino@195.91.48.99] has quit [Ping timeout: 246 seconds]
10:59 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection]
11:13 -!- harrymm [~harrymm@43.249.37.7] has quit [Ping timeout: 246 seconds]
11:34 -!- harrymm [~harrymm@43.249.37.7] has joined #bitcoin-core-dev
12:20 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has quit [Remote host closed the connection]
12:36 -!- obsrver [~quassel@p5DC6B61C.dip0.t-ipconnect.de] has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
12:44 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
12:44 < bitcoin-git> [bitcoin] jonasschnelli closed pull request #14050: Add chacha20/poly1305 and chacha20poly1305_AEAD from openssh (master...2018/08/bip151_chachapoly1305) https://github.com/bitcoin/bitcoin/pull/14050
12:44 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
12:57 -!- hibye [617661f6@gateway/web/freenode/ip.97.118.97.246] has joined #bitcoin-core-dev
13:07 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev
13:55 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 245 seconds]
14:00 -!- owowo [~ovovo@s91904426.blix.com] has joined #bitcoin-core-dev
14:00 -!- owowo [~ovovo@s91904426.blix.com] has quit [Changing host]
14:00 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev
14:14 -!- hibye [617661f6@gateway/web/freenode/ip.97.118.97.246] has quit [Ping timeout: 256 seconds]
14:15 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:17 -!- Randolf [~randolf@96.53.47.42] has quit [Quit: Leaving]
14:19 -!- z [1896612a@gateway/web/freenode/ip.24.150.97.42] has joined #bitcoin-core-dev
14:20 -!- z is now known as Guest80974
14:21 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has joined #bitcoin-core-dev
14:22 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
14:23 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
14:24 -!- rh0nj [~rh0nj@88.99.167.175] has joined #bitcoin-core-dev
14:25 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
14:25 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has quit [Ping timeout: 250 seconds]
14:28 -!- wzhroho [~robino@195.91.48.99] has joined #bitcoin-core-dev
15:03 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
15:03 < bitcoin-git> [bitcoin] r8921039 opened pull request #15659: [docs] fix findFork comment (master...fix_findFork_comment) https://github.com/bitcoin/bitcoin/pull/15659
15:03 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
15:20 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
15:20 < bitcoin-git> [bitcoin] sdaftuar opened pull request #15660: [qa] Overhaul p2p_compactblocks.py (master...2019-03-refactor-p2p-compactblocks-2) https://github.com/bitcoin/bitcoin/pull/15660
15:20 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
15:22 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection]
15:23 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev
15:23 < jonasschnelli> harding: I wrote a reply to your mailing list mail but it seem to not appear? any ideas?
15:24 < sipa> jonasschnelli: it takes a while 
15:24 < sipa> all mails are manually approved
15:25 < jonasschnelli> Ah. I just saw that the discussion he had with Greg was 8h ago.. okay. fine
15:32 -!- wzhroho [~robino@195.91.48.99] has quit [Ping timeout: 250 seconds]
15:37 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
15:51 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
15:58 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 245 seconds]
16:34 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Ping timeout: 256 seconds]
16:35 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev
16:42 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
16:53 < fanquake_> Who has access to bitcoincore.org, and could address #15658 ? cfields?
16:53 < gribble> https://github.com/bitcoin/bitcoin/issues/15658 | depends: files missing from bitcoincore.org fallback · Issue #15658 · bitcoin/bitcoin · GitHub
16:59 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
17:05 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
17:21 -!- fanquake_ [~fanquake@unaffiliated/fanquake] has quit []
17:25 -!- Guest80974 [1896612a@gateway/web/freenode/ip.24.150.97.42] has quit [Quit: Page closed]
17:29 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 246 seconds]
17:45 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 246 seconds]
17:52 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev
17:52 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
17:56 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 250 seconds]
17:58 -!- jonatack [58aba822@gateway/web/freenode/ip.88.171.168.34] has quit []
18:05 -!- _Sam-- is now known as tonto27
18:11 -!- tonto27 is now known as _Sam--
18:18 -!- zhangzf [~zhangzf@106.38.157.147] has joined #bitcoin-core-dev
18:24 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev
18:31 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev
18:43 -!- _Sam-- [~greybits@unaffiliated/greybits] has quit [Read error: Connection reset by peer]
18:55 -!- Aaronvan_ is now known as AaronvanW
18:56 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit []
19:12 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 250 seconds]
19:12 -!- BGL [~twenty@75-149-171-58-Washington.hfc.comcastbusiness.net] has quit [Read error: Connection reset by peer]
19:38 -!- ccdle12 [~ccdle12@n11212095090.netvigator.com] has joined #bitcoin-core-dev
19:40 -!- dviola [~diego@unaffiliated/dviola] has joined #bitcoin-core-dev
19:50 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
19:52 -!- kj_ [c7f17d67@gateway/web/freenode/ip.199.241.125.103] has joined #bitcoin-core-dev
19:56 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Remote host closed the connection]
19:57 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev
20:12 -!- BGL [eighty@75-149-171-58-Washington.hfc.comcastbusiness.net] has joined #bitcoin-core-dev
20:15 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Remote host closed the connection]
20:20 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
20:22 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has joined #bitcoin-core-dev
20:25 -!- kj_ [c7f17d67@gateway/web/freenode/ip.199.241.125.103] has quit [Quit: Page closed]
20:26 -!- promag [~promag@bl16-114-47.dsl.telepac.pt] has quit [Ping timeout: 250 seconds]
20:48 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev
20:54 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Ping timeout: 244 seconds]
21:07 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev
21:16 -!- ccdle12 [~ccdle12@n11212095090.netvigator.com] has quit [Remote host closed the connection]
21:34 -!- dviola [~diego@unaffiliated/dviola] has quit [Quit: WeeChat 2.4]
21:35 -!- diego1 [~diego@177.34.230.167] has joined #bitcoin-core-dev
21:35 -!- diego1 [~diego@177.34.230.167] has left #bitcoin-core-dev []
21:44 -!- dviola [~diego@unaffiliated/dviola] has joined #bitcoin-core-dev
22:14 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Remote host closed the connection]
22:16 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev
22:18 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Remote host closed the connection]
22:24 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev
22:31 < fanquake> dongcarl Sorry for the delay, getting to Guix capabilities today. Was sidetracked with other depends stuff.
22:56 -!- ccdle12 [~ccdle12@116.92.188.38] has joined #bitcoin-core-dev
23:06 -!- dviola [~diego@unaffiliated/dviola] has quit [Quit: WeeChat 2.4]
23:21 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz]
23:36 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Remote host closed the connection]
23:59 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Remote host closed the connection]
--- Log closed Mon Mar 25 00:00:25 2019