--- Log opened Thu Oct 01 00:00:34 2020
00:05 < promag> MarcoFalke: please see #20017
00:05 < gribble> https://github.com/bitcoin/bitcoin/issues/20017 | rpc: Add RPCContext by promag · Pull Request #20017 · bitcoin/bitcoin · GitHub
00:11 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
00:12 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
00:15 -!- S3RK [~s3rk@47.246.66.116] has joined #bitcoin-core-dev
00:18 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
00:18 < bitcoin-git> [bitcoin] kallewoof closed pull request #20045: upstream: add and use defaulted getters to UniValue (master...202009-defaulted-get) https://github.com/bitcoin/bitcoin/pull/20045
00:18 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
00:21 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
00:21 < bitcoin-git> [bitcoin] fanquake closed pull request #19785: build: lrelease requires xml if not cross-building (master...200823-xml) https://github.com/bitcoin/bitcoin/pull/19785
00:21 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
00:24 -!- jaybny [~jaybny@c-73-162-160-252.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
00:25 -!- cloudhead [~cloudhead@li1811-8.members.linode.com] has quit [Quit: WeeChat 2.8]
00:26 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 258 seconds]
00:29 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:fd40:903:a94:8ea1] has quit [Ping timeout: 272 seconds]
00:44 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
00:44 < bitcoin-git> [bitcoin] MarcoFalke pushed 8 commits to master: https://github.com/bitcoin/bitcoin/compare/3487e421a7fe...40aab35e9828
00:44 < bitcoin-git> bitcoin/master e455713 John Newbery: [tests] Move bech32 unit tests to test framework
00:44 < bitcoin-git> bitcoin/master 011e784 John Newbery: [tests] Rename segwit encode and decode functions
00:45 < bitcoin-git> bitcoin/master 7f639df John Newbery: [tests] Remove unused optional verify_checksum parameter
00:45 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
00:45 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
00:45 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #19253: Tests: tidy up address.py and segwit_addr.py (master...2020-06-addr-unit-tests) https://github.com/bitcoin/bitcoin/pull/19253
00:45 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
00:46 -!- jonatack [~jon@37.164.132.126] has joined #bitcoin-core-dev
00:47 -!- promag_ [~promag@188.251.225.32] has joined #bitcoin-core-dev
00:52 -!- Lightsword [~Lightswor@107.170.253.193] has quit [Quit: ZNC]
00:53 -!- Lightsword [~Lightswor@107.170.253.193] has joined #bitcoin-core-dev
00:55 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Ping timeout: 240 seconds]
00:56 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
00:56 -!- JD2983 [~jarret@S01069050cacf3d53.ed.shawcable.net] has quit [Remote host closed the connection]
00:56 -!- JD2983_ [~jarret@S01069050cacf3d53.ed.shawcable.net] has joined #bitcoin-core-dev
00:56 < vasild> jonatack: https://github.com/bitcoin/bitcoin/pull/19954#pullrequestreview-499530501 "Should we test for both msg_addr and msg_addrv2?"
00:57 < vasild> Right! Good question :)
00:58 < vasild> I was thinking that it is possible to change the py testing framework to always announce support for addrv2 which would flip all tests to use addrv2 but then addr will be untested... hmm
01:03 < wumpus> tryphe: oh no, if so it's just a new symptom of the old 'we hang the UI event loop on everything' problem
01:06 < wumpus> in any case I don't remember the windows shutdown detection code changing recently
01:07 -!- ahmed_ [sid14086@gateway/web/irccloud.com/x-ukufcanwmvrttcrt] has joined #bitcoin-core-dev
01:07 -!- felixweis [sid154231@gateway/web/irccloud.com/x-krefugjevbfmhthz] has joined #bitcoin-core-dev
01:07 -!- fjahr [sid374480@gateway/web/irccloud.com/x-rbbwbtbigjvdlmkh] has joined #bitcoin-core-dev
01:07 < wumpus> but it would be good if anyone that runs windows could check this
01:09 -!- promag_ [~promag@188.251.225.32] has quit [Remote host closed the connection]
01:09 < jonatack> vasild: indeed, i wondered how much extra effort it would be to test both and started doing it, then stopped before the rabbit hole "nah...i'll ask the question" ;)
01:10 < vasild> git grep msg_addr ./test/functional/
01:11 < wumpus> not seeing anything that could break the shutdown monitor in the git log for winshutdownmonitor.cpp, the last change of any significance was removing OpenSSL seeding in 2019, which jus removes an if() statement, before that it effectively wasn't teouched since the file was first introduced 
01:11 < fanquake> wumpus: I did try this morning and from what I remember I didn't see a shutdown window
01:11 < fanquake> Will test again
01:11 < vasild> jonatack: p2p_addr_relay.py is the only test that uses msg_addr!?
01:11 < wumpus> fanquake: okay, worrying then :/
01:12 < jonatack> vasild: seems so
01:13 < vasild> jonatack: I assumed there were many others that would keep testing msg_addr when p2p_addr_relay.py is converted to use msg_addrv2, but if that test is the only one testing msg_addr, then we better not stop it
01:14 < jonatack> yes, initially it didn't seem to be too much extra effort to test both
01:14 < wumpus> the only thing I can think of, besides Windows deprecating this way of detecting shutdown, is that it might be one of the Qt updates breaking how native event filters work?
01:15 -!- marcoagner [~user@bl11-17-219.dsl.telepac.pt] has quit [Ping timeout: 272 seconds]
01:15 < wumpus> I honestly don't know though I'd expect much more complaints if this really doesn't work anymore
01:18 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev
01:31 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
01:32 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has quit [Read error: Connection reset by peer]
01:33 -!- promag_ [~promag@188.251.225.32] has joined #bitcoin-core-dev
01:34 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has joined #bitcoin-core-dev
01:37 -!- promag_ [~promag@188.251.225.32] has quit [Remote host closed the connection]
01:38 -!- promag_ [~promag@188.251.225.32] has joined #bitcoin-core-dev
01:38 < jnewbery> #proposedmeetingtopic merging PR 19953 (taproot)
01:39 -!- promag_ [~promag@188.251.225.32] has quit [Remote host closed the connection]
01:40 < vasild> MarcoFalke: why those builds on 18750? https://github.com/bitcoin/bitcoin/pull/18750#event-3822788532
01:41 < vasild> to test that compilation works on more platforms than CI?
01:43 -!- promag__ [~promag@188.251.225.32] has joined #bitcoin-core-dev
01:44 < vasild> btw, guix_build.log for master is 35M while for master+PR 3.4MB
01:51 -!- S3RK [~s3rk@47.246.66.116] has quit [Remote host closed the connection]
01:52 -!- Netsplit *.net <-> *.split quits: fjahr, promag__, felixweis, ahmed_
01:55 -!- nckx [~nckx@tobias.gr] has quit [Ping timeout: 264 seconds]
01:55 -!- nckx [~nckx@tobias.gr] has joined #bitcoin-core-dev
02:00 -!- Alphi [~Alphi@193.56.252.210] has quit []
02:10 -!- Netsplit over, joins: felixweis, fjahr, promag__, ahmed_
02:11 -!- promag__ [~promag@188.251.225.32] has quit [Remote host closed the connection]
02:11 -!- promag_ [~promag@188.251.225.32] has joined #bitcoin-core-dev
02:22 -!- kini1 [~kini@s91904426.blix.com] has joined #bitcoin-core-dev
02:29 < fanquake> wumpus: I tried again, and didn't see a shutdown dialog, but that's also might be because Windows threw up another shutting down overlay, which might have hid it.
02:30 -!- S3RK [~s3rk@47.246.66.116] has joined #bitcoin-core-dev
02:31 < wumpus> fanquake: maybe a test like would be useful: add a sleep during shutdown to make sure it's slow, then shut down windows, afterwards check the log if it got to the end or was interrupted 
02:31 < wumpus> also maybe check for the message (if we log any) that the shutdown request came in
02:32 < wumpus> after all, the issue here would be not so much not seeing the shutdown window but that it shuts down unclean
02:32 < fanquake> wumpus: I'll take a look at it tonight
02:33 < wumpus> thanks!
02:34 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds]
02:34 < wumpus> (looking at the code: no we don't log any specific message if WM_QUERYENDSESSION comes in, nor on registering the shutdown handler itself, though it does log if it fails for some erason)
02:35 -!- promag_ [~promag@188.251.225.32] has quit [Remote host closed the connection]
02:37 < wumpus> it might make sense to add those things to make troubleshooting easier
02:42 -!- S3RK [~s3rk@47.246.66.116] has quit [Ping timeout: 260 seconds]
02:43 -!- isis_ [~isis@abulafia.patternsinthevoid.net] has quit [Ping timeout: 240 seconds]
02:43 -!- isis_ [~isis@abulafia.patternsinthevoid.net] has joined #bitcoin-core-dev
02:49 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:f96a:addc:bd41:b4a1] has joined #bitcoin-core-dev
02:55 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
02:55 -!- S3RK [~s3rk@47.246.66.116] has joined #bitcoin-core-dev
02:59 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
03:00 -!- Aaronva__ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
03:02 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds]
03:03 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds]
03:04 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 240 seconds]
03:05 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #bitcoin-core-dev
03:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
03:15 -!- jonatack [~jon@37.164.132.126] has quit [Ping timeout: 260 seconds]
03:17 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev
03:18 -!- Mortimer82Collie [~Mortimer8@static.57.1.216.95.clients.your-server.de] has joined #bitcoin-core-dev
03:20 < kallewoof> i get a bunch of errors about inline asm when i try -fsanitize=address on a mac. is that normal?
03:22 -!- wullon587 [~wullon@241.243.86.88.rdns.comcable.net] has quit [Ping timeout: 265 seconds]
03:23 -!- Mortimer82Collie [~Mortimer8@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 265 seconds]
03:23 -!- braydonf [~braydon@gateway/tor-sasl/braydonf] has quit [Ping timeout: 240 seconds]
03:33 -!- jaybny [~jaybny@c-73-162-160-252.hsd1.ca.comcast.net] has quit [Quit: jaybny]
03:36 -!- Asbestos_Vapor [~Mercury_V@174-082-166-092.res.spectrum.com] has quit [Read error: Connection reset by peer]
03:36 -!- Asbestos_Vapor [~Mercury_V@174-082-166-092.res.spectrum.com] has joined #bitcoin-core-dev
03:37 -!- braydonf [~braydon@gateway/tor-sasl/braydonf] has joined #bitcoin-core-dev
03:38 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:f96a:addc:bd41:b4a1] has quit [Remote host closed the connection]
03:45 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:4ec:f8ec:7c04:d312] has joined #bitcoin-core-dev
03:50 -!- pingwindyktator [~pingwindy@pingwindyktator.me] has quit [Ping timeout: 240 seconds]
03:51 -!- S3RK [~s3rk@47.246.66.116] has quit [Remote host closed the connection]
03:51 -!- pingwindyktator [~pingwindy@pingwindyktator.me] has joined #bitcoin-core-dev
03:51 -!- S3RK [~s3rk@47.246.66.116] has joined #bitcoin-core-dev
03:53 -!- S3RK [~s3rk@47.246.66.116] has quit [Remote host closed the connection]
03:53 -!- S3RK [~s3rk@47.246.66.116] has joined #bitcoin-core-dev
03:56 -!- Tennis [~Tennis@unaffiliated/tennis] has joined #bitcoin-core-dev
04:18 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
04:19 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
04:20 -!- S3RK [~s3rk@47.246.66.116] has quit [Remote host closed the connection]
04:20 -!- S3RK [~s3rk@47.246.66.116] has joined #bitcoin-core-dev
04:24 -!- S3RK [~s3rk@47.246.66.116] has quit [Ping timeout: 246 seconds]
04:31 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
04:31 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/40aab35e9828...9fc2f011ba17
04:31 < bitcoin-git> bitcoin/master 6fccad7 Jon Atack: signet: do not log signet startup messages for other chains
04:31 < bitcoin-git> bitcoin/master 9fc2f01 MarcoFalke: Merge #20048: chainparams: do not log signet startup messages for other ch...
04:31 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
04:31 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
04:31 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #20048: chainparams: do not log signet startup messages for other chains (master...signet-startup-logging-bugfix) https://github.com/bitcoin/bitcoin/pull/20048
04:31 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
04:48 -!- gleb [~gleb@178.150.137.228] has quit [Ping timeout: 258 seconds]
04:50 -!- gleb [~gleb@178.150.137.228] has joined #bitcoin-core-dev
04:57 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:4ec:f8ec:7c04:d312] has quit [Remote host closed the connection]
04:57 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
04:58 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
05:00 -!- kini1 [~kini@s91904426.blix.com] has quit []
05:00 -!- S3RK [~s3rk@47.246.66.116] has joined #bitcoin-core-dev
05:02 < MarcoFalke> vasild: The builds are just to confirm our guix/gitian build doesn't break. I ask DrahtBot to do those on "risky" build system changes
05:04 -!- S3RK [~s3rk@47.246.66.116] has quit [Ping timeout: 256 seconds]
05:06 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:65d4:b4f4:ba4f:1583] has joined #bitcoin-core-dev
05:21 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #bitcoin-core-dev
05:22 -!- kro[au] [~kroau]@195.206.169.184] has joined #bitcoin-core-dev
05:37 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-core-dev
05:39 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 260 seconds]
05:59 < vasild> MarcoFalke: ok, did it break? (it is not obvious to me from the logs, but I think not)
05:59 < MarcoFalke> no, it didn't break ;)
06:00 < vasild> do you think that it makes sense to do one test run with the new option enabled? because by default it is disabled which means no change in behavior
06:00 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #bitcoin-core-dev
06:19 -!- Aaronva__ is now known as AaronvanW
06:28 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:65d4:b4f4:ba4f:1583] has quit [Remote host closed the connection]
06:32 < aj> sipa: hmm. every single binary in src/test/fuzz is ~185MB for me (following the instructions in doc/fuzzzing.md). 117MB stripped, by the looks. total of 18G for src/test/fuzz, 22G for src
06:34 < wumpus> aj: that's large even for a static build
06:34 < aj> wumpus: hmm, bitcoind is 83M unstripped, 16M stripped for me
06:35 < aj> ./configure CC=clang CXX=clang++ --with-incompatible-bdb --enable-zmq --enable-debug --enable-werror --enable-fuzz --with-sanitizers=address,fuzzer,undefined
06:35 < wumpus> aj: for comparision, stripped x86_64 bitcoind 0.20.1 from the release is 10M
06:36 < wumpus> bitcoin-qt is 31MB, for reference, that includes a large part of whopping qt statically
06:36 < wumpus> I'm not sure what's happening in your case but it's fairly weird
06:37 < aj> wumpus: bitcoind with same options but not zmq or fuzz or sanitizers is 8MB stripped for me
06:37 < aj> (134M unstripped)
06:38 < wumpus> ohh, yes it's not unreasonable that the sanitizers that add extra code size 
06:38 < aj> wumpus: debian testing, clang 9 apparently
06:38 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:1551:90c4:977e:f40d] has joined #bitcoin-core-dev
06:38 < wumpus> zmq or not should hardly make a difference
06:39 < aj> yeah, just happened to have the non-zmq binary and config options handy
06:39 < aj> maybe fuzzing.md shouldn't recommend with-sanitizers in its quickstart section then?
06:40 < wumpus> I suppose it does make the fuzzing more effective, which might be considered worth the extra harddisk usage
06:43 < aj> oh well, i guess now i've got more disk space free it doesn't matter to me?
06:54 -!- filchef [~filchef@212.104.97.177] has joined #bitcoin-core-dev
07:01 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
07:01 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #bitcoin-core-dev
07:07 -!- S3RK [~s3rk@47.246.66.116] has joined #bitcoin-core-dev
07:12 -!- S3RK [~s3rk@47.246.66.116] has quit [Ping timeout: 272 seconds]
07:22 -!- IGHOR [~quassel@176.121.4.135] has quit [Ping timeout: 256 seconds]
07:25 < hebasto> https://github.com/bitcoin/bips/pull/967 is merged
07:27 < vasild> \o/
07:30 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:1551:90c4:977e:f40d] has quit [Ping timeout: 272 seconds]
07:32 -!- opsec_x12 [~opsec_x12@44-25-143-49.ip.hamwan.net] has quit [Read error: Connection reset by peer]
07:33 -!- opsec_x12 [~opsec_x12@44-25-143-49.ip.hamwan.net] has joined #bitcoin-core-dev
07:34 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:1551:90c4:977e:f40d] has joined #bitcoin-core-dev
07:36 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:1551:90c4:977e:f40d] has quit [Remote host closed the connection]
07:36 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:1551:90c4:977e:f40d] has joined #bitcoin-core-dev
07:36 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection]
07:41 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:1551:90c4:977e:f40d] has quit [Ping timeout: 260 seconds]
07:42 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #bitcoin-core-dev
07:43 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:684e:e96a:d9b3:e473] has joined #bitcoin-core-dev
07:44 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
07:44 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #20054: Remove confusing and useless "unexpected version" warning (master...2010-valRemVerWarn) https://github.com/bitcoin/bitcoin/pull/20054
07:44 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
07:50 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:684e:e96a:d9b3:e473] has quit [Remote host closed the connection]
07:52 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
07:52 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
08:00 -!- kro[au] [~kroau]@195.206.169.184] has quit []
08:07 -!- nthumann [5bf99b42@leasedline-static-091-249-155-066.ewe-ip-backbone.de] has joined #bitcoin-core-dev
08:13 < nthumann> Hey there! I´m looking for some feedback/tests of my PR #18309, so feel free to leave a comment, if you have some spare time :)  
08:13 < gribble> https://github.com/bitcoin/bitcoin/issues/18309 | zmq: Add support to listen on multiple interfaces by n-thumann · Pull Request #18309 · bitcoin/bitcoin · GitHub
08:22 -!- Alucard [~Alucard@185.163.110.116] has joined #bitcoin-core-dev
08:30 < luke-jr> nthumann: looks simple and good to me
08:31 -!- kexkey [~kexkey@89.36.78.198] has joined #bitcoin-core-dev
08:34 < nthumann> luke-jr thanks :)
08:36 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
08:36 < bitcoin-git> [bitcoin] laanwj opened pull request #20055: rpc: Set HTTP Content-Type in bitcoin-cli (master...2020_10_cli_contenttype) https://github.com/bitcoin/bitcoin/pull/20055
08:36 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
08:38 < wumpus> nthumann: looks good to me and has a test
08:40 < wumpus> I also see no reason why this would *not* be allowed
08:43 < instagibbs> nthumann, bugging on IRC works! ;P
08:43 < instagibbs> RFM imo
08:44 -!- opsec_x12 [~opsec_x12@44-25-143-49.ip.hamwan.net] has quit [Read error: Connection reset by peer]
08:44 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
08:44 < bitcoin-git> [bitcoin] laanwj pushed 6 commits to master: https://github.com/bitcoin/bitcoin/compare/9fc2f011ba17...a0185d90a7f2
08:44 < bitcoin-git> bitcoin/master 347c94f Nicolas Thumann: zmq: Add support to listen on multiple interfaces
08:44 < bitcoin-git> bitcoin/master b1c3f18 nthumann: doc: Adjust ZMQ usage to support multiple interfaces
08:44 < bitcoin-git> bitcoin/master a0b2e5c nthumann: doc: Add release notes to support multiple interfaces
08:44 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
08:44 -!- opsec_x12 [~opsec_x12@44-25-143-49.ip.hamwan.net] has joined #bitcoin-core-dev
08:45 < luke-jr> lol
08:45 < instagibbs> I forgot how simple it was, would have re-acked earlier
08:45 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
08:45 < bitcoin-git> [bitcoin] laanwj merged pull request #18309: zmq: Add support to listen on multiple interfaces (master...zmq-listen-multiple-interfaces) https://github.com/bitcoin/bitcoin/pull/18309
08:45 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
08:46 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev
08:47 < instagibbs> I was harassing nthumann on email to re-review my zmq PR :P 
08:48 -!- opsec_x12 [~opsec_x12@44-25-143-49.ip.hamwan.net] has quit [Read error: Connection reset by peer]
08:48 -!- opsec_x12 [~opsec_x12@44-25-143-49.ip.hamwan.net] has joined #bitcoin-core-dev
08:50 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
08:51 < wumpus> yes, bugging on IRC works
08:51 < luke-jr> for simple stuff anyway
08:52 < nthumann> instagibbs don´t worry about it :D  
08:55 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
08:58 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
08:58 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #20056: net: Use Span in ReceiveMsgBytes (master...2010-netSpan) https://github.com/bitcoin/bitcoin/pull/20056
08:58 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
09:04 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #bitcoin-core-dev
09:04 < wumpus> luke-jr: or in any case, almost-ready PRs
09:06 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack]
09:09 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
09:10 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
09:14 -!- nthumann [5bf99b42@leasedline-static-091-249-155-066.ewe-ip-backbone.de] has quit [Remote host closed the connection]
09:15 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #bitcoin-core-dev
09:21 -!- promag_ [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
09:21 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Read error: Connection reset by peer]
09:23 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
09:26 < achow101> is the arm travis failure a thing now or am I doing somethign wrong?
09:27 -!- roconnor [~roconnor@host-104-157-196-197.dyn.295.ca] has quit [Ping timeout: 260 seconds]
09:29 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
09:29 -!- promag_ [~promag@bl19-22-20.dsl.telepac.pt] has quit [Read error: Connection reset by peer]
09:29 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
09:30 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
09:32 < wumpus> oh no... what now?
09:32 < wumpus> the same one that jnewbery reported yesterday?
09:33 < achow101> yes
09:33 < achow101> showing up on most (all?) of my PRs
09:34 < wumpus> okay
09:35 < wumpus> it seems to have passed on the PR I just opened
09:35 < achow101> it passed on one of the prs I updated yesterday, but not the others
09:38 < achow101> it seems to just be timing out. the log isn't terribly helpful, just a bunch of dots
09:38 < achow101> e.g. https://travis-ci.org/github/bitcoin/bitcoin/jobs/723672782
09:39 < wumpus> yes the error is terribly unhelpful, it seems like simply a timeout
09:40 < wumpus> same as for previous reported ones, "Ran for 1 hr 4 min 38 sec" looks like there's a cutoff point there
09:40 < wumpus> restarted it
09:40 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #bitcoin-core-dev
09:41 < achow101> usually travis says something about timing out when it times out
09:44 < achow101> if there's a cutoff, it's not consistent. https://travis-ci.org/github/bitcoin/bitcoin/jobs/731742236 ran for 1 hr 17 min and passed
09:44 < sipa> there is a cutoff at 10 minutes of non-activity, but that's what the dots prevent
09:47 < achow101> and usually there's a message saying it timed out
09:54 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
09:54 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
09:56 -!- [\\\] [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev
09:58 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Ping timeout: 272 seconds]
10:15 < wumpus> right, there's no message at all of any exit status, it just stops
10:15 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
10:16 < wumpus> I have not seen any problems on ARM locally so I'm fairly sure this is a travis problem
10:16 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
10:17 < achow101> travis and random unexplainable issues, name a more iconic duo
10:18 < wumpus> heh
10:19 < sipa> haha
10:22 -!- S3RK [~s3rk@47.246.66.116] has joined #bitcoin-core-dev
10:27 -!- S3RK [~s3rk@47.246.66.116] has quit [Ping timeout: 256 seconds]
10:38 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
10:56 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
10:56 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
11:00 -!- Alucard [~Alucard@185.163.110.116] has quit []
11:00 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Read error: Connection reset by peer]
11:00 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
11:01 -!- Netsplit *.net <-> *.split quits: fjahr, felixweis, ahmed_
11:02 -!- watchtower [~watchtowe@ool-ad03fb1d.dyn.optonline.net] has joined #bitcoin-core-dev
11:05 -!- promag_ [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
11:05 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Read error: Connection reset by peer]
11:07 -!- watchtower [~watchtowe@ool-ad03fb1d.dyn.optonline.net] has left #bitcoin-core-dev []
11:08 -!- watchtower [~watchtowe@ool-ad03fb1d.dyn.optonline.net] has joined #bitcoin-core-dev
11:17 -!- watchtower [~watchtowe@ool-ad03fb1d.dyn.optonline.net] has left #bitcoin-core-dev []
11:18 -!- lordnoid1 [~lordnoid@178.239.168.171] has joined #bitcoin-core-dev
11:44 -!- sdaftuar [~sdaftuar@gateway/tor-sasl/sdaftuar] has quit [Remote host closed the connection]
11:45 -!- sdaftuar [~sdaftuar@gateway/tor-sasl/sdaftuar] has joined #bitcoin-core-dev
11:47 -!- Netsplit over, joins: felixweis, fjahr, ahmed_
11:50 -!- IGHOR [~quassel@176.121.4.135] has joined #bitcoin-core-dev
11:57 < aj> luke-jr: ping re bips PRs 978 and 1000
11:58 -!- promag_ [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
11:58 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
11:58 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:4447:9769:9f6a:6638] has joined #bitcoin-core-dev
12:00 < wumpus> #startmeeting
12:00 -!- sr_gi [~sr_gi@static-80-160-230-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer]
12:00 < lightningbot> Meeting started Thu Oct  1 19:00:21 2020 UTC.  The chair is wumpus. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:00 < lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
12:00 < promag> meeting?
12:00 < jnewbery> hi
12:00 < promag> oh, hi
12:00 < hebasto> hi
12:00 < amiti> hi
12:00 < aj> hi
12:00 < achow101> hi
12:00 < wumpus> #bitcoin-core-dev Meeting: wumpus sipa gmaxwell jonasschnelli morcos luke-jr sdaftuar jtimon cfields petertodd kanzure bluematt instagibbs phantomcircuit codeshark michagogo marcofalke paveljanik NicolasDorier jl2012 achow101 meshcollider jnewbery maaku fanquake promag provoostenator aj Chris_Stewart_5 dongcarl gwillen jamesob ken281221 ryanofsky gleb moneyball kvaciral ariard digi_james
12:00 < wumpus> amiti fjahr jeremyrubin lightlike emilengler jonatack hebasto jb55 elichai2
12:00 < ariard> hi
12:00 -!- sr_gi [~sr_gi@static-80-160-230-77.ipcom.comunitel.net] has joined #bitcoin-core-dev
12:00 < provoostenator> hi
12:01 < meshcollider> hi
12:01 < dongcarl> hi
12:01 < sipa> hi
12:01 < luke-jr> hi
12:01 < jonatack> kon'nichiwa
12:01 < wumpus> one proposed topic for today:  merging PR 19953 (taproot) (jnewbery)
12:02 < wumpus> any last minute suggestions?
12:03 < kanzure> hi
12:03 < wumpus> jonatack: こんにちは
12:03 < wumpus> #topic High priority for review
12:04 < wumpus> https://github.com/bitcoin/bitcoin/projects/8  12 blockers, 1 bugfix, 2 chasing concept ACK
12:04 < promag> please remove mine from hp, it doesn't help getting more reviews
12:05 < wumpus> ok
12:05 < wumpus> yes, anything concerning libevent initialization/shutdown is notoriously hard to review
12:06 < promag> basically it will wait for you ^^
12:07 < wumpus> well the PR seemed really tricky to me... I think what we need is a clear test, and then to test with different versions of libevent
12:07 < wumpus> I can't judge just from the code change wether it's better or not
12:07 < promag> ok, then I guess I need to make it clear and improve testing!
12:08 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!]
12:09 < wumpus> it's kind of awkward we've had a history of PRs like that, and it never really fixed the problem, we'll really want to make sure we get it right this time or it doesn't make sense to make another change there
12:09 < wumpus> thanks!
12:10 < wumpus> anything else for high prio?
12:10 < sipa> #19953 ? :)
12:10 < gribble> https://github.com/bitcoin/bitcoin/issues/19953 | Implement BIP 340-342 validation (Schnorr/taproot/tapscript) by sipa · Pull Request #19953 · bitcoin/bitcoin · GitHub
12:10 < sipa> oh, it is
12:10 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:4447:9769:9f6a:6638] has quit [Read error: Connection reset by peer]
12:10 < wumpus> hehe
12:11 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:4447:9769:9f6a:6638] has joined #bitcoin-core-dev
12:11 < wumpus> that's also the other topic
12:12 < wumpus> #topic Merging PR 19953 (taproot) (jnewbery)
12:12 < jnewbery> Hi!
12:12 < jnewbery> Apologies if eveyone else is already on the same page on this and I'm just not keeping up.
12:12 < jnewbery> What are people's hopes for when the Taproot PR gets merged?
12:12 < jnewbery> Feature freeze is in a couple of weeks, and it seems optimistic to get it merged before then.
12:12 < jnewbery> But if we want it included in v0.21.1, I think it makes sense to be merged very soon after the v0.21 branch, to make back-porting easier.
12:12 < jnewbery> So in my mind, it's the priority as soon as v0.21 gets branched, and before any big refactors (eg switching things to C++17) go in.
12:12 < jnewbery> Is that what other people are thinking too?
12:13 < jnewbery> (I'm personally prioritizing #19988 ahead of it for my reviews, because I think it'd be good to get that in 0.21)
12:13 < gribble> https://github.com/bitcoin/bitcoin/issues/19988 | Overhaul transaction request logic by sipa · Pull Request #19988 · bitcoin/bitcoin · GitHub
12:13 < luke-jr> jnewbery: before the branch?
12:13 < luke-jr> after the branch is too late, isn't it?
12:13 < sipa> i was hoping before the branch, but it's obviously not up to me
12:13 < sipa> i do think the PR is essentially done
12:13 < wumpus> yep, FWIW today was the translations freeze, feature freeze is in 14 days: https://github.com/bitcoin/bitcoin/issues/18947
12:14 < aj> i thought before the branch was still plausible; also prioritising 19988, but i think it's just about there
12:14 < promag> no backport after branch off right?
12:14 < luke-jr> promag: softforks should always be backported to anything supported
12:14 < luke-jr> not necessarily until activation is set tho
12:14 < wumpus> yes, softforks are always backported
12:15 < wumpus> but it would be good to get that in before the branch-off if it's ready anyway
12:15 < jnewbery> it currently has two ACKs (instagibbs and benthecarmen). Feels like now would be the time to review if anyone was waiting for the right moment!
12:15 < ariard> sounds good to prioritize 19988, I had the same PR order
12:15 < jonatack> agree. i was thinking the same as aj and sipa WRT these two PRs, 19953 and 19988
12:15 -!- andreacab [~andreacab@2a02:120b:2c22:e0c0:4447:9769:9f6a:6638] has quit [Ping timeout: 260 seconds]
12:16 < jonatack> (along with the tor v3 support)
12:16 < sipa> it seems silly to say "merge right after branch", if it's ready to merge at that point, it's also ready to merge before
12:16 < achow101> i'll move it to the top of my review queue
12:17 < wumpus> sipa: right, 'merge after branch' is for features that shouldn't be backported
12:17 < sipa> or for very invasive refactors perhaps
12:17 < wumpus> yes
12:17 < sipa> of course, if it isn't ready before, it isn't, and that should be that
12:18 < jnewbery> sipa: I meant "if it's not ready to merge at branch, then it should be a priority to get it reviewed/merged as soon as possible", not "don't merge it before the branch even if it's ready"
12:18 < sipa> jnewbery: right, that makes sense
12:19 < sipa> in any case, the outstanding things i have for 19953 at this point are a few review comments (which will just result in added code comments for clarification), and documenting the process of creating the JSON unit test data
12:19 < sipa> https://github.com/bitcoin-core/qa-assets/pull/27 FWIW
12:19 < wumpus> so just documentation work
12:19 < ariard> I still want to review in-depth the test coverage, but that said 14 days is largely enough
12:19 < wumpus> which is important but doesn't hold up the code merge
12:19 < sipa> and obviously addressing any review comments that may still arise
12:20 < jnewbery> I guess maybe the message should be: feature freeze is in two weeks, think about what your priorities are. Mine are 19988 and 19953.
12:21 < sipa> i'm committed to quickly addressing comments in both of those
12:21 < sipa> my other priority is torv3
12:21 < luke-jr> IMO #11082 is important to get into 0.21, but clearly I can't do it alone :/
12:21 < gribble> https://github.com/bitcoin/bitcoin/issues/11082 | Add new bitcoin_rw.conf file that is used for settings modified by this software itself by luke-jr · Pull Request #11082 · bitcoin/bitcoin · GitHub
12:21 < aj> wumpus: oh, i guess #19937 for high-pri might be nice
12:21 < gribble> https://github.com/bitcoin/bitcoin/issues/19937 | signet mining utility by ajtowns · Pull Request #19937 · bitcoin/bitcoin · GitHub
12:21 < wumpus> mine are, beside taproot, #19991 and #19954
12:21 < gribble> https://github.com/bitcoin/bitcoin/issues/19991 | net: Use alternative port for incoming Tor connections by hebasto · Pull Request #19991 · bitcoin/bitcoin · GitHub
12:22 < gribble> https://github.com/bitcoin/bitcoin/issues/19954 | tor: complete the TORv3 implementation by vasild · Pull Request #19954 · bitcoin/bitcoin · GitHub
12:22 < sipa> luke-jr: i haven't seen any argument as for what it adds over settings.json, so barring a wide agreement to revert that (and there doesn't seem to be), it seems hard to get people to find it important
12:23 < luke-jr> sipa: it potentially reduces us to 1 config format, whereas settings.json bumped us to 3 or 4
12:23 < wumpus> aj: added
12:23 < wumpus> sipa: I agree, that's why I haven't really looked at it either
12:23 < wumpus> I don'twant yet another config file, initialization and setting priority is complex enough as it is
12:24 < sipa> luke-jr: but settings.json is merged; you'll need a much stronger case if your goal is reverting that and merging bitcoin_rw instead
12:24 < luke-jr> wumpus: that's the point behind rwconf - it reduces
12:24 < sipa> as having both seems the worst of both worlds
12:24 < luke-jr> sipa: that's why it's important to do before 0.21
12:24 < luke-jr> once 0.21 is released, we're stuck with settings.json
12:24 < sipa> luke-jr: but your goal isn't just merging bitcoin_rw; it's replacing a feature that was already merged
12:24 < sipa> i have no opinion either way, but one is merged, and the other isn't
12:25 < wumpus> it's an internal settings file, people are not supposed to edit it manually, might be better if it's in json format instead
12:25 < wumpus> could have been some obscure binary format as well but as least this is readible if you want to...
12:25 < jnewbery> luke-jr: you failed to convince people that bitcoin_rw was the right approach in the PRs. I don't see what simply repeating your position here will achieve
12:26 < wumpus> any other topics?
12:27 < achow101> at what point do we switch to the milestone for hi prio?
12:27 < wumpus> achow101: well not yet as I've not really looked at what is at the milestone yet
12:28 < wumpus> but yes good point
12:30 < wumpus> we could do that starting from next week, after sorting things out, I think we need to postpone things like "sqlite wallet storage" to 0.22  https://github.com/bitcoin/bitcoin/milestone/45
12:30 < achow101> :(
12:30 < wumpus> as well as the guix build
12:30 < wumpus> yes, :(
12:30 < sipa> i'm sorry i haven't had the time to dive into that... i'd really like to see sqlite happen
12:30 < luke-jr> "the guix build"?
12:31 < wumpus> but that sounds scary to do last minute at least to me, seems like something that needs to brew in the master branch for a while
12:31  * dongcarl awakens
12:31 < wumpus> luke-jr: yes, 0.21 will be another release built with gitian it seems?
12:31 < luke-jr> wumpus: hopefully gitian won't be abandoned any time soon
12:32 < luke-jr> guix is an improvement over Ubuntu, but not over gitian
12:32 < achow101> the main thing was that I had wanted to couple sqlite with descriptor wallets just to avoid multiple upgrade scenarios
12:33 < sipa> achow101: i get that, but does that add that much? you'll still need to support legacy+bdb, legacy+sqlite, desc+sqlite anyway
12:33 < wumpus> achow101: yes, I understand … but it seems too recent to have as default yet
12:33 < luke-jr> Guix requires running third-party blobs to use (or at least, I couldn't get it running - and if I can't, how could we expect others to?)
12:33 < achow101> sipa: the idea was there wasn't a legacy+sqlite
12:33 < wumpus> luke-jr: my point was, that's a concern for 0.22 not 0.21
12:33 < luke-jr> k
12:34 < sipa> achow101: in the short term perhaps, but longer term i'd hope you can convert a legacy bdb wallet to sqlite so we could (in due time) have a reasonable build without bdb dependency
12:34 < wumpus> ^^
12:34 < sipa> while converting legacy to descriptor seems much harder/impossible
12:35 < achow101> converting legacy to descriptor seems possible
12:35 < wumpus> there needs to be a way to upgrade old wallets
12:35 < wumpus> if not, we'll be stuck with them forever
12:35 < achow101> #19602 does it
12:35 < gribble> https://github.com/bitcoin/bitcoin/issues/19602 | wallet: Migrate legacy wallets to descriptor wallets by achow101 · Pull Request #19602 · bitcoin/bitcoin · GitHub
12:36 < achow101> my plan was for the legacy -> desc upgrade is the bdb -> sqlite upgrade too
12:36 < luke-jr> we *could* disable descriptor wallets in 0.21, but I don't think anyone wants to go there..
12:36 < sipa> luke-jr: yeah, no
12:37 < wumpus> you can't really require people to transfer their funds to a new wallet to upgrade, ever
12:37 < sipa> achow101: i see, right, if you require a new backup at the same time, it does seem reasonaBLE
12:37 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Ping timeout: 240 seconds]
12:37 < wumpus> requiring a new backup is fine
12:38 < wumpus> just be clear about it
12:38 < achow101> wumpus: no funds transfer is required for the upgrade
12:39 < wumpus> achow101: good, that's the only hope we can get rid of berkeleydb at some point :)
12:39 < dongcarl> luke-jr: We can talk more about guix on #bitcoin-builds, would very much like to know the problems you ran into
12:39 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #bitcoin-core-dev
12:40 < luke-jr> dongcarl: k, after the meeting
12:40 < wumpus> (which I fully support, FWIW, though we'll want to be careful to somehow have some tools somewhere that people can use to convert old bdb wallets they find)
12:41 < wumpus> it highlights how important backwards compatibility is for our wallet formats anway
12:42 < wumpus> any other topics?
12:42 < sipa> 42 is a good minute to end at
12:42 < wumpus> #endmeeting
12:42 < lightningbot> Meeting ended Thu Oct  1 19:42:43 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
12:42 < lightningbot> Minutes:        http://www.erisian.com.au/meetbot/bitcoin-core-dev/2020/bitcoin-core-dev.2020-10-01-19.00.html
12:42 < lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/bitcoin-core-dev/2020/bitcoin-core-dev.2020-10-01-19.00.txt
12:42 < lightningbot> Log:            http://www.erisian.com.au/meetbot/bitcoin-core-dev/2020/bitcoin-core-dev.2020-10-01-19.00.log.html
12:42 < jonatack> :)
12:42 < jnewbery> thanks wumpus. Great meeting!
12:43 < aj> i guess 42:42 must be a doubleplus-good second to have neded at
12:43 < sipa> next time.
12:44 < aj> oh, it was right on 42:42 for me
12:44 < aj> maybe lightningbot's clock is wrong. i could edit the logs?
12:44 < sipa> did you know that the decimal sequence "424242" appears for the first time in byte position 242424 in the digits of Pi?
12:44 < achow101> I got it at 42:43. maybe your internet is just fater
12:45 < sipa> aj: irc doesn't guarantee bounded time delivery (iirc it doesn't even guarantee that messages won't be reordered, in multi-server setups)
12:46 < cfields> sipa: Huh, neat. I suppose you could probably find any fun pattern like that you want if you look long enough :)
12:46 < sipa> cfields: the actual string at that position is even 242424242 or something like that
12:47 < wumpus> jnewbery: thank you!
12:47 < promag> (sipa pretending he doesn't know all pi digits)
12:47 < aj> nope, it's my local clock that's 1s slow it seems. further updates in the news at 9
12:48 < sipa> promag: i can promise you that i cannot recite them backwards
12:48 < achow101> promag: new fact for pieterwuillefacts.com
12:48 < gloriazhao> i can recite all the unique digits of pi does that count
12:50 < wumpus> hehe
12:50 < sipa> gloriazhao: woah
12:50 < promag> btw regarding windows hang
12:50 < promag> what version is it?
12:51 < aj> gloriazhao: if you do it in the obvious order, it _is_ counting?
12:51 < sipa> promag: i don't know, and the user complaining on SE isn't volunteering much information
12:51 < promag> right, maybe he is using datadir on usb
12:52 < wumpus> we've already ruled out it happening on current versions of windows in the standard case?
12:53 < hebasto> promag: testing right now on Win10 build 19041.450, and cannot reproduce for now
12:53 < wumpus> hebasto: thanks for testing, I think it's good to have a baseline at least
12:54 < gwillen> cfields: fun fact -- it's actually an open problem whether you can find any fun pattern you like in pi if you look long enough! https://www.askamathematician.com/2009/11/since-pi-is-infinite-can-i-draw-any-random-number-sequence-and-be-certain-that-it-exists-somewhere-in-the-digits-of-pi/
12:54 < promag> he says "However, recently, whether it was a new version of Bitcoin Core or an update to Windows 10"
12:54 < promag> so looks like he updated bitcoind too
12:55 < hebasto> I'm testing v0.20.1
12:55 < sipa> gwillen: yeah, proving normality of a number is very hard
12:56 < cfields> gwillen: neat!
12:56 < promag> hebasto: vm?
12:56 < hebasto> yes
12:57 < sipa> gwillen, cfields: apparently some theorem about them was proven a certain C. P. Schnorr: https://en.wikipedia.org/wiki/Normal_number
12:59 < cfields> sipa: scared to click.. don't want to click, don't want him to sue me for using pi :p
12:59 < sipa> cfields: it's from 1972
12:59 < sipa> hebasto: based on earlier comments by (presumably) the same user under a different identity (long story), i suspect he is using 0.20.1 and not master
12:59 < cfields> whoops, some c/p there someow.
12:59 < cfields> sipa: that was a joke.
12:59 < sipa> cfields: obviously
13:00 < sipa> sorry, should have used an interrobang
13:00 < hebasto> sipa: thanks
13:00 < cfields> heh
13:01 < sipa> a c/p schnorr?
13:01 < cfields> nm
13:02 -!- Guyver2_ [Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev
13:02 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has quit [Ping timeout: 256 seconds]
13:03 < cfields> I'm going to resist going down another number theory rabbit hole. This stuff is so freaking fun to learn about.
13:06 < sipa> cfields: you know https://www.futilitycloset.com/wp-content/uploads/2018/10/2018-10-30-fruit-cocktail.jpg right?
13:16 < gwillen> sipa: apparently my freshman college roommate was responsible for the final version of that meme: https://www.quora.com/How-do-you-find-the-positive-integer-solutions-to-frac-x-y%2Bz-%2B-frac-y-z%2Bx-%2B-frac-z-x%2By-4/answer/Alon-Amit/comment/36734352
13:17 < sipa> ha
13:17 < sipa> small world
13:17 < sipa> alon amit's explanation there is a really nice read, btw, if you like number theory rabbit holes
13:18 < sipa> hint: it's got elliptic curves
13:20 -!- Guyver2_ [Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
13:21 -!- Bullit [~Bullit01@042-236-158-163.dynamic.caiway.nl] has joined #bitcoin-core-dev
13:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
13:27 < bitcoin-git> [bitcoin] laanwj opened pull request #20058: Update transifex slug for 0.21 (master...2020_10_transifex_slug) https://github.com/bitcoin/bitcoin/pull/20058
13:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
13:29 -!- GankMove [~GankMove@dsl-lprbng11-54f88d-13.dhcp.inet.fi] has joined #bitcoin-core-dev
13:35 < amiti> jnewbery, achow101, sipa, wumpus: I've also been seeing a decent amount of travis ARM64 builds just stopping w/out any exit status or explicit failure. another eg. https://travis-ci.org/github/bitcoin/bitcoin/jobs/732023438
13:36 < achow101> amiti: yeah, it seems to be travis just dying again
13:36 < amiti> 😬
13:36 < sipa> sigh
13:38 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #bitcoin-core-dev
13:41 < phantomcircuit> how difficult would it be to run those unit tests on a dedicated server?
13:42 < sipa> phantomcircuit: i'm sure we would have no problems finding funds to buy/run such a server, but something has to set it up and maintain it
13:42 < phantomcircuit> sipa, yeah that's my question, what would the maintenance look like?
13:42 < achow101> we have bitcoinbuilds.org doing almost everything
13:43 < phantomcircuit> presumably there isn't anything to prevent a pull request from being some altcoin miner
13:54 < aj> newb question, but now i've got a fuzzer crash, how do i get at the data that triggered it?
13:54 < sipa> aj: it should have created a file crash-HHHHHHHH
13:55 < aj> sipa: yep
13:55 < sipa> that contains the raw data fed to the fuzzer
13:55 < phantomcircuit> did someone fix the fuzzer stuff to be different binaries?
13:55 < sipa> phantomcircuit: yes, every fuzzer is one binary
13:55 < aj> sipa: right, but that got run through ConsumeIntegral and ConsumeDeserializable and stuff?
13:55 < sipa> aj: you can add debug statements to the fuzzer code, and then rerun it with ./fuzzer crash-HHHH
13:56 < sipa> if you need to see the "unpacked" values from it
14:00 -!- lordnoid1 [~lordnoid@178.239.168.171] has quit []
14:01 -!- filchef [~filchef@212.104.97.177] has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
14:08 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
14:08 < bitcoin-git> [bitcoin] laanwj closed pull request #20055: rpc: Set HTTP Content-Type in bitcoin-cli (master...2020_10_cli_contenttype) https://github.com/bitcoin/bitcoin/pull/20055
14:08 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
14:19 -!- Dimlock [~Dimlock@84.39.116.180] has joined #bitcoin-core-dev
14:23 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
14:23 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
14:35 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
14:35 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
15:11 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
15:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev
15:15 -!- S3RK [~s3rk@47.246.66.116] has joined #bitcoin-core-dev
15:15 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
15:19 -!- S3RK [~s3rk@47.246.66.116] has quit [Ping timeout: 240 seconds]
15:24 -!- thaumavorio [~thaumavor@thaumavor.io] has quit [Quit: ZNC 1.7.1 - https://znc.in]
15:25 -!- thaumavorio [~thaumavor@thaumavor.io] has joined #bitcoin-core-dev
15:32 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #bitcoin-core-dev
16:04 -!- Tennis [~Tennis@unaffiliated/tennis] has quit [Quit: Leaving]
16:11 -!- isis_ is now known as isis
16:39 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
16:40 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
16:55 -!- Netsplit *.net <-> *.split quits: fjahr, felixweis, ahmed_
16:55 -!- go1111111 [~go1111111@104.156.98.86] has joined #bitcoin-core-dev
17:00 -!- Dimlock [~Dimlock@84.39.116.180] has quit []
17:00 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
17:05 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
17:05 -!- Netsplit over, joins: felixweis, fjahr, ahmed_
17:05 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
17:06 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
17:19 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
17:22 -!- DuncanT1 [~DuncanT@84.39.116.180] has joined #bitcoin-core-dev
17:40 -!- S3RK [~s3rk@47.246.66.116] has joined #bitcoin-core-dev
17:44 -!- S3RK [~s3rk@47.246.66.116] has quit [Ping timeout: 240 seconds]
17:45 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
17:46 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
17:56 -!- S3RK [~s3rk@47.246.66.116] has joined #bitcoin-core-dev
18:25 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
18:34 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev
18:35 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds]
18:51 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
18:52 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev
18:55 -!- TallTim [~TallTim@216.15.20.214] has joined #bitcoin-core-dev
19:04 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
19:04 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Ping timeout: 240 seconds]
19:09 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds]
19:09 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds]
19:23 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection]
19:24 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #bitcoin-core-dev
19:28 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
19:33 -!- shesek [~shesek@164.90.217.137] has joined #bitcoin-core-dev
19:33 -!- shesek [~shesek@164.90.217.137] has quit [Changing host]
19:33 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev
20:00 -!- DuncanT1 [~DuncanT@84.39.116.180] has quit []
20:06 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds]
20:20 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
20:21 -!- Netsplit *.net <-> *.split quits: fjahr, felixweis, ahmed_
20:21 -!- sr_gi [~sr_gi@static-80-160-230-77.ipcom.comunitel.net] has quit [Write error: Connection reset by peer]
20:21 -!- espadrine [~espadrine@178.239.168.171] has joined #bitcoin-core-dev
20:21 -!- sr_gi [~sr_gi@static-80-160-230-77.ipcom.comunitel.net] has joined #bitcoin-core-dev
20:32 -!- Ga1aCt1Cz00 [~Ga1aCt1Cz@2a02:810a:8d40:5ebc:91f:d32d:ba1d:f0e5] has quit [Remote host closed the connection]
20:32 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
20:32 -!- Ga1aCt1Cz00 [~Ga1aCt1Cz@2a02:810a:8d40:5ebc:cc6a:ab86:a44a:da6f] has joined #bitcoin-core-dev
20:42 -!- promag_ [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
20:42 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Read error: Connection reset by peer]
20:43 -!- Emcy_ [~Emcy@unaffiliated/emcy] has quit [Quit: Leaving]
20:45 -!- opsec_x122 [~opsec_x12@44-25-143-49.ip.hamwan.net] has joined #bitcoin-core-dev
20:46 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev
20:48 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
20:48 -!- promag_ [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Read error: Connection reset by peer]
20:48 -!- opsec_x12 [~opsec_x12@44-25-143-49.ip.hamwan.net] has quit [Ping timeout: 260 seconds]
20:49 -!- Netsplit over, joins: felixweis, fjahr, ahmed_
21:02 -!- cato_ [~cato@gateway/tor-sasl/alec] has quit [Remote host closed the connection]
21:03 -!- cato_ [~cato@gateway/tor-sasl/alec] has joined #bitcoin-core-dev
21:03 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
21:03 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
21:06 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
21:07 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
21:08 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
21:09 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
21:09 < bitcoin-git> [bitcoin] robot-dreams closed pull request #19968: doc: make it easier to work out size of bloom filter (master...bloom-doc) https://github.com/bitcoin/bitcoin/pull/19968
21:09 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
21:09 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
21:09 < bitcoin-git> [bitcoin] robot-dreams reopened pull request #19968: doc: make it easier to work out size of bloom filter (master...bloom-doc) https://github.com/bitcoin/bitcoin/pull/19968
21:09 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
21:13 -!- sdaftuar [~sdaftuar@gateway/tor-sasl/sdaftuar] has quit [Remote host closed the connection]
21:14 -!- sdaftuar [~sdaftuar@gateway/tor-sasl/sdaftuar] has joined #bitcoin-core-dev
21:17 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
21:17 < bitcoin-git> [bitcoin] fanquake pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/a0185d90a7f2...69a73803dfb2
21:17 < bitcoin-git> bitcoin/master 598e3b1 Wladimir J. van der Laan: tx: Update transifex slug for 0.21
21:17 < bitcoin-git> bitcoin/master 7532c9a Wladimir J. van der Laan: qt: Periodic translations update
21:17 < bitcoin-git> bitcoin/master 69a7380 fanquake: Merge #20058: Update transifex slug for 0.21
21:17 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
21:17 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
21:17 < bitcoin-git> [bitcoin] fanquake merged pull request #20058: Update transifex slug for 0.21 (master...2020_10_transifex_slug) https://github.com/bitcoin/bitcoin/pull/20058
21:17 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
21:19 -!- S3RK [~s3rk@47.246.66.116] has quit [Remote host closed the connection]
21:20 -!- S3RK [~s3rk@47.246.66.116] has joined #bitcoin-core-dev
21:23 -!- hugohn [sid304114@gateway/web/irccloud.com/x-wnvicsfksfayqswb] has quit [Ping timeout: 256 seconds]
21:24 -!- hugohn [sid304114@gateway/web/irccloud.com/x-wigsyrnczlzuvegj] has joined #bitcoin-core-dev
21:24 -!- S3RK [~s3rk@47.246.66.116] has quit [Ping timeout: 260 seconds]
21:29 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
21:29 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev
21:32 -!- mekster [~mekster@139.180.192.79] has quit [Ping timeout: 260 seconds]
21:33 -!- mekster [~mekster@139.180.192.79] has joined #bitcoin-core-dev
21:38 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
21:38 < bitcoin-git> [bitcoin] fanquake opened pull request #20060: refactor: fix -Wbraced-scalar-init warning in validation tests (master...braces_scalar_init) https://github.com/bitcoin/bitcoin/pull/20060
21:38 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
21:39 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds]
21:42 -!- S3RK [~s3rk@47.246.66.116] has joined #bitcoin-core-dev
21:57 -!- proofofkeags [~proofofke@174-29-30-112.hlrn.qwest.net] has quit [Ping timeout: 260 seconds]
22:00 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds]
22:01 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev
22:08 -!- ohsoclean [~ohsoclean@2606:6080:2001:5:48ec:2d6:cc35:3864] has joined #bitcoin-core-dev
22:22 -!- braydonf [~braydon@gateway/tor-sasl/braydonf] has quit [Remote host closed the connection]
22:22 -!- braydonf [~braydon@gateway/tor-sasl/braydonf] has joined #bitcoin-core-dev
22:23 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
22:24 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
22:26 -!- Asbestos_Vapor [~Mercury_V@174-082-166-092.res.spectrum.com] has quit [Ping timeout: 256 seconds]
22:28 -!- ohsoclean [~ohsoclean@2606:6080:2001:5:48ec:2d6:cc35:3864] has left #bitcoin-core-dev ["Leaving..."]
22:28 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection]
22:29 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev
22:31 -!- Mercury_Vapor [~Mercury_V@174-082-166-092.res.spectrum.com] has joined #bitcoin-core-dev
22:54 -!- S3RK [~s3rk@47.246.66.116] has quit [Remote host closed the connection]
23:00 -!- espadrine [~espadrine@178.239.168.171] has quit []
23:21 -!- AIM [~AIM@195.206.169.184] has joined #bitcoin-core-dev
23:36 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
23:39 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has joined #bitcoin-core-dev
23:39 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
23:39 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/69a73803dfb2...a6a993a888f5
23:39 < bitcoin-git> bitcoin/master 82b70f1 fanquake: refactor: fix -Wbraced-scalar-init warning in validation tests
23:39 < bitcoin-git> bitcoin/master a6a993a MarcoFalke: Merge #20060: refactor: fix -Wbraced-scalar-init warning in validation tes...
23:39 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
23:40 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
23:40 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #20060: refactor: fix -Wbraced-scalar-init warning in validation tests (master...braces_scalar_init) https://github.com/bitcoin/bitcoin/pull/20060
23:40 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
23:42 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has quit [Ping timeout: 256 seconds]
23:49 -!- S3RK [~s3rk@47.246.66.116] has joined #bitcoin-core-dev
23:54 -!- S3RK [~s3rk@47.246.66.116] has quit [Ping timeout: 265 seconds]
23:58 -!- S3RK [~s3rk@47.246.66.116] has joined #bitcoin-core-dev
23:58 -!- cltrbreak_MAD2 [~ctrlbreak@159.2.182.106] has joined #bitcoin-core-dev
--- Log closed Fri Oct 02 00:00:35 2020