--- Log opened Tue Feb 26 00:00:01 2019
00:00 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 240 seconds]
00:03 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev
00:07 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev
00:16 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev
00:18 < Muoi> Btw, I would be very gladful if you guys can help to take a look at this problem. I can provide detailed debug.log, node specs, etc..
00:21 < gmaxwell> Muoi: thanks someone will. If you can hang around (or leave an email). It would be helpful to open an issue too.
00:22 < gmaxwell> (I'm not looking at it right now since it's late for me and I should be asleep)
00:23 < Muoi> Okay sure, I will open an issue. FYI, my email is muoitran@comp.nus.edu.sg. Please feel free to drop an email so we can discuss more. Good night!. 
00:24 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection]
00:26 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
00:39 -!- jungly [~quassel@79.8.200.97] has joined #bitcoin-core-dev
00:42 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
01:05 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
01:12 -!- droark [~droark@c-24-21-203-195.hsd1.or.comcast.net] has joined #bitcoin-core-dev
01:14 -!- siom [~siom@165.84.231.19] has joined #bitcoin-core-dev
01:15 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 250 seconds]
01:18 -!- Deinogalerix21 [~Deinogale@89.238.176.150] has joined #bitcoin-core-dev
01:23 -!- ctrlbreak_MAD [~ctrlbreak@142.162.20.53] has joined #bitcoin-core-dev
01:24 -!- murrayn [~murrayn@unaffiliated/murrayn] has quit [Read error: Connection reset by peer]
01:24 -!- siom_ [~siom@165.84.231.19] has joined #bitcoin-core-dev
01:25 -!- siom [~siom@165.84.231.19] has quit [Remote host closed the connection]
01:27 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev
01:28 -!- murrayn [~murrayn@S0106f8a097f16608.ok.shawcable.net] has joined #bitcoin-core-dev
01:28 -!- murrayn [~murrayn@S0106f8a097f16608.ok.shawcable.net] has quit [Changing host]
01:28 -!- murrayn [~murrayn@unaffiliated/murrayn] has joined #bitcoin-core-dev
01:29 -!- Kvaciral_ [~Kvaciral@5ED6B9A2.cm-7-7c.dynamic.ziggo.nl] has joined #bitcoin-core-dev
01:30 -!- ctrlbreak [~ctrlbreak@142.162.20.53] has quit [Ping timeout: 245 seconds]
01:30 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 245 seconds]
01:30 -!- Kvaciral [~Kvaciral@5ED6B9A2.cm-7-7c.dynamic.ziggo.nl] has quit [Ping timeout: 245 seconds]
01:30 -!- andytoshi [~apoelstra@unaffiliated/andytoshi] has quit [Remote host closed the connection]
01:30 -!- gkrizek [~gkrizek@ec2-34-222-229-197.us-west-2.compute.amazonaws.com] has quit [Read error: Connection reset by peer]
01:30 -!- tryphe_ is now known as tryphe
01:30 -!- andytoshi [~apoelstra@wpsoftware.net] has joined #bitcoin-core-dev
01:30 -!- andytoshi [~apoelstra@wpsoftware.net] has quit [Changing host]
01:30 -!- andytoshi [~apoelstra@unaffiliated/andytoshi] has joined #bitcoin-core-dev
01:30 -!- gkrizek [~gkrizek@ec2-34-222-229-197.us-west-2.compute.amazonaws.com] has joined #bitcoin-core-dev
01:33 -!- gkrizek3 [~gkrizek@ec2-34-222-229-197.us-west-2.compute.amazonaws.com] has joined #bitcoin-core-dev
01:34 -!- kabaum [~kabaum@2001:9b1:efd:9b00:36e6:d7ff:fe35:5aa] has joined #bitcoin-core-dev
01:34 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
01:35 -!- rockhouse [~rockhouse@unaffiliated/rockhouse] has quit [Ping timeout: 245 seconds]
01:35 -!- gkrizek [~gkrizek@ec2-34-222-229-197.us-west-2.compute.amazonaws.com] has quit [Ping timeout: 245 seconds]
01:35 -!- davec_ [~davec@cpe-24-243-249-218.hot.res.rr.com] has quit [Ping timeout: 245 seconds]
01:35 -!- davec [~davec@cpe-24-243-249-218.hot.res.rr.com] has joined #bitcoin-core-dev
01:35 -!- rockhouse [~rockhouse@unaffiliated/rockhouse] has joined #bitcoin-core-dev
01:39 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 255 seconds]
01:49 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev
02:06 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev
02:09 -!- volkov [~volkov@gateway/tor-sasl/volkov] has joined #bitcoin-core-dev
02:17 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
02:21 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds]
02:29 -!- Deinogalerix21 [~Deinogale@89.238.176.150] has quit [Quit: WeeChat 2.4]
02:41 -!- darosior [52ff9820@gateway/web/freenode/ip.82.255.152.32] has joined #bitcoin-core-dev
02:48 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
03:02 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
03:03 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
03:07 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 255 seconds]
03:20 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
03:20 < bitcoin-git> [bitcoin] darosior opened pull request #15483: Adding a 'logpath' entry to getrpcinfo, as discussed in #15438 (master...getrpcinfo_logpath) https://github.com/bitcoin/bitcoin/pull/15483
03:20 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
03:25 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
03:25 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
03:25 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
03:45 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
03:46 -!- mmgen [~mmgen@gateway/tor-sasl/mmgen] has joined #bitcoin-core-dev
04:04 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev
04:05 -!- volkov [~volkov@gateway/tor-sasl/volkov] has quit [Quit: volkov]
04:10 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds]
04:20 -!- junior_ [ac69d512@gateway/web/freenode/ip.172.105.213.18] has joined #bitcoin-core-dev
04:20 -!- junior_ [ac69d512@gateway/web/freenode/ip.172.105.213.18] has quit [Client Quit]
04:21 -!- darosior [52ff9820@gateway/web/freenode/ip.82.255.152.32] has quit [Ping timeout: 256 seconds]
04:25 -!- Paz [~MrPaz@84.39.112.85] has joined #bitcoin-core-dev
04:25 -!- tryphe_ [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
04:25 -!- Paz is now known as Guest7635
04:26 -!- booyah_ [~bb@193.25.1.157] has joined #bitcoin-core-dev
04:28 -!- cryptapus_ [~cryptapus@jupiter.osmus.org] has joined #bitcoin-core-dev
04:28 -!- cryptapus_ [~cryptapus@jupiter.osmus.org] has quit [Changing host]
04:28 -!- cryptapus_ [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev
04:30 -!- commavir_ [~vir@23.226.237.192] has joined #bitcoin-core-dev
04:30 -!- commavir [~vir@23.226.237.192] has quit [Ping timeout: 246 seconds]
04:30 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 246 seconds]
04:30 -!- spinza [~spin@155.93.246.187] has quit [Ping timeout: 246 seconds]
04:30 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 246 seconds]
04:30 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Ping timeout: 246 seconds]
04:30 -!- instagibbs [~instagibb@pool-100-15-135-248.washdc.fios.verizon.net] has quit [Ping timeout: 246 seconds]
04:30 -!- booyah [~bb@193.25.1.157] has quit [Ping timeout: 246 seconds]
04:30 -!- sgeisler [~quassel@x8d1ee20a.agdsn.tu-dresden.de] has quit [Ping timeout: 246 seconds]
04:30 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Ping timeout: 246 seconds]
04:30 -!- sgeisler [~quassel@x8d1ee20a.agdsn.tu-dresden.de] has joined #bitcoin-core-dev
04:30 -!- victorSN [~victorSN@unaffiliated/victorsn] has quit [Ping timeout: 255 seconds]
04:30 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Ping timeout: 255 seconds]
04:30 -!- so [~so@unaffiliated/so] has quit [Ping timeout: 255 seconds]
04:30 -!- MrPaz [~MrPaz@84.39.112.85] has quit [Ping timeout: 255 seconds]
04:30 -!- so_ [~so@unaffiliated/so] has joined #bitcoin-core-dev
04:30 -!- instagibbs [~instagibb@100.15.135.248] has joined #bitcoin-core-dev
04:30 -!- Emcy [~Emcy@147.85.7.51.dyn.plus.net] has joined #bitcoin-core-dev
04:31 -!- rh0nj [~rh0nj@88.99.167.175] has joined #bitcoin-core-dev
04:31 -!- Emcy [~Emcy@147.85.7.51.dyn.plus.net] has quit [Changing host]
04:31 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev
04:31 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev
04:31 -!- victorSN [~victorSN@unaffiliated/victorsn] has joined #bitcoin-core-dev
04:32 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Remote host closed the connection]
04:35 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Client Quit]
04:35 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev
04:36 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Remote host closed the connection]
04:37 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev
04:37 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-core-dev
04:37 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has quit [Changing host]
04:37 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
04:40 -!- commavir_ is now known as commavir
04:42 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 245 seconds]
04:45 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
04:49 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds]
04:54 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 268 seconds]
04:59 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev
05:07 -!- lio17 [~lio17@80.ip-145-239-89.eu] has quit [Quit: lio17]
05:07 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
05:08 -!- lio17 [~lio17@80.ip-145-239-89.eu] has joined #bitcoin-core-dev
05:08 -!- lio17 [~lio17@80.ip-145-239-89.eu] has quit [Client Quit]
05:09 -!- lio17 [~lio17@80.ip-145-239-89.eu] has joined #bitcoin-core-dev
05:09 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
05:11 -!- siom_ [~siom@165.84.231.19] has quit [Remote host closed the connection]
05:14 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 244 seconds]
05:26 -!- TheCharlatan [~TheCharla@109.236.87.57] has quit [Read error: Connection reset by peer]
05:27 -!- muoitran [8984da19@gateway/web/freenode/ip.137.132.218.25] has joined #bitcoin-core-dev
05:27 -!- TheCharlatan [~TheCharla@109.236.87.57] has joined #bitcoin-core-dev
05:28 -!- muoitran [8984da19@gateway/web/freenode/ip.137.132.218.25] has quit [Client Quit]
05:34 < sdaftuar> Muoi: hi, i'd like to investigate the p2p issue you're seeing (i wrote the code that seems to be involved).  can you post your debug.log somewhere? if there might be sensitive information in it (eg wallet related things, ip addresses, etc) i'm most interested in just a few lines that might appear:
05:35 < sdaftuar> lines involving "UpdateTip", "Potential stale tip", "disconnecting extra outbound peer", "keeping outbound peer"
05:35 < sdaftuar> also "setting try another outbound peer"
05:39 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
05:41 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
05:46 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 240 seconds]
05:46 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection]
05:50 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Read error: Connection reset by peer]
05:51 -!- Zenton [~user@unaffiliated/vicenteh] has joined #bitcoin-core-dev
06:08 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev
06:12 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has quit [Ping timeout: 250 seconds]
06:21 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:21 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/8f470ecc534d...d88f7f8764b1
06:21 < bitcoin-git> bitcoin/master ef362f2 Wladimir J. van der Laan: rpc/gui: Remove 'Unknown block versions being mined' warning
06:21 < bitcoin-git> bitcoin/master d88f7f8 MarcoFalke: Merge #15471: rpc/gui: Remove 'Unknown block versions being mined' warning...
06:21 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:22 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:22 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #15471: rpc/gui: Remove 'Unknown block versions being mined' warning (master...2019_02_false_positives) https://github.com/bitcoin/bitcoin/pull/15471
06:22 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:24 -!- booyah_ [~bb@193.25.1.157] has quit [Read error: Connection reset by peer]
06:25 -!- booyah_ [~bb@193.25.1.157] has joined #bitcoin-core-dev
06:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:27 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #13972: Remove 16 bits from versionbits signalling system (BIP320) (master...reservedbits2) https://github.com/bitcoin/bitcoin/pull/13972
06:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:27 < bitcoin-git> [bitcoin] MarcoFalke reopened pull request #13972: Remove 16 bits from versionbits signalling system (BIP320) (master...reservedbits2) https://github.com/bitcoin/bitcoin/pull/13972
06:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:29 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev
06:36 -!- rafalcpp_ is now known as rafalcpp
06:37 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev
06:39 -!- phwalkr [~phwalkr@192.32.61.94.rev.vodafone.pt] has joined #bitcoin-core-dev
06:45 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
06:45 < phantomcircuit> Muoi, possibly your system clock is broken
06:52 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection]
06:53 -!- promag_ [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev
07:24 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has joined #bitcoin-core-dev
07:27 -!- darosior [52ff9820@gateway/web/freenode/ip.82.255.152.32] has joined #bitcoin-core-dev
07:33 -!- elichai2 [uid212594@gateway/web/irccloud.com/x-tqempquacvnrwdnh] has joined #bitcoin-core-dev
07:41 -!- Muoi_ [8984da19@gateway/web/freenode/ip.137.132.218.25] has joined #bitcoin-core-dev
07:42 -!- Muoi_ [8984da19@gateway/web/freenode/ip.137.132.218.25] has quit [Client Quit]
07:56 -!- dviola [~diego@unaffiliated/dviola] has joined #bitcoin-core-dev
08:15 -!- _flow_ [~none@salem.informatik.uni-erlangen.de] has joined #bitcoin-core-dev
08:17 -!- _flow_ [~none@salem.informatik.uni-erlangen.de] has quit [Client Quit]
08:17 -!- _flow_ [~none@salem.informatik.uni-erlangen.de] has joined #bitcoin-core-dev
08:17 -!- setpill [~setpill@unaffiliated/setpill] has quit [Quit: o/]
08:18 -!- dqx_ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev
08:24 -!- darosior [52ff9820@gateway/web/freenode/ip.82.255.152.32] has quit [Ping timeout: 256 seconds]
08:33 -!- dviola [~diego@unaffiliated/dviola] has quit [Quit: WeeChat 2.4]
08:54 -!- tryphe_ is now known as tryphe
08:55 < sdaftuar> phantomcircuit: it seems to be a bug in the addrman/net interaction, see #15484.  can someone tag that with the Bug label?  we should fix it...
08:55 < gribble> https://github.com/bitcoin/bitcoin/issues/15484 | No feeler connection is made when our tip is stale · Issue #15484 · bitcoin/bitcoin · GitHub
08:57 < achow101> Has anyone seen this issue with 0.17.1 on ubuntu 18.10 before: https://bitcoin.stackexchange.com/questions/84868/bitcoin-qt-testnet-0-17-1-send-and-receive-buttons-do-nothing?
08:57 < achow101> the debug.log file indicates that various signals aren't being connected
09:23 -!- led_zgrl [3a0ad034@gateway/web/freenode/ip.58.10.208.52] has joined #bitcoin-core-dev
09:27 -!- darosior [52ff9820@gateway/web/freenode/ip.82.255.152.32] has joined #bitcoin-core-dev
09:28 -!- promag [~promag@83.223.249.234] has joined #bitcoin-core-dev
09:28 -!- jarthur [~jarthur@207.114.244.5] has joined #bitcoin-core-dev
09:34 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Remote host closed the connection]
09:34 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-core-dev
09:34 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has quit [Changing host]
09:34 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
09:39 -!- led_zgrl [3a0ad034@gateway/web/freenode/ip.58.10.208.52] has quit [Ping timeout: 256 seconds]
09:39 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev
09:39 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 250 seconds]
09:57 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
10:00 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-core-dev
10:01 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has quit [Changing host]
10:01 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
10:05 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection]
10:07 -!- fabianfabian [~fabianfab@D9656CCE.cm-27.dynamic.ziggo.nl] has joined #bitcoin-core-dev
10:08 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev
10:09 -!- jungly [~quassel@79.8.200.97] has quit [Remote host closed the connection]
10:12 -!- darosior [52ff9820@gateway/web/freenode/ip.82.255.152.32] has quit [Ping timeout: 256 seconds]
10:15 -!- promag [~promag@83.223.249.234] has quit [Remote host closed the connection]
10:26 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
10:30 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 244 seconds]
10:41 -!- Aaronvan_ is now known as AaronvanW
10:52 -!- _Sam-- [greybits@gateway/vpn/privateinternetaccess/sam--/x-37783179] has joined #bitcoin-core-dev
11:03 < BlueMatt> is feature_assumevalid known to be failing on travis?
11:03 < gmaxwell> BlueMatt: isn't failed on any other PRs than yours, AFAICT
11:04 < BlueMatt> weird...given I havent touched it and it passes locally :(
11:04 < sipa> have you tried turning it off and on again?
11:04 < sipa> (restarting travis)
11:04 < BlueMatt> I have...a few times :(
11:04 < gmaxwell> https://github.com/bitcoin/bitcoin/commit/b6f0db69a9c9cdf101371720351935121590d3aa#diff-42a25137995f0f513f6ee7653bc2c63e
11:05 < gmaxwell> apparently it's been flaking before.
11:05 < BlueMatt> recently, too
11:05  * gmaxwell grumbles about testing on cloud services.
11:05 < BlueMatt> fails on the same line, too
11:05 < gmaxwell> try again... :(
11:06 < BlueMatt> yea, I bumped the time limit, lets see if it fixes it
11:07 < gmaxwell> Unrelated, do we need to move off linuxfoundation lists?  AFAICT the mailing list has been dysfunctional for some time and now isn't working at all.
11:07 < BlueMatt> I am curious why that generated a failure, though, given it also fails on the pre-fork-changes commit which I dont see how it could possibly have a performance effect aside from running a different set of tests in parallell at the time
11:10 < jnewbery> what's the pre-fork-changes commit?
11:10 < gmaxwell> performance of travis executors seems to be extremely inconsistent. 
11:11 < BlueMatt> jnewbery: the commit that only changed the getblocktemplate/miner.cpp behavior
11:11 < BlueMatt> (and added a new test)
11:11 < BlueMatt> ie #15481
11:11 < gribble> https://github.com/bitcoin/bitcoin/issues/15481 | Restrict timestamp when mining a diff-adjustment block to prev-600 by TheBlueMatt · Pull Request #15481 · bitcoin/bitcoin · GitHub
11:13 < gmaxwell> kanzure: do you know whats up with the mailing list?
11:13 < sipa> admin interface is down, i heard
11:14 < BlueMatt> last I heard he said he'd "escalated" it
11:14 < BlueMatt> so....who knows
11:18 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev
11:20 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 246 seconds]
11:20 -!- so_ [~so@unaffiliated/so] has quit [Ping timeout: 246 seconds]
11:20 -!- spinza [~spin@155.93.246.187] has quit [Ping timeout: 255 seconds]
11:20 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Ping timeout: 255 seconds]
11:20 -!- so [~so@unaffiliated/so] has joined #bitcoin-core-dev
11:21 -!- promag_ [~promag@bl22-246-44.dsl.telepac.pt] has quit [Ping timeout: 255 seconds]
11:21 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev
11:21 < jnewbery> and it hasn't failed on master recently?
11:22 < luke-jr> gmaxwell: PM
11:25 -!- phwalkr [~phwalkr@192.32.61.94.rev.vodafone.pt] has quit [Remote host closed the connection]
11:25 < BlueMatt> jnewbery: what hasnt?
11:26 -!- phwalkr [~phwalkr@192.32.61.94.rev.vodafone.pt] has joined #bitcoin-core-dev
11:26 < BlueMatt> also, processnewblock_signals_ordering is busted on windows, but if I restart it it works again
11:26 < BlueMatt> soooo ummm...thats bad
11:29 < kanzure> gmaxwell: no, i don't know what's going on. it's just "internal server error" all the time.
11:29 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
11:29 < kanzure> gmaxwell: i escalated to warren, who knows the linux foundation people
11:31 -!- phwalkr [~phwalkr@192.32.61.94.rev.vodafone.pt] has quit [Ping timeout: 255 seconds]
11:33 < jnewbery> the test that's failing - feature_assumevalid.py ?
11:35 < jnewbery> ah, I think I see what's happening
11:36 < jnewbery> feature_assumevalid.py always takes a long time on travis. usually around 150 seconds
11:36 < jnewbery> for me locally, it runs in less than 10
11:36 < jnewbery> it must be taking a long time here:
11:36 < jnewbery>             p2p1.send_message(msg_block(self.blocks[i]))
11:36 < jnewbery> sorry, here:
11:36 < jnewbery>         for i in range(2202):
11:36 < jnewbery>             p2p1.send_message(msg_block(self.blocks[i]))
11:37 < jnewbery> which presumably is hitting storage in AcceptBlock()
11:37 < jnewbery> any disk activity is super slow in Travis
11:39 < jnewbery> I don't think there's any way to speed it up. The test is feeding a long chain of blocks to a node where one of the early blocks has an invalid signature, and checking that the chain is accepted when assumevalid is set
11:40 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev
11:41 < jnewbery> I can't see any reason your change would make a difference there, unless it just happens to be running a different test that has disk i/o in parallel
11:41 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds]
11:43 < jnewbery> Actually, I guess we don't need to feed it the full chain of blocks. As long as it accepts the invalid block (height 102), then it's testing the assumevalid behaviour
11:43 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
11:43 < bitcoin-git> [bitcoin] adamjonas opened pull request #15485: add rpc_misc.py, mv test getmemoryinfo, add test mallocinfo (master...test_rpc_misc) https://github.com/bitcoin/bitcoin/pull/15485
11:44 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
11:49 -!- elichai2 [uid212594@gateway/web/irccloud.com/x-tqempquacvnrwdnh] has quit [Quit: Connection closed for inactivity]
11:54 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Remote host closed the connection]
11:57 -!- jarthur_ [~jarthur@207.114.244.5] has joined #bitcoin-core-dev
12:01 -!- jarthur [~jarthur@207.114.244.5] has quit [Ping timeout: 246 seconds]
12:01 < BlueMatt> jnewyea, the new test *also* accepts like 2k blocks at once, so understandably it may interfere
12:01 < BlueMatt> it appears to have been fixed by further increasing the timeout
12:01 < BlueMatt> jnewbery: 
12:06 < jnewbery> Consider moving assumevalid.py and the new test to EXTENDED_SCRIPTS
12:06 < jnewbery> that way they wouldn't get run on Travis
12:06 < sipa> do the extended tests get run anywhere automatically?
12:06 < jnewbery> no :(
12:06 < sipa> could we enable then for travis master builds?
12:06 < jnewbery> Travis is too slow for any tests that hit disk too much
12:06 < sipa> (but not PRs?)
12:07 < sipa> could MarcoFalke's Drahtbot run then at some regular interval? I don't know what hardware it runs on
12:08 < jnewbery> Previously, a bunch more of the tests were EXTENDED, and they got moved to BASIC
12:08 < jnewbery> the EXTENDED tests were run nightly on a travis cron job, with the exception of pruning and dbcrash
12:09 < jnewbery> those were too slow to be run even nightly, because the travis job would time out
12:10 < gmaxwell> how long until we ship a serious bug that the extended tests would have caught?
12:10 < jnewbery> It would be nice to have a non-cloud CI
12:10 < jnewbery> I think a long time. Only pruning and dbcrash are extended tests now
12:11 < jnewbery> There are probably more critical paths that don't have any test coverage at all
12:11 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 250 seconds]
12:15 -!- ap4lmtree [ap4lmtree@unaffiliated/ap4lmtree] has quit [Remote host closed the connection]
12:15 -!- ap4lmtree [ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev
12:25 -!- ap4lmtree [ap4lmtree@unaffiliated/ap4lmtree] has quit [Read error: Connection reset by peer]
12:27 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev
12:28 -!- comboy_ [~quassel@tesuji.pl] has quit [Remote host closed the connection]
12:28 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Excess Flood]
12:28 -!- comboy [~quassel@tesuji.pl] has joined #bitcoin-core-dev
12:28 -!- wolfspraul [~wolfsprau@bobbin.q-ag.de] has quit [Remote host closed the connection]
12:28 -!- wolfspraul [~wolfsprau@bobbin.q-ag.de] has joined #bitcoin-core-dev
12:30 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
12:30 < bitcoin-git> [bitcoin] sdaftuar opened pull request #15486: [net] Allow feeler connections to go to the same netgroup as existing outbound peers (master...2019-02-addrman-collisions) https://github.com/bitcoin/bitcoin/pull/15486
12:30 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
12:30 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
12:31 < gmaxwell> sdaftuar: dud you see the report last night that feelers were stopping?
12:31 < gmaxwell> did
12:31 < gmaxwell> oh you are fixing it
12:31 < sdaftuar> :)
12:31 < gmaxwell> ohh nice
12:31 < gmaxwell> thats subtle
12:32 < BlueMatt> damn, sdaftuar is smart...
12:32 < gmaxwell> sorry I haven't looked this morning, been dealing with meatspace stuff.  but I probably wouldn't have figured that out anyways.
12:32 < sdaftuar> luckily the reporter's logging made this easier to find... our default logging doesn't provide the ip you're colliding with
12:34 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 250 seconds]
12:37 < gmaxwell> Your change seems reasonable but it also seems like a really indirect fix.
12:37 < sdaftuar> yeah i agree. i haven't quite wrapped my head around the addrman well enough to propose a fix there
12:38 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
12:38 < gmaxwell> I think the tried buffer should have a maximum size and random forgetting if it overfills.
12:38 < gmaxwell> I don't think addrman's behavior needs to change.
12:39 < sdaftuar> i think it does?  at least, from reading the original PR it seems to
12:39 < sdaftuar> the issue is that you might not have any new collisions for a long time
12:39 -!- jarthur_ [~jarthur@207.114.244.5] has quit [Remote host closed the connection]
12:39 < sdaftuar> so you have just one tried entry, which you have to try each time
12:39 < sdaftuar> one tried collision entry i mean
12:39 < sdaftuar> but then we fail because it's in the same netgroup
12:39 -!- jarthur [~jarthur@207.114.244.5] has joined #bitcoin-core-dev
12:39 < sdaftuar> so we could bail out differently i guess and pull from regular Select
12:40 < gmaxwell> making it unconditionally remove when it makes use of it would be sufficient
12:41 < sdaftuar> well, that's trickier to write i think -- i believe we use it asynchronously, so if we drained it there we'd need to put it somewhere else so that we could resolve the collision later the right way
12:42 < gmaxwell> I don't think it's critical that absolutely always retry an evicted try.
12:43 < gmaxwell> just so long as an attacker can't cause us to never try.
12:43 < sdaftuar> i actually don't recall why we do it this way in the first place... the concern is around an attacker getting us to remove things from the tried table that we shouldn't?
12:43 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 258 seconds]
12:43 < sdaftuar> don't we use some kind of salted hashing or something to make that hard to do?
12:45  * sdaftuar hopes ethan will pop in and fix this in some simple way
12:57 < gmaxwell> sdaftuar: kind of, basically it's just creating an anti-eviction bias. In simulation it helps a lot.
12:57 < gmaxwell> we resist the attacker flooding our table, but can't block it completely.
12:57 < gmaxwell> So we essentially give anything that was already in there a second chance.
12:58 < sdaftuar> oh, so if we looked at collisions as "if we're not sure the existing entry is bad, keep it" that's probably fine?
12:58 < gmaxwell> like: we want to evict old tried data in favor of new known to be working stuff... but only because the old tried data is old and may no longer be a working node. So the idea behind try before evict is to resolve that "we don't know".
12:59 < gmaxwell> If we knew an entry in tried was working we'd prefer to never evict it in favor of something new.
13:00 -!- booyah_ is now known as booyah
13:04 < sdaftuar> (from ethan, pasting from a slack channel at his request)
13:04 < sdaftuar> Ethan Heilman [3:57 PM]
13:04 < sdaftuar> We make the following assumption: The addresses in the tried table contain some non-malicious addresses because if they were all malicious controlled addresses the attack has already won and you would not learn about non-malicious addresses. Based on this assumption you don't want to evict an address from the tried table if that address is still up and connectable.
13:04 < sdaftuar> Ethan Heilman [3:57 PM]
13:04 < sdaftuar> So we never evict an address without trying it
13:04 < sdaftuar> exactly
13:04 < sdaftuar> Ethan Heilman [3:59 PM]
13:04 < sdaftuar> I haven't read it closely but PR #15486 seems like a reasonable fix at face value.
13:04 < gribble> https://github.com/bitcoin/bitcoin/issues/15486 | [net] Allow feeler connections to go to the same netgroup as existing outbound peers by sdaftuar · Pull Request #15486 · bitcoin/bitcoin · GitHub
13:04 < sdaftuar> The second role of feeler connections is testing addresses in new and adding them to tried
13:04 < sdaftuar> both of these purposes don't need to care about the group the address is from
13:05 -!- ethan_ [04100d4e@gateway/web/freenode/ip.4.16.13.78] has joined #bitcoin-core-dev
13:05 < gmaxwell> right but is the fix complete? I'm concerned that if there is a persistant issue with one of the addresses that we'll get stuck on it.
13:06 < gmaxwell> like, do we correctly count it as unreachable under all possibility failure conditions... clearly not currently.
13:06 < gmaxwell> An alternative to your fix would be counting the grouping failure as failed, that would be dumb because feelers shouldn't be obeying the network group rule regardless.. but it would also be a fix.
13:07 < ethan_> We can enumerate the ways we believe it can fail and then cover all those cases or mark it with a number of attempts uint and if that number is greater than 3 remove it
13:08 < gmaxwell> My thought was just anytime we attempt to try we should remove it from the list.  Maybe this means some spurrious removals will happen, but I don't think that matters.
13:09 < gmaxwell> like if 1:50 try before evicts didn't really try but evicted anyways, ... so what?
13:09 < gmaxwell> network connections fail by chance sometimes too.
13:09 < sdaftuar> my thought was that if something has been in the m_tried_collisions for too long, we just remove it?
13:10 -!- ap4lmtree [ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev
13:10 < sdaftuar> basically add one extra condition in ResolveCollisions() where after 20 minutes or something we give up on an eviction attempt. 
13:10 < ethan_> that seems reasonable
13:10 < sdaftuar> or do the eviction anyway, not sure which way makes more sense
13:10 -!- promag_ [~promag@83.223.249.234] has joined #bitcoin-core-dev
13:11 -!- promag__ [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev
13:13 < ethan_> you should evict if you are failing to connect or resolve the goodness of the to-be-evicted address
13:14 < ethan_> if you can't test an IP and the reason isn't because of its group, then you aren't going to be able to connect to the IP anyway and it should be evicted
13:14 < sdaftuar> that's a good point
13:15 -!- promag_ [~promag@83.223.249.234] has quit [Ping timeout: 240 seconds]
13:22 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
13:28 -!- mmgen [~mmgen@gateway/tor-sasl/mmgen] has quit [Quit: (https://github.com/mmgen) leaving]
13:34 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
13:34 < bitcoin-git> [bitcoin] Sjors opened pull request #15487: [WIP] descriptor based wallet  (master...2019/02/descriptor-wallet) https://github.com/bitcoin/bitcoin/pull/15487
13:34 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
13:34 -!- jarthur [~jarthur@207.114.244.5] has quit [Ping timeout: 257 seconds]
13:36 < sdaftuar> ethan_: gmaxwell: i updated #15486 with a timeout in ResolveCollisions
13:36 < gribble> https://github.com/bitcoin/bitcoin/issues/15486 | [net] Allow feeler connections to go to the same netgroup as existing outbound peers by sdaftuar · Pull Request #15486 · bitcoin/bitcoin · GitHub
13:37 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
13:37 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
13:50 -!- jarthur [~jarthur@23.228.172.92] has joined #bitcoin-core-dev
13:52 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
14:01 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
14:01 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #14775: net: 'break' should be 'continue' here? (master...patch-6) https://github.com/bitcoin/bitcoin/pull/14775
14:01 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
14:05 -!- jarthur [~jarthur@23.228.172.92] has quit [Remote host closed the connection]
14:06 -!- cryptapus_ is now known as cryptapus
14:11 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:20 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 250 seconds]
14:21 < MarcoFalke> So it is not recommended to post to the mailing list right now, because non-approved people can not post to it?
14:22 -!- parmado [4c67bfcf@gateway/web/freenode/ip.76.103.191.207] has joined #bitcoin-core-dev
14:24 < sipa> i think nobody is approved
14:25 < parmado> i came in as a guest, which is an option 
14:26 < luke-jr> parmado: the channel is intentionally open to the public; however, if you have questions about Bitcoin, #bitcoin is usually a better place to ask
14:26 < parmado> thanks. is spectating okay for the time being?
14:27 < sipa> of course!
14:27 < parmado> thanks.
14:28 < parmado> is the consensus here that bitcoin will dominate amongst electronic assets, or is there substantial disagreement on that?
14:28 < sipa> parmado: #bitcoin
14:29 -!- timothy [~tredaelli@redhat/timothy] has quit [Remote host closed the connection]
14:30 < gwillen> hmm, I just rebased a feature branch, and now loading my testnet wallet is warning me: “Warning: Error reading ! All keys read correctly, but transaction data or address book entries might be missing or incorrect.”
14:30 < gwillen> I added some debug prints, and I am seeing errors when loading an object of strType="keymeta", and I am seeing lots of them, and all of them are caught exceptions (meaning that strErr="" so nothing useful prints)
14:31 < gwillen> achow101: I think you touched this recently? Should I be worried either that I did something wrong, or that you did?
14:31 -!- darosior [~darosior@2a01:e35:2ff9:8200:9d71:5b1f:da8f:3768] has joined #bitcoin-core-dev
14:32 < gmaxwell> ethan_: the only kind of case where I think it might make sense to not always remove a connection from that list is when we're offline.
14:32 < gmaxwell> but we don't really know when we're offline in any case..
14:44 < gmaxwell> sdaftuar: you should probably add a reported by credit to the feelerfix, it's esp to do when the report was good enough to make fixing it easier/possible.
14:44 < sipa> credit?
14:44 < sipa> oh!
14:44 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev
14:44 < sipa> a "reported by" credit, not a reported "by credit"
14:44 < gmaxwell> indeed.
14:45 -!- promag__ [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection]
14:47 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
14:47 -!- fabianfabian [~fabianfab@D9656CCE.cm-27.dynamic.ziggo.nl] has quit [Quit: Textual IRC Client: www.textualapp.com]
14:50 -!- amiti [36afffb0@gateway/web/freenode/ip.54.175.255.176] has joined #bitcoin-core-dev
14:52 -!- amiti [36afffb0@gateway/web/freenode/ip.54.175.255.176] has quit [Client Quit]
14:54 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
14:55 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Remote host closed the connection]
14:55 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
14:55 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
14:56 -!- jarthur [~jarthur@2605:6000:1019:41ab:8d5:e6a3:9e59:f818] has joined #bitcoin-core-dev
14:57 -!- Guest60674 [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-core-dev
15:01 -!- Guest60674 [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has quit [Ping timeout: 250 seconds]
15:13 -!- darosior [~darosior@2a01:e35:2ff9:8200:9d71:5b1f:da8f:3768] has quit [Remote host closed the connection]
15:16 -!- parmado [4c67bfcf@gateway/web/freenode/ip.76.103.191.207] has quit [Ping timeout: 256 seconds]
15:18 -!- promag_ [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev
15:31 < promag_> sipa: with #15402 it's possible to have concurrent invalidateblock right?
15:31 < gribble> https://github.com/bitcoin/bitcoin/issues/15402 | Granular invalidateblock and RewindBlockIndex by sipa · Pull Request #15402 · bitcoin/bitcoin · GitHub
16:01 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
16:01 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #15489: doc: Update release process for snap package (master...1902-docSnap) https://github.com/bitcoin/bitcoin/pull/15489
16:01 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
16:03 < sipa> promag_: i think so
16:04 < promag_> sipa: could that cause problems?
16:04 < sipa> we should try that, but i don't think so
16:05 < promag_> in a way both work for each other by calling DisconnectTip
16:06 -!- rh0nj [~rh0nj@88.99.167.175] has joined #bitcoin-core-dev
16:06 < sipa> right, they'll at best just take turns in calling DisconnectTip
16:06 < promag_> eventually the higher invalidation quits first
16:07 < promag_> not sure about the code after that loop
16:07 < promag_> InvalidChainFound and NotifyBlockTip
16:08 < sipa> shouldn't hurt to call either of those twice
16:08 < sipa> (i say should; it's a good point that we should test this)
16:09 < promag_> maybe by adding some sleeps between iterations?
16:09 < promag_> we could disallow concurrent invalidateblock
16:10 < gwillen> achow101: okay after investigating I think the most likely cause is that I ran some prior version of your PR before it was merged, and fucked up my wallet, so nevermind
16:10 < sipa> gwillen: #15427 may be of interest to you
16:10 < gribble> https://github.com/bitcoin/bitcoin/issues/15427 | Add support for descriptors to utxoupdatepsbt by sipa · Pull Request #15427 · bitcoin/bitcoin · GitHub
16:11 < gwillen> (my CKeyMetadata entries have the KeyOriginInfo, but they are missing the has_key_origin bool afterwards. I can't imagine any likely way that could have happened other than "I ran a version of the code that didn't have that yet"
16:11 < gwillen> sipa: this is indeed of interest to me, thanks -- I had made a note to look at it, but not gotten around to doing so
16:21 -!- promag_ [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection]
16:27 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Ping timeout: 256 seconds]
16:29 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-core-dev
16:34 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
16:35 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
17:29 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has quit [Remote host closed the connection]
17:29 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has joined #bitcoin-core-dev
17:30 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev
17:34 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has quit [Ping timeout: 257 seconds]
17:40 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 250 seconds]
17:43 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
17:47 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
17:47 < bitcoin-git> [bitcoin] iamgru opened pull request #15490: Update copyright headers to 2019 (master...master) https://github.com/bitcoin/bitcoin/pull/15490
17:48 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
17:59 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
17:59 < bitcoin-git> [bitcoin] fanquake closed pull request #15490: Update copyright headers to 2019 (master...master) https://github.com/bitcoin/bitcoin/pull/15490
17:59 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
18:01 -!- jarthur [~jarthur@2605:6000:1019:41ab:8d5:e6a3:9e59:f818] has quit [Remote host closed the connection]
18:01 -!- jarthur [~jarthur@2605:6000:1019:41ab:8d5:e6a3:9e59:f818] has joined #bitcoin-core-dev
18:14 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.2]
18:14 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
18:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
18:27 < bitcoin-git> [bitcoin] gwillen opened pull request #15491: wallet: Improve log output for errors during load (master...feature-improve-wallet-load-debug-output) https://github.com/bitcoin/bitcoin/pull/15491
18:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
18:27 -!- booyah [~bb@193.25.1.157] has quit [Excess Flood]
18:29 -!- booyah [~bb@193.25.1.157] has joined #bitcoin-core-dev
18:30 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev
18:52 -!- Muoi [8984d489@gateway/web/freenode/ip.137.132.212.137] has quit [Quit: Page closed]
19:06 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit []
19:12 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.2]
19:13 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit []
19:13 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
20:04 -!- Guest7635 [~MrPaz@84.39.112.85] has quit [Ping timeout: 250 seconds]
20:08 -!- MrPaz [~MrPaz@c-71-57-73-68.hsd1.il.comcast.net] has joined #bitcoin-core-dev
20:14 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
20:32 -!- ethan_ [04100d4e@gateway/web/freenode/ip.4.16.13.78] has quit [Ping timeout: 256 seconds]
20:52 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz]
20:54 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
21:00 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
21:09 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
21:12 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection]
21:34 -!- abc [8f598124@gateway/web/freenode/ip.143.89.129.36] has joined #bitcoin-core-dev
21:34 < abc> help
21:34 < abc> ls
21:34 < abc> HELP
21:34 < abc> --HELP
21:34 -!- abc [8f598124@gateway/web/freenode/ip.143.89.129.36] has quit [Client Quit]
21:35 -!- BB_ [8f598124@gateway/web/freenode/ip.143.89.129.36] has joined #bitcoin-core-dev
21:35 -!- BB_ [8f598124@gateway/web/freenode/ip.143.89.129.36] has quit [Client Quit]
21:58 -!- droark [~droark@c-24-21-203-195.hsd1.or.comcast.net] has quit [Ping timeout: 246 seconds]
22:26 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz]
22:30 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
22:38 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Ping timeout: 257 seconds]
22:39 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
22:48 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
22:48 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev
23:20 -!- jarthur [~jarthur@2605:6000:1019:41ab:8d5:e6a3:9e59:f818] has quit []
23:29 -!- promag_ [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev
23:30 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz]
23:35 -!- promag_ [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection]
23:53 < provoostenator> gwillen: #15424 can help you get rid of these messages, though we should make sure nobody who didn't use any intermediate achow101 branches does not see this message. 
23:53 < gribble> https://github.com/bitcoin/bitcoin/issues/15424 | [wallet] wallet-tool: command to remove key metadata by Sjors · Pull Request #15424 · bitcoin/bitcoin · GitHub
--- Log closed Wed Feb 27 00:00:01 2019