--- Log opened Thu Feb 11 00:00:26 2021 00:22 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 00:25 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev 00:26 -!- jonatack [~jon@37.173.248.254] has quit [Ping timeout: 272 seconds] 00:27 -!- jungly [~jungly@host-80-104-171-181.retail.telecomitalia.it] has quit [Ping timeout: 256 seconds] 00:27 -!- jungly [~jungly@host-79-12-187-142.retail.telecomitalia.it] has joined #bitcoin-core-dev 00:27 -!- mrostecki [mrostecki@nat/suse/x-avfusvhnqdgrkbkk] has quit [Quit: WeeChat 1.8] 00:30 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 00:30 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 00:30 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has joined #bitcoin-core-dev 00:31 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 260 seconds] 00:38 -!- promag [~promag@188.250.84.129] has joined #bitcoin-core-dev 00:38 -!- sr_gi [~sr_gi@static-125-62-230-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 00:39 -!- sr_gi [~sr_gi@static-125-62-230-77.ipcom.comunitel.net] has joined #bitcoin-core-dev 00:43 -!- promag [~promag@188.250.84.129] has quit [Ping timeout: 272 seconds] 00:47 -!- flag [~flag@net-5-94-131-164.cust.vodafonedsl.it] has joined #bitcoin-core-dev 00:50 -!- promag [~promag@188.250.84.129] has joined #bitcoin-core-dev 00:58 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection] 00:58 -!- asdlkfjwerpoicvx [~flack@p200300d46f24de00088efaeaba4d1e1e.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 00:58 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev 01:00 -!- wumpus [~ircclient@pdpc/supporter/professional/wumpus] has quit [Ping timeout: 272 seconds] 01:20 < vasild> sdaftuar: I wonder if it is worth changing SIGNATURE_TYPE=EdDSA_SHA512_Ed25519 to SIGNATURE_TYPE=7 in the request we send? If the buggy i2pd is the latest version which debian stable has... 01:30 -!- rich [~rich@shindig.notmandatory.org] has quit [Ping timeout: 256 seconds] 01:31 -!- paracyst [paracyst@unaffiliated/paracyst] has quit [Ping timeout: 272 seconds] 01:31 -!- paracyst_ [paracyst@unaffiliated/paracyst] has joined #bitcoin-core-dev 01:31 -!- rich [~rich@shindig.notmandatory.org] has joined #bitcoin-core-dev 01:31 -!- cornfeedhobo [~cornfeedh@unaffiliated/cornfeed] has quit [Ping timeout: 246 seconds] 01:31 -!- cryptapus_ [~cryptapus@jupiter.osmus.org] has joined #bitcoin-core-dev 01:31 -!- cryptapus_ [~cryptapus@jupiter.osmus.org] has quit [Changing host] 01:31 -!- cryptapus_ [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 01:32 -!- IGHOR [~quassel@176.121.4.135] has quit [Ping timeout: 272 seconds] 01:32 -!- IGHOR_ [~quassel@176.121.4.135] has joined #bitcoin-core-dev 01:32 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Ping timeout: 265 seconds] 01:32 -!- midnight [~midnight@unaffiliated/midnightmagic] has quit [Ping timeout: 272 seconds] 01:33 -!- ishaqm [~ishaqm@host-92-26-31-113.as13285.net] has joined #bitcoin-core-dev 01:34 -!- cornfeedhobo [~cornfeedh@unaffiliated/cornfeed] has joined #bitcoin-core-dev 01:35 < ishaqm> all, does anyone have pointers on compiling bitcoin-core with DEBUG symbols on? 01:36 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 01:36 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/b69eab902567...dd0521b6408a 01:36 < bitcoin-git> bitcoin/master fabeb5b MarcoFalke: fuzz: Disable shuffle when merge=1 01:36 < bitcoin-git> bitcoin/master dd0521b MarcoFalke: Merge #21023: fuzz: Disable shuffle when merge=1 01:36 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 01:36 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 01:36 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #21023: fuzz: Disable shuffle when merge=1 (master...2101-fuzzMerge) https://github.com/bitcoin/bitcoin/pull/21023 01:36 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 01:38 -!- IGHOR_ [~quassel@176.121.4.135] has quit [Ping timeout: 240 seconds] 01:38 -!- wumpus [~ircclient@pdpc/supporter/professional/wumpus] has joined #bitcoin-core-dev 01:40 -!- IGHOR [~quassel@176.121.4.135] has joined #bitcoin-core-dev 01:41 < michaelfolkson> ishaqm: Does this answer your question? Please upvote if you find it useful https://bitcoin.stackexchange.com/questions/66892/what-are-the-debug-categories 01:41 -!- jungly [~jungly@host-79-12-187-142.retail.telecomitalia.it] has quit [Ping timeout: 246 seconds] 01:42 -!- Emcy_ [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 01:43 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Remote host closed the connection] 01:43 < ishaqm> michaelfolkson, let me check (and of course if this is the answer, it must be upvoted :-) ) 01:43 < ishaqm> thank you 01:45 < michaelfolkson> Or this https://github.com/bitcoin/bitcoin/blob/34322b7f5cbdf05d625dff671b6c2f34749cd2b1/doc/developer-notes.md#compiling-for-debugging 01:46 < ishaqm> i see, I might have phrased my question better I am afraid. I am trying to output debug *symbols* i.e. so that I can run it with a debugger (gdb or similar) 01:47 < ishaqm> ah, the second link is exactly what I wanted, thank you very much michaelfolkson 01:47 < michaelfolkson> No problem 01:47 -!- gleb [~gleb@178.150.137.228] has quit [Remote host closed the connection] 01:47 -!- gleb [~gleb@178.150.137.228] has joined #bitcoin-core-dev 01:53 -!- jungly [~jungly@host-79-12-187-142.retail.telecomitalia.it] has joined #bitcoin-core-dev 01:53 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 01:53 < bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/dd0521b6408a...a59e7ed0bc34 01:53 < bitcoin-git> bitcoin/master faefed8 MarcoFalke: fuzz: Count message type fuzzers before main() 01:53 < bitcoin-git> bitcoin/master fa4bc89 MarcoFalke: fuzz: Fail if message type is not fuzzed 01:53 < bitcoin-git> bitcoin/master a59e7ed MarcoFalke: Merge #20915: fuzz: Fail if message type is not fuzzed 01:53 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 01:53 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 01:53 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #20915: fuzz: Fail if message type is not fuzzed (master...2101-fuzzFailMsgType) https://github.com/bitcoin/bitcoin/pull/20915 01:54 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 01:55 -!- Processus42 [~leo@unaffiliated/processus42] has quit [Remote host closed the connection] 01:56 -!- dfjfyfjmkghmhmkg [5d24be18@93-36-190-24.ip61.fastwebnet.it] has joined #bitcoin-core-dev 01:56 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev 01:57 -!- dfjfyfjmkghmhmkg [5d24be18@93-36-190-24.ip61.fastwebnet.it] has quit [Client Quit] 02:02 -!- Processus42 [~leo@unaffiliated/processus42] has joined #bitcoin-core-dev 02:02 < prusnak> dongcarl: is there a Guix Docker image or what's the preferred way to build bitcoin w/ guix on macos ? 02:03 < fanquake> prusnak: you can try using https://github.com/fanquake/core-review/tree/master/guix if you want to. I think we link to it from our Guix docs as well. 02:03 < fanquake> That sets up a Docker image for doing Guix builds 02:03 < prusnak> ah great, so docker is preferred, ty 02:05 < prusnak> i'll send a pr to your repo, so also arm64 builds work via docker 02:06 < fanquake> great thanks 02:15 -!- Zenton [~user@unaffiliated/vicenteh] has joined #bitcoin-core-dev 02:20 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 02:27 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Disconnected by services] 02:27 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev 02:27 -!- vasild_ is now known as vasild 02:32 -!- midnight [~midnight@unaffiliated/midnightmagic] has joined #bitcoin-core-dev 02:33 -!- ishaqm [~ishaqm@host-92-26-31-113.as13285.net] has quit [Ping timeout: 260 seconds] 02:44 -!- ishaqm [~ishaqm@host-92-26-31-113.as13285.net] has joined #bitcoin-core-dev 02:48 -!- ishaqm [~ishaqm@host-92-26-31-113.as13285.net] has quit [Remote host closed the connection] 02:49 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 02:49 < bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/a59e7ed0bc34...e498aeffbec9 02:49 < bitcoin-git> bitcoin/master fa59e0b MarcoFalke: test: Add missing script_standard_Solver_success cases 02:49 < bitcoin-git> bitcoin/master fa650ca MarcoFalke: Use -Wswitch for TxoutType where possible 02:49 < bitcoin-git> bitcoin/master e498aef MarcoFalke: Merge #20211: Use -Wswitch for TxoutType where possible 02:50 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 02:50 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 02:50 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #20211: Use -Wswitch for TxoutType where possible (master...2010-WswitchTxoutType) https://github.com/bitcoin/bitcoin/pull/20211 02:50 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 02:52 -!- ishaqm [~ishaqm@host-92-26-31-113.as13285.net] has joined #bitcoin-core-dev 03:03 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Remote host closed the connection] 03:03 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev 03:13 -!- mrostecki [mrostecki@nat/suse/x-znnawdplrvikyuww] has joined #bitcoin-core-dev 03:18 -!- Jaron69Goldner [~Jaron69Go@static.57.1.216.95.clients.your-server.de] has joined #bitcoin-core-dev 03:30 -!- sdaftuar [~sdaftuar@gateway/tor-sasl/sdaftuar] has quit [Remote host closed the connection] 03:30 -!- sdaftuar [~sdaftuar@gateway/tor-sasl/sdaftuar] has joined #bitcoin-core-dev 03:32 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 03:37 -!- cryptapus_ is now known as cryptapus 03:41 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 03:41 < bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/e498aeffbec9...685c16fcb2c7 03:41 < bitcoin-git> bitcoin/master f5f2f97 practicalswift: net: Avoid UBSan warning in ProcessMessage(...) 03:41 < bitcoin-git> bitcoin/master 3ddbf22 MarcoFalke: util: Disallow negative mocktime 03:41 < bitcoin-git> bitcoin/master 685c16f MarcoFalke: Merge #21043: net: Avoid UBSan warning in ProcessMessage(...) 03:41 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 03:42 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 03:42 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #21043: net: Avoid UBSan warning in ProcessMessage(...) (master...ubsan-nTime) https://github.com/bitcoin/bitcoin/pull/21043 03:42 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 03:51 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 04:06 -!- Jaron69Goldner [~Jaron69Go@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 272 seconds] 04:33 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has quit [Read error: Connection reset by peer] 04:51 -!- notmandatory [notmandato@2600:3c00::f03c:92ff:fe8e:dce6] has joined #bitcoin-core-dev 04:52 -!- notmandatory_ [~notmandat@shindig.notmandatory.org] has quit [Ping timeout: 264 seconds] 04:54 -!- ishaqm [~ishaqm@host-92-26-31-113.as13285.net] has quit [Remote host closed the connection] 04:57 -!- jonatack [~jon@37.169.62.216] has joined #bitcoin-core-dev 05:01 -!- Mercury_Vapor [~Mercury_V@174-082-158-108.res.spectrum.com] has joined #bitcoin-core-dev 05:04 -!- belcher_ is now known as belcher 05:08 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 05:08 < bitcoin-git> [bitcoin] laanwj pushed 7 commits to master: https://github.com/bitcoin/bitcoin/compare/685c16fcb2c7...a1be08405d9b 05:08 < bitcoin-git> bitcoin/master aa17a44 Vasil Dimov: net: move MillisToTimeval() from netbase to util/time 05:08 < bitcoin-git> bitcoin/master dec9b5e Vasil Dimov: net: move CloseSocket() from netbase to util/sock 05:08 < bitcoin-git> bitcoin/master ba9d732 Vasil Dimov: net: add RAII socket and use it instead of bare SOCKET 05:08 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 05:08 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 05:08 < bitcoin-git> [bitcoin] laanwj merged pull request #20788: net: add RAII socket and use it instead of bare SOCKET (master...sock) https://github.com/bitcoin/bitcoin/pull/20788 05:08 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 05:10 < vasild> jonatack: wumpus: Thanks! Now lets see what happens with the I2P PR, I think some good simplification will be possible. Maybe the moving of SocketEvents() to a standalone function will not be necessary because it would be possible to use sock.Wait() 05:11 < vasild> SocketEvents() allows to wait for at least one of a bunch of sockets to become ready. If it is just one socket then sock.Wait() may be used as well. 05:12 < jonatack> vasild: looking forward to it :) 05:14 < vasild> The I2P PR used SocketEvents() to wait on more than one socket simultaneously at some point - to issue more than one STREAM ACCEPT, but it turned out that this is SAM 3.2 feature and i2pd only supports SAM 3.1, so IIRC we no longer call SocketEvents() with more than one socket. 05:16 < vasild> So, now we wait for incoming connections on just one socket and there is a tiny interval of time - after we have accepted a connection and before we issue STREAM ACCEPT where we are not listening. I think this is acceptable, though I did not check what happens if somebody tries to connect to us exactly then - would he get an error or just wait for us to issue STREAM ACCEPT. 05:17 * vasild brb... 05:18 -!- cguida [~cguida@fixed-189-203-97-30.totalplay.net] has joined #bitcoin-core-dev 05:30 -!- qapla_org [~qapla_org@217.146.82.202] has quit [Remote host closed the connection] 05:31 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has joined #bitcoin-core-dev 05:31 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 05:38 < wumpus> vasild: i'm pretty sure you need something like socketEvents, after all the P2P code uses async networking, waiting on one socket is not enough 05:39 < wumpus> (or is this only for session setup like the SOCKS5 init?) 05:46 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Remote host closed the connection] 05:47 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 05:47 < bitcoin-git> [bitcoin] MarcoFalke pushed 5 commits to master: https://github.com/bitcoin/bitcoin/compare/a1be08405d9b...8e1913ae025a 05:47 < bitcoin-git> bitcoin/master 9db10a5 gzhao408: [refactor] clean up logic in testmempoolaccept 05:47 < bitcoin-git> bitcoin/master f82baf0 gzhao408: [refactor] return MempoolAcceptResult 05:47 < bitcoin-git> bitcoin/master 174cb53 gzhao408: [refactor] const ATMPArgs and non-const Workspace 05:47 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 05:47 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 05:47 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #21062: refactor: return MempoolAcceptResult from ATMP (master...2021-02-refactor-validation) https://github.com/bitcoin/bitcoin/pull/21062 05:47 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 05:52 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-core-dev 05:54 -!- rc_423 [~r_423@cpe-75-185-100-189.cinci.res.rr.com] has joined #bitcoin-core-dev 05:56 -!- rc_423_ [~r_423@cpe-75-185-100-189.cinci.res.rr.com] has quit [Ping timeout: 256 seconds] 05:59 -!- morcos [~morcos@gateway/tor-sasl/morcos] has joined #bitcoin-core-dev 06:03 < vasild> wumpus: after we accept the i2p socket (in a i2p-specific way, not like usual tcp sockets via listen() bind() accept()), we give it to the connman like a normal already connected peer, then it uses CConnman::SocketEvents() internally to see if some of the peers has something to say 06:04 -!- jonatack [~jon@37.169.62.216] has quit [Ping timeout: 240 seconds] 06:05 < vasild> but lets see... 06:06 < wumpus> vasild: ok so it's similar to SOCKS5 in that regard, there's some initial setup but after that it's simply a TCP connection like any other 06:07 < vasild> exactly 06:08 < wumpus> makes sense thanks 06:13 -!- jonatack [~jon@37.169.62.216] has joined #bitcoin-core-dev 06:30 < luke-jr> -builder for `/home/dev/guix/root/gnu/store/6mx4wp11nwrj886amyb86nwgvws68d03-gzip-1.10.tar.xz.drv' failed to produce output path `/home/dev/guix/root/gnu/store/vgrx621h8750zm0ijlpdfnd9s4igsakp-gzip-1.10.tar.xz' 06:30 < luke-jr> dongcarl: I put the file where it wants it, but it's just deleting it and trying to refetch 06:45 -!- blackjid [~blackjid@195.140.213.38] has joined #bitcoin-core-dev 06:48 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev 06:50 -!- harrigan [~harrigan@ptr-93-89-242-202.ip.airwire.ie] has quit [Read error: Connection reset by peer] 06:52 -!- harrigan [~harrigan@ptr-93-89-242-202.ip.airwire.ie] has joined #bitcoin-core-dev 06:54 -!- kexkey [~kexkey@static-198-54-132-89.cust.tzulo.com] has joined #bitcoin-core-dev 07:06 -!- ishaqm [~ishaqm@host-92-26-31-113.as13285.net] has joined #bitcoin-core-dev 07:07 -!- harrigan [~harrigan@ptr-93-89-242-202.ip.airwire.ie] has quit [Read error: Connection reset by peer] 07:07 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Ping timeout: 268 seconds] 07:10 -!- harrigan [~harrigan@ptr-93-89-242-202.ip.airwire.ie] has joined #bitcoin-core-dev 07:10 < dongcarl> luke-jr: happy to debug, could you send me logs? 07:12 < sdaftuar> vasild: maybe, or perhaps we should just document the requirements somewhere so that others aren't tripped up? i don't have much of an opinion i guess 07:27 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev 07:38 -!- Kiminuo [~Kiminuo@141.98.103.124] has quit [Ping timeout: 246 seconds] 07:58 < luke-jr> dongcarl: nothing interesting in log 07:58 < luke-jr> https://dpaste.com/FN25ZCJLU 08:07 -!- ishaqm [~ishaqm@host-92-26-31-113.as13285.net] has quit [Ping timeout: 272 seconds] 08:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 08:27 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/8e1913ae025a...0ad46567905a 08:27 < bitcoin-git> bitcoin/master fabce45 MarcoFalke: fuzz: version handshake 08:27 < bitcoin-git> bitcoin/master 0ad4656 MarcoFalke: Merge #20370: fuzz: version handshake 08:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 08:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 08:27 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #20370: fuzz: version handshake (master...2011-fuzzNetFlags) https://github.com/bitcoin/bitcoin/pull/20370 08:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 08:47 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #bitcoin-core-dev 08:52 -!- asdlkfjwerpoicvx [~flack@p200300d46f24de00088efaeaba4d1e1e.dip0.t-ipconnect.de] has quit [Quit: Konversation terminated!] 08:53 -!- ishaqm [~ishaqm@host-92-26-31-113.as13285.net] has joined #bitcoin-core-dev 08:54 -!- ishaqm [~ishaqm@host-92-26-31-113.as13285.net] has quit [Remote host closed the connection] 08:58 -!- setpill [~setpill@unaffiliated/setpill] has quit [Quit: o/] 09:08 < dongcarl> luke-jr: That log you linked doesn't look like text? 09:11 -!- jonatack [~jon@37.169.62.216] has quit [Read error: Connection reset by peer] 09:20 -!- harrigan [~harrigan@ptr-93-89-242-202.ip.airwire.ie] has quit [Read error: Connection reset by peer] 09:20 -!- cguida [~cguida@fixed-189-203-97-30.totalplay.net] has quit [Quit: Leaving.] 09:21 -!- jonatack [~jon@37.169.62.216] has joined #bitcoin-core-dev 09:21 -!- harrigan [~harrigan@ptr-93-89-242-202.ip.airwire.ie] has joined #bitcoin-core-dev 09:21 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 265 seconds] 09:21 -!- larryruane_ [uid473749@gateway/web/irccloud.com/x-mvpbcqmcknxawhss] has quit [Quit: Connection closed for inactivity] 09:23 -!- harrigan [~harrigan@ptr-93-89-242-202.ip.airwire.ie] has quit [Read error: Connection reset by peer] 09:29 -!- harrigan [~harrigan@ptr-93-89-242-202.ip.airwire.ie] has joined #bitcoin-core-dev 09:33 -!- Kiminuo [~Kiminuo@141.98.103.124] has joined #bitcoin-core-dev 09:34 -!- jonatack [~jon@37.169.62.216] has quit [Ping timeout: 256 seconds] 09:36 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev 09:41 < sipa> luke-jr, dongcarl: https://0bin.net/paste/8tHpMqMh#EAeXD372w0YUBvQHVjg842ywOoDobs023QBQ0hbf-Xc 09:42 < sipa> luke-jr: your dpaste looks like bzip2 compressed data 09:43 < dongcarl> sipa: could you send me `/usr/local/var/log/guix/drvs/wk/rgrjfkpqdzdvv81nbra7bvskfl9i57-gawk-5.0.1.drv.gz`? 09:46 < sipa> dongcarl: i restarted, and it seems to work now... 09:47 < dongcarl> sipa: Great! 09:48 < dongcarl> One of the things that Guix tries to do is to run as much of the test suite for its packages as possible... Which is great in ensuring that the built product works, but a lot of times reveals just how fragile pacakges' tests are (esp in a multi-threaded environment) 10:02 < luke-jr> sipa: indeed! lol 10:02 < luke-jr> https://dpaste.com/7QAVTM2RT 10:03 < luke-jr> `less` automatically decompresses but `wgetpaste` does not >_< 10:05 < luke-jr> if I make the source immutable, it errors with guix install: error: cannot unlink `/home/dev/guix/root/gnu/store/vgrx621h8750zm0ijlpdfnd9s4igsakp-gzip-1.10.tar.xz': Operation not permitted 10:05 < luke-jr> still no explanation why it's trying to delete and refetch it 10:08 -!- jonatack [~jon@37.169.62.216] has joined #bitcoin-core-dev 10:18 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Quit: Leaving] 10:18 < sipa> luke-jr: did starting over help? 10:19 < luke-jr> sipa: no 10:19 * dongcarl looking 10:19 < dongcarl> luke-jr: Did you turn off networking for this? 10:19 < luke-jr> sipa: not sure how far I got last time, but it's probably around the same point 10:19 < luke-jr> dongcarl: yes 10:20 < dongcarl> Okay, asking on #guix now 10:21 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has quit [Remote host closed the connection] 10:21 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has joined #bitcoin-core-dev 10:24 < dongcarl> Aha! 10:25 < dongcarl> luke-jr: Do: `guix download ` 10:25 -!- jungly [~jungly@host-79-12-187-142.retail.telecomitalia.it] has quit [Ping timeout: 256 seconds] 10:25 < luke-jr> oh right, it keeps a db of what it has :/ 10:27 < sipa> is there a way to make it download everything it will need for a particular build? 10:28 < dongcarl> sipa: I'm guessing if you do `--dry-run` it'll do that? 10:28 * dongcarl double-checking 10:36 < dongcarl> FWIW: All guix package builds are offline (enforced by network namespaces I think) and hermetic. The bitcoin build script I wrote also builds in a completely offline environment by default. 10:36 < dongcarl> Of course, pulling out the ethernet cable may be easier to trust... 10:36 < luke-jr> keeping guix itself offline is my only way to ensure it doesn't pull in a blob 10:38 < luke-jr> iptables -I OUTPUT -m owner --uid-owner dev -j REJECT 10:38 < luke-jr> in this case 10:39 < dongcarl> Right. I'm gunna see if it's easy to write a Guile script to generate a list of files to download from a manifest... 10:39 < sipa> luke-jr: but it needs to download source code anyway, and how do you know that source code doesn't contain any blobs? :) 10:39 < sipa> i guess your argument is: you download everything once, inspect it, then turn off networking, and build it? 10:40 < luke-jr> sipa: that's why I'm downloading each one manually and checking 10:40 -!- jonatack [~jon@37.169.62.216] has quit [Read error: Connection reset by peer] 10:40 < luke-jr> I'll automate it once I have it sorted out 10:41 < sipa> that's fair 10:41 -!- jonatack [~jon@37.169.62.216] has joined #bitcoin-core-dev 10:41 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 10:41 < bitcoin-git> [bitcoin] prayank23 opened pull request #21155: doc: Improve Tor docs (master...tor-docs-improve) https://github.com/bitcoin/bitcoin/pull/21155 10:41 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 10:42 < dongcarl> luke-jr: I'll post on the Guix mailing list about extracting out a list of needed downloads from a manifest, hopefully it's a simple enough Guile script. 10:42 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Ping timeout: 268 seconds] 10:44 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev 10:50 < sipa> dongcarl: if what i've been told about scheme/lisp is true, this should be easy ;) 10:51 -!- jonatack [~jon@37.169.62.216] has quit [Ping timeout: 240 seconds] 10:52 -!- jonatack [~jon@37.169.62.216] has joined #bitcoin-core-dev 10:52 -!- jonatack [~jon@37.169.62.216] has quit [Read error: Connection reset by peer] 10:54 < dongcarl> sipa: Hehe true :-) 10:57 < luke-jr> dongcarl: guix ignored that Debian trick 10:57 < MarcoFalke> how much space does a guix build need these days (looks like DrahtBot is running out of disk) 10:57 < luke-jr> stubbornly insisting on https://git.savannah.gnu.org/cgit/guix.git/plain/gnu/packages/bootstrap/i686-linux/bash?id=44f07d1dc6806e97c4e9ee3e6be883cc59dc666e 10:58 < dongcarl> MarcoFalke: You can most likely garbage collect and get some space back. One thing on my list is to pin the latest manifest output so that it doesn't get garbage collected, so that you can safely garbage collect everything else without affecting bitcoin builds 10:58 < dongcarl> luke-jr: Looking 10:58 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 10:58 < bitcoin-git> [bitcoin] laanwj pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/0ad46567905a...937dfa839873 10:59 < bitcoin-git> bitcoin/master acd7980 practicalswift: log: Move "Leaving block file [...]: [...]" log message to debug category 10:59 < bitcoin-git> bitcoin/master 25f899c practicalswift: log: Move "Pre-allocating up to position 0x[...] in [...].dat" log message... 10:59 < bitcoin-git> bitcoin/master 937dfa8 Wladimir J. van der Laan: Merge #21041: log: Move "Pre-allocating up to position 0x[…] in […].dat" l... 10:59 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 10:59 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 10:59 < bitcoin-git> [bitcoin] laanwj merged pull request #21041: log: Move "Pre-allocating up to position 0x[…] in […].dat" log message to debug category (master...pre-allocation-up-to-position-0xff-in-foo.dat) https://github.com/bitcoin/bitcoin/pull/21041 10:59 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 10:59 < MarcoFalke> dongcarl: wait? guix can garbage collect? how 10:59 < dongcarl> MarcoFalke: https://guix.gnu.org/manual/en/html_node/Invoking-guix-gc.html 11:00 < dongcarl> MarcoFalke: HPC folks love their admin tools hehe 11:00 < wumpus> #startmeeting 11:00 < core-meetingbot> Meeting started Thu Feb 11 19:00:17 2021 UTC. The chair is wumpus. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings. 11:00 < core-meetingbot> Available commands: action commands idea info link nick 11:00 < fjahr> hi 11:00 < wumpus> #bitcoin-core-dev Meeting: achow101 aj amiti ariard bluematt cfields Chris_Stewart_5 digi_james dongcarl elichai2 emilengler fanquake fjahr gleb glozow gmaxwell gwillen hebasto instagibbs jamesob jb55 jeremyrubin jl2012 jnewbery jonasschnelli jonatack jtimon kallewoof kanzure kvaciral lightlike luke-jr maaku marcofalke meshcollider michagogo moneyball morcos nehan NicolasDorier paveljanik 11:00 < wumpus> petertodd phantomcircuit promag provoostenator ryanofsky sdaftuar sipa vasild wumpus 11:00 < michaelfolkson> hi 11:00 < dongcarl> hi 11:00 < luke-jr> existing convo overwritten by meeting :P 11:00 < achow101> hi 11:01 < phantomcircuit> hi 11:01 < warren> hi 11:01 < phantomcircuit> warren, HI 11:01 < jonasschnelli> Hi 11:01 < wumpus> one proposed meeting topic Initial Guix Release Transition Plan for 22.0 (dongcarl) 11:01 -!- jonatack [~jon@37.173.153.89] has joined #bitcoin-core-dev 11:02 < dongcarl> :) 11:02 < wumpus> anything else to discuss this week? 11:02 < MarcoFalke> hi 11:02 < sipa> hi 11:02 < jonatack> hi 11:02 < jonasschnelli> I have a small one,... nested commands vs @height macros 11:02 < wumpus> jonasschnelli: thanks 11:02 < jnewbery> hi 11:03 < wumpus> #topic High priority for review 11:03 < core-meetingbot> topic: High priority for review 11:03 < wumpus> https://github.com/bitcoin/bitcoin/projects/8 open: 7 blockers, no bugfixes, 2 chasing concept ACK 11:03 < wumpus> anything to add/remove or that is ready for merge? 11:03 < sdaftuar> can i request that #20726 be added? 11:04 < gribble> https://github.com/bitcoin/bitcoin/issues/20726 | p2p: Add DISABLETX message for negotiating block-relay-only connections by sdaftuar · Pull Request #20726 · bitcoin/bitcoin · GitHub 11:04 < sipa> i like #20861 11:04 < gribble> https://github.com/bitcoin/bitcoin/issues/20861 | BIP 350: Implement Bech32m and use it for v1+ segwit addresses by sipa · Pull Request #20861 · bitcoin/bitcoin · GitHub 11:04 < sipa> *i'd like 11:04 < jonatack> #19145 seems close to rfm 11:04 < gribble> https://github.com/bitcoin/bitcoin/issues/19145 | Add hash_type MUHASH for gettxoutsetinfo by fjahr · Pull Request #19145 · bitcoin/bitcoin · GitHub 11:04 < wumpus> sdaftuar: added 11:04 < achow101> 19145 has 4 acks 11:04 < wumpus> jonatack: achow101 good to know 11:05 < fjahr> jonatack, achow101: thanks, I was just typing :) 11:05 < wumpus> sipa: added 11:05 < meshcollider> hi 11:06 < wumpus> #topic Initial Guix Release Transition Plan for 22.0 (dongcarl) 11:06 < core-meetingbot> topic: Initial Guix Release Transition Plan for 22.0 (dongcarl) 11:06 < dongcarl> Hello everyone! I'm published a plan here: #21145 11:06 < gribble> https://github.com/bitcoin/bitcoin/issues/21145 | Guix Release Transition Plan for 22.0 · Issue #21145 · bitcoin/bitcoin · GitHub 11:07 < wumpus> dongcarl: great! 11:07 < dongcarl> There is a "What I need help with" section, which I'd encourage people to look at 11:07 < wumpus> adding 22.0 milestone 11:07 < dongcarl> :) 11:07 < luke-jr> still missing gitian support 11:07 < wumpus> i've been trying around with guix builds, seems to work okay 11:08 < dongcarl> wumpus: Happy to hear that! 11:08 < achow101> the guix build seems to work 11:08 < luke-jr> only if you run third-party blobs 11:08 < achow101> getting guix setup seems to be the sticking point 11:08 < dongcarl> As always, anything that doesn't work: tell me and I'll document and try to debug 11:09 < dongcarl> Right. Setting up Guix is definitely a pain point, which is why a detailed installation guide is in the TODOs 11:09 < wumpus> hit some small snags but it they were my own fault (e.g. crap left behind in the build dir), and the issue reported https://github.com/bitcoin/bitcoin/pull/21089#issuecomment-777562303 here which seems to be harmless just spammy 11:10 < MarcoFalke> Is it? debian bullseye comes with it and setting it up on other distros isn't too hard either. I think the pain point is to keep it in a working state/learn to use it. 11:10 < dongcarl> wumpus: My general feeling is that if people run into things that are "their own fault" enough times, it's probably best to add an early check. 11:10 < warren> luke-jr: I don't understand why you are asking for gitian support. The purpose of switching to guix is to eliminate the untrackable blob that we had in gitian. 11:10 < wumpus> i had no trouble setting up guix at all, then again an ubuntu VM is probably easy mode 11:10 < luke-jr> warren: as things stand, Guix is a regression in that respect 11:11 < sipa> luke-jr: you can run guix in a VM if you like 11:11 < luke-jr> warren: gitian works just fine without any untrusted blobs on my own system 11:11 < MarcoFalke> Didn't we discuss this last week? 11:11 < sipa> yes 11:11 < wumpus> yes, no need to revisit this 11:11 < MarcoFalke> ok, let's move on for now 11:11 < luke-jr> it still needs to get on the plan 11:11 < MarcoFalke> dongcarl: Do we need to change anything in the ci? 11:12 < wumpus> luke-jr: you can write it yourself and contribute it as well as you want it so badly 11:12 < wumpus> luke-jr: don't demand others work 11:12 < luke-jr> wumpus: first I need to get Guix to work ;) 11:12 < MarcoFalke> Currently we have the windows cross build using focal because gitian uses that 11:12 < MarcoFalke> (windows cross build in the ci) 11:12 < warren> dongcarl: Pre-meeting it sounds like a supported way to pre-populate downloads for guix bootstrap is a priority. The packager of Guix for Debian similarly commented that entirely offline is a requirement for their distro packages. He had to add a ton of unsupported hacks to package Guix for Debian. 11:13 < sipa> i've been setting up guix from scratch in an ubuntu VM, from source, with --bootstrap... it's been a bit of a pain, but running fine now 11:13 < MarcoFalke> So I am wondering how to deal with diverging compilers between the guix windows build and the ci windows build 11:13 * dongcarl trying to answer one at a time 11:14 < sipa> MarcoFalke: ideally we have a guix build in CI, i guess? 11:14 < MarcoFalke> sipa: That'd be hard to setup, because you'd have to cache the gnu_store 11:14 < MarcoFalke> for DrahtBot that is 11GB 11:14 < MarcoFalke> 11G ./temp/scratch/guix/root_store/ 11:15 < dongcarl> MarcoFalke: Right, ideally we would have the same... Let me write it down and think about it. Will reach out back to you. Most likely we just cache a fully-GC'd gnu_store 11:15 < luke-jr> wumpus: the only "demand" (more like expectation) is that it be usable without regressions before we switch to it exclusively.. and I've already said I'm willing to help, but I need to get to the point where I can 11:15 < sipa> MarcoFalke: well, let drahtbot do it and comment, rather than actual CI? 11:15 < MarcoFalke> on every pull? 11:15 < sipa> just master would be great already 11:16 < dongcarl> luke-jr: Will continue helping you set up like we've been doing this past 24 hrs :-) 11:16 < sipa> luke-jr: you don't run gitian in a VM (outside; i'm not talking about the VM gitian itself uses internally) 11:16 < sipa> ? 11:16 < luke-jr> sipa: not anymore, no; I got rid of that extra layer a while ago.. 11:16 < sipa> ok 11:16 < warren> gitian has optional VM or container mode 11:17 < luke-jr> (only did that at first because once upon a time gitian required Ubuntu IIRC) 11:17 < sipa> warren: i know; that's not what i'm talking about 11:17 < MarcoFalke> Maybe for ci we just use the closest version of mingw to guix that is offered by ubuntu/debian? 11:18 < dongcarl> MarcoFalke: I think it'll be easier to do the other way around 11:18 < dongcarl> I'll double-check, I think I made the Guix mingw build correspond to focal when I first set it up 11:19 < luke-jr> are we expecting CI to produce binaries that match Guix? O.o 11:19 < wumpus> no, just to run with the same version of the compiler to find relevant issues 11:19 < dongcarl> No, but I think similar behaviour is good 11:19 < MarcoFalke> luke-jr: Mostly to catch compiler errors before they are in the release 11:19 < wumpus> right 11:19 < dongcarl> I feel like I might have missed some comments up above, let me know if I did 11:20 < warren> dongcarl: "Most likely we just cache a fully-GC'd gnu_store" <--- Is this also the answer to my question above about offline operation? 11:20 < warren> Debian and Fedora require that for builds 11:20 < luke-jr> MarcoFalke: ultimately, I think a full Guix CI is needed to avoid that? 11:20 < dongcarl> warren: Could you detail what you want out of offline operations? 11:21 < MarcoFalke> luke-jr: I think that'd be tricky to set up, as we need to cache the full guix store 11:21 < MarcoFalke> (the part that we are using) 11:21 < luke-jr> MarcoFalke: just DrahtBot is enough..? it's not like we want *all* the CI to use the same compiler ideally 11:21 < sipa> warren: the gnu_store is the result of building all dependencies; i think with "offline operation" you're talking about the ability to fetch the sources beforehand, not the results (which implies trusted binaries) 11:22 < warren> dongcarl: for packaging Guix in Debian in Fedora we're required to bootstrap from source starting with the distro toolchains of those respective distros. The build process cannot download anything from the network so we must pre-populate any downloads that it would expect. The Debian packager added a ton of hacks to enable this to work offline for Debian guix bootstrap. 11:22 < sipa> warren: for CI trusted binaries are fine, we're just mimicking the release process 11:23 < warren> s/Debian in Fedora/Debian and Fedora/ 11:23 < dongcarl> warren: Right, I believe those hacks are still required for packing for Fedora. I believe the Debian maintainer just mentioned that he's slowly upstreaming this effort. 11:24 < luke-jr> warren: can you help with that after the meeting? ;) 11:24 < warren> It was unfortunate to learn that Guix does not have a goal of Guix itself being reproducible. 11:24 < dongcarl> I think w/re CI, let's get the versions as close as possible, and we will figure out a way to get a Guix-based CI working. 11:24 < dongcarl> warren: ? 11:25 < warren> dongcarl: the resulting Guix is not 100% identical to bootstrapped in a different way, reason being is reproducibility is not a goal of Guix, only bootstrapability. 11:26 < sipa> you mean the guix-daemon and guix binaries? 11:28 < dongcarl> If you're building Guix from source in $DISTRO, it's not going to be reproducible because $DISTRO's build tools are not reproducible. But once you have Guix built from source, you can reproduce Guix itself, and even challenge the binary tarball released on the Guix website. 11:28 < dongcarl> See: `guix challenge` and the last section of: https://guix.gnu.org/manual/en/html_node/Binary-Installation.html 11:28 < warren> OK thanks. 11:28 < wumpus> it could do a second pass for that? 11:28 < dongcarl> wumpus: Yup! `guix install guix` works (I think) 11:29 < sipa> we must go deeper. 11:29 < wumpus> like if you compile the compiler using the OS' build tools, then compile the compiler using that compiler, that one should be deterministic 11:29 < wumpus> ok 11:29 < dongcarl> :-) 11:29 < dongcarl> Any other concerns/questions? 11:30 < luke-jr> wumpus: Gentoo actually builds every GCC 3 times :p 11:30 < warren> Should a goal of bitcoin's release reproduce the bootstrap of guix and challenge? Or you expect guix to be already somehow bootstrapped on your own? 11:30 < sipa> warren: i think our goal should be reproducibility; the user can choose what level of trust they have in their own build process 11:31 < wumpus> agree with sipa 11:31 < phantomcircuit> luke-jr, i guess that's why it's so slow 11:31 < dongcarl> Exactly... Especially once Guix bridges into stage0... Bootstrap builds may take a week... 11:31 < sipa> if you guix, presumably you got it in a way you're comfortable with, and if you have that - regardless of how you did so - you can build a reproducible bitcoin core release binary 11:31 < sipa> +have 11:31 < wumpus> it's useful if some people taking part in builds bootstrap guix from ~nothing, but not everyone would need to do this to be useful 11:32 < luke-jr> I'm going to aim to have a gitian descriptor that produces a guix base with most deps at least 11:32 < warren> That'd be fine if Guix had an upstream supported way of doing it offline 11:32 < dongcarl> Guix boostrapping party leggoooo (just a bunch of nerds staring a build logs scrolling by) 11:32 < wumpus> hehe 11:33 < sipa> dongcarl: a bunch of geeks 11:33 < sipa> (that's how guix is pronounced, right?) 11:33 < dongcarl> warren: Let's open a dialogue with vagrantc, he has a full year's experience doing this for Debian and can answer more questions 11:33 < luke-jr> lol 11:33 < dongcarl> Haha yup! 11:33 < dongcarl> NOT goo-iks! 11:33 < warren> k 11:34 < sipa> building python 3.8.2, and guile 3.0.2 now, ... 11:34 < sipa> is there any kind of progress indicator? 11:34 < luke-jr> I'm still stuck on not allowing it to run a 3P bash :/ 11:34 < dongcarl> sipa: Yes if it thinks you are on a tty... I might have messed that up with all my nesting... 11:34 < sipa> luke-jr: yes, i'm sure we'll find a way around that 11:35 < dongcarl> luke-jr: Yeah let's talk afterwards 11:35 < sipa> dongcarl: it's printing what it's doing, and what it did; i don't know what it still has to do 11:35 < dongcarl> sipa: Yup, if it thinks it has a tty it'll print "what it still has to do" as well... A good UX improvement... Will note it down 11:36 < sipa> aH 11:36 < sipa> cool 11:36 < wumpus> that would be neat 11:37 < dongcarl> Any other qs/comments? 11:37 * jb551 ponders a nix guix build 11:38 < wumpus> if not, let's move to jonasschnelli's quick topic 11:38 < dongcarl> 👍 11:38 < jonatack> dongcarl: know that you had me at guile (and guix pronounced geeks) 11:38 < dongcarl> hehe 11:39 < jonasschnelli> I think it would be helpful to chime in on #16439 versus (or and) #20273 11:39 < gribble> https://github.com/bitcoin/bitcoin/issues/16439 | cli/gui: support "@height" in place of blockhash for getblock on client side by ajtowns · Pull Request #16439 · bitcoin/bitcoin · GitHub 11:39 < gribble> https://github.com/bitcoin/bitcoin/issues/20273 | Extend support for nested commands to bitcoin-cli by jonasschnelli · Pull Request #20273 · bitcoin/bitcoin · GitHub 11:39 < wumpus> #topic Nested commands vs @height macros (jonasschnelli) 11:39 < core-meetingbot> topic: Nested commands vs @height macros (jonasschnelli) 11:39 < jonasschnelli> I guess aj and I like to know what and to drag through the rebase hell 11:39 -!- TallTim_ [~TallTim@184-83-248-206-dynamic.midco.net] has joined #bitcoin-core-dev 11:39 < jonasschnelli> For me, nested commands in the cli would be pretty neat (and consistent with the GUI) 11:39 -!- jb551 is now known as jb55 11:40 < wumpus> nested commands in the cli would be great, all for that 11:40 < luke-jr> I don't think I'd use it, but why not 11:40 < achow101> why not both? 11:40 < wumpus> @height is basically a shorthand for nested commands, could be useful too dunno 11:40 -!- TallTim [~TallTim@184-83-248-206-dynamic.midco.net] has quit [Ping timeout: 240 seconds] 11:40 < jonasschnelli> yes. Both would work as well 11:40 < wumpus> eg @height would evaluate to the block hash right ? 11:40 < luke-jr> if both, it makes sense to implement @height using nested logic 11:40 < wumpus> i have no problems with anything as long as it's client side 11:40 < jonatack> i'd use 16439, thus my reviews 11:41 < luke-jr> just be sure @number doesn't turn into a hash in other contexts >_< 11:41 < jonasschnelli> @height could just translate into a nedted command 11:41 < luke-jr> eg tx comments 11:41 < jonasschnelli> preprocessing 11:41 < jonatack> yes, why not 11:42 -!- narodism [~narodnik@37.223.80.136] has quit [Read error: Connection reset by peer] 11:42 < jonasschnelli> If people think both (together) are viable, then we can continue rebasing it. 11:42 < jonasschnelli> But there was some lack of concept acks/nacks 11:42 < wumpus> i think nested should go in first 11:42 -!- narodism [~narodnik@37.223.80.136] has joined #bitcoin-core-dev 11:42 < luke-jr> jonasschnelli: what happens if I want to do a tx comment '@45123' or such? 11:43 < jonasschnelli> Yes. It's kind of the base 11:43 < wumpus> it's the most general and powerful 11:43 < sipa> the height thing should only trigger in arguments that are known to be block hashes? 11:43 < luke-jr> imo yes 11:43 < sipa> (which could be in the rpc tables) 11:43 < jonasschnelli> yes 11:43 < jonasschnelli> the descriptors are also a problem 11:43 < jonasschnelli> since they use bracket syntax 11:43 < jonasschnelli> but all solvable 11:44 < luke-jr> hrm 11:44 < sipa> yeah just restrict it to whitelisted fields 11:44 < jonasschnelli> yes. 11:44 < luke-jr> sipa: well, for nested in genreal.. 11:44 < sipa> and concept ack on having stuff like this on the client side 11:45 < jonasschnelli> cool. Let me enhance it then. 11:45 < jonasschnelli> (btw: its purely client side) 11:45 < jonatack> yes, iirc 16439 is gui-side and cli-side (with some duplication for now) 11:45 < luke-jr> does GUI currently have a problem with descriptors? 11:46 -!- jungly [~jungly@host-79-12-187-142.retail.telecomitalia.it] has joined #bitcoin-core-dev 11:46 < jonasschnelli> I don't recall but I think possibly 11:47 < jonasschnelli> no. it doesn't since its captured in quotes 11:50 < wumpus> anything else to discuss? 11:50 < wumpus> #endmeeting 11:50 < core-meetingbot> topic: Bitcoin Core development discussion and commit log | Feel free to watch, but please take commentary and usage questions to #bitcoin | Channel logs: http://www.erisian.com.au/bitcoin-core-dev/, http://gnusha.org/bitcoin-core-dev/ | Meeting topics http://gnusha.org/bitcoin-core-dev/proposedmeetingtopics.txt / http://gnusha.org/bitcoin-core-dev/proposedwalletmeetingtopics.txt 11:50 < core-meetingbot> Meeting ended Thu Feb 11 19:50:25 2021 UTC. 11:50 < core-meetingbot> Minutes: https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/2021/bitcoin-core-dev.2021-02-11-19.00.moin.txt 11:51 < luke-jr> dongcarl: warren: so anyway, I made gnu/packages/bootstrap/x86_64-linux and dropped my bash/mkdir/xz/tar bins there - but Guix is still trying to download the 3rd party blobs 11:56 < dongcarl> luke-jr: Are you running the Test Suite? 11:57 < dongcarl> luke-jr: Debian maintainer seems to think that only the test suite tries to clobber the 3rd party blobs 12:01 < jamesob> hi 12:01 < jamesob> Oh oops, timezones haha 12:03 < wumpus> heh 12:05 < luke-jr> dongcarl: no 12:05 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #bitcoin-core-dev 12:05 < luke-jr> per docs, I was trying to: guix install glibc-utf8-locales 12:14 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!] 12:25 -!- miketwenty1 [~miketwent@136.55.84.49] has joined #bitcoin-core-dev 12:29 -!- miketwenty1 [~miketwent@136.55.84.49] has quit [Remote host closed the connection] 12:29 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 12:30 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #bitcoin-core-dev 12:31 < luke-jr> fwiw, the answer we're getting in #guix appears to still be "you can't" (setup Guix without trusted third-party binaries) ☹ 12:33 -!- miketwenty1 [~miketwent@136.55.84.49] has joined #bitcoin-core-dev 12:35 -!- promag_ [~promag@188.250.84.129] has joined #bitcoin-core-dev 12:35 -!- promag [~promag@188.250.84.129] has quit [Read error: Connection reset by peer] 12:40 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Remote host closed the connection] 12:40 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-core-dev 12:40 -!- jungly [~jungly@host-79-12-187-142.retail.telecomitalia.it] has quit [Ping timeout: 256 seconds] 12:40 -!- miketwenty1 [~miketwent@136.55.84.49] has quit [Remote host closed the connection] 12:43 -!- TallTim_ [~TallTim@184-83-248-206-dynamic.midco.net] has quit [Quit: Textual IRC Client: www.textualapp.com] 12:44 -!- TallTim [~TallTim@184-83-248-206-dynamic.midco.net] has joined #bitcoin-core-dev 12:47 < sipa> dongcarl: https://0bin.net/paste/fvIHvwQZ#IQsNQpIOio4XTHyrYn8U21VZFFVL1VZKaS3NpPSyFrj 12:49 < dongcarl> sipa: Could you send me: /usr/local/var/log/guix/drvs/vh/phki5sg9xkdhh2pbc8gi6vhpfzryf0-gnutls-3.6.12.drv.gz 12:51 < dongcarl> luke-jr: Right, until wip-full-source-bootstrap is merged, building packages in Guix will require the binary seed. Which is smaller than the Ubuntu distro. 12:52 < sipa> dongcarl: https://0bin.net/paste/NF7n65Jb#HZRmfT-yTpLCEBoXolOpCLXdqotYDlES1q8vGKPcatC 12:52 < sipa> does that work? 12:52 < luke-jr> dongcarl: which makes Guix a suitable substittue for Ubuntu, but not gitian 12:54 -!- jonatack [~jon@37.173.153.89] has quit [Read error: Connection reset by peer] 12:54 -!- jonatack_ [~jon@37.173.153.89] has joined #bitcoin-core-dev 12:54 < dongcarl> sipa: No, I think 0bin mangles stuff... Could you pipe it to `bzcat` first? 12:55 * luke-jr wonders why 0bin requires cookies :/ 12:56 < sipa> dongcarl: https://0bin.net/paste/08lqkp9f#2Fw4RoP+qHZXlTB7EIRbDntA6BuMuQEO5dSALl7Rfdr 12:56 < gribble> https://github.com/bitcoin/bitcoin/issues/2 | Long-term, safe, store-of-value · Issue #2 · bitcoin/bitcoin · GitHub 13:02 < dongcarl> sipa: Ah I know this one, looking for best fix right now 13:04 -!- jonatack_ [~jon@37.173.153.89] has quit [Quit: jonatack_] 13:14 -!- harrigan [~harrigan@ptr-93-89-242-202.ip.airwire.ie] has quit [Read error: Connection reset by peer] 13:18 -!- dviola [~diego@unaffiliated/dviola] has quit [Quit: WeeChat 3.0] 13:18 < dongcarl> sipa: Okay this is due to a bug in Gnutls' test suite that tests a certificate, but that certificate expired on 2020-10-24. There's already a fix in Guix master upstream, which I will pull into my branch for our time-machine, but for now, this might work: 1. Disable NTP 2. Set your time to 2020-10-01 3. `guix build 13:18 < dongcarl> /gnu/store/vhphki5sg9xkdhh2pbc8gi6vhpfzryf0-gnutls-3.6.12.drv` (only builds gnutls) 4. re-enable NTP and check that your time is okay 13:19 -!- dviola [~diego@unaffiliated/dviola] has joined #bitcoin-core-dev 13:20 < dongcarl> Actually I think it's already fixed as of #21088... Will check 13:20 < gribble> https://github.com/bitcoin/bitcoin/issues/21088 | guix: Jump forwards in time-machine and adapt by dongcarl · Pull Request #21088 · bitcoin/bitcoin · GitHub 13:21 -!- harrigan [~harrigan@ptr-93-89-242-202.ip.airwire.ie] has joined #bitcoin-core-dev 13:23 < dongcarl> Yes, it's already fixed as of that time-machine jump :-) 13:23 < dongcarl> sipa: If my hack doesn't work, you may want to check out that PR 13:23 < sipa> ok, so i'll just checkout that branch 13:28 < dongcarl> sipa: Thanks for being patient with me as we work through these kinks, I am taking notes on the hiccups we run into :-) 13:29 < sipa> dongcarl: very welcome 13:29 -!- IGHOR [~quassel@176.121.4.135] has quit [Quit: http://quassel-irc.org ? ??????????? ?????????. ????-??.] 13:31 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 13:31 < bitcoin-git> [bitcoin] prayank23 closed pull request #21155: doc: Improve Tor docs (master...tor-docs-improve) https://github.com/bitcoin/bitcoin/pull/21155 13:31 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 13:32 -!- dermoth [~dermoth@unaffiliated/dermoth] has quit [Ping timeout: 240 seconds] 13:34 -!- jonatack [~jon@37.173.153.89] has joined #bitcoin-core-dev 13:34 -!- IGHOR [~quassel@176.121.4.135] has joined #bitcoin-core-dev 13:39 -!- dermoth [~dermoth@unaffiliated/dermoth] has joined #bitcoin-core-dev 13:41 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 13:45 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 13:45 < bitcoin-git> [bitcoin] prayank23 opened pull request #21157: doc: Improve Tor docs (master...tor-docs-add) https://github.com/bitcoin/bitcoin/pull/21157 13:45 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 13:58 < sipa> dongcarl: now it's trying to build macOS 13:59 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Quit: Leaving] 14:00 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Remote host closed the connection] 14:00 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 272 seconds] 14:00 -!- owowo [~ovovo@s91904428.blix.com] has joined #bitcoin-core-dev 14:00 -!- owowo [~ovovo@s91904428.blix.com] has quit [Changing host] 14:00 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 14:00 < jb55> sipa: that happened to me and I had to explicitly set HOSTS=x86_64-linux-gnu 14:01 < jb55> then again I haven't tried that PR so might be different issue 14:01 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-core-dev 14:02 -!- jacob84 [bc45c248@md-188-69-194-72.omni.lt] has joined #bitcoin-core-dev 14:02 -!- jacob84 [bc45c248@md-188-69-194-72.omni.lt] has quit [Client Quit] 14:03 -!- jacob63 [bc45c248@md-188-69-194-72.omni.lt] has joined #bitcoin-core-dev 14:04 -!- jacob63 [bc45c248@md-188-69-194-72.omni.lt] has quit [Client Quit] 14:10 -!- sipa_ [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-core-dev 14:12 -!- rex4539_ [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev 14:14 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Remote host closed the connection] 14:14 -!- sipa_ [~pw@gateway/tor-sasl/sipa1024] has quit [Client Quit] 14:18 -!- blackjid [~blackjid@195.140.213.38] has quit [Remote host closed the connection] 14:24 -!- Kiminuo [~Kiminuo@141.98.103.124] has quit [Ping timeout: 256 seconds] 14:31 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 268 seconds] 14:32 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev 14:34 -!- aricon1 [~aricon@195.140.213.38] has joined #bitcoin-core-dev 14:41 -!- wallet42____ [sid154231@gateway/web/irccloud.com/x-ihozpqrvbxpcilcr] has quit [Read error: Connection reset by peer] 14:41 -!- felixweis [sid154231@gateway/web/irccloud.com/x-ntdyaxjwaufomstj] has quit [Read error: Connection reset by peer] 14:41 -!- miketwenty1 [~miketwent@136.55.84.49] has joined #bitcoin-core-dev 14:41 -!- wangchun_ [sid444603@gateway/web/irccloud.com/x-xznnrtbggxdjkjro] has quit [Read error: Connection reset by peer] 14:41 -!- elichai2 [sid212594@gateway/web/irccloud.com/x-fnnnbfkbileowsih] has quit [Read error: Connection reset by peer] 14:41 -!- wallet42____ [sid154231@gateway/web/irccloud.com/x-bnqmyrnstbxbslmf] has joined #bitcoin-core-dev 14:41 -!- felixweis [sid154231@gateway/web/irccloud.com/x-uxvkkvzinlkyxlvm] has joined #bitcoin-core-dev 14:41 -!- wangchun_ [sid444603@gateway/web/irccloud.com/x-kszhzxjqgjaaiytr] has joined #bitcoin-core-dev 14:41 -!- elichai2 [sid212594@gateway/web/irccloud.com/x-ruscvhxdkxnvfepw] has joined #bitcoin-core-dev 14:45 -!- miketwenty1 [~miketwent@136.55.84.49] has quit [Ping timeout: 240 seconds] 14:59 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 14:59 < bitcoin-git> [bitcoin] jrawsthorne opened pull request #21158: lib: Add Taproot support to libconsensus (master...libconsensus_taproot) https://github.com/bitcoin/bitcoin/pull/21158 14:59 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 15:03 -!- rex4539_ [~rex4539@gateway/tor-sasl/rex4539] has quit [Remote host closed the connection] 15:11 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 15:29 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev 15:38 -!- ciccio [5d948908@net-93-148-137-8.cust.vodafonedsl.it] has joined #bitcoin-core-dev 15:38 -!- ciccio is now known as Guest64367 15:43 -!- Guest64367 [5d948908@net-93-148-137-8.cust.vodafonedsl.it] has quit [Ping timeout: 240 seconds] 15:48 -!- rc_423 [~r_423@cpe-75-185-100-189.cinci.res.rr.com] has quit [Remote host closed the connection] 15:49 -!- sdaftuar [~sdaftuar@gateway/tor-sasl/sdaftuar] has quit [Remote host closed the connection] 15:49 -!- rc_423 [~r_423@cpe-75-185-100-189.cinci.res.rr.com] has joined #bitcoin-core-dev 15:49 -!- sdaftuar [~sdaftuar@gateway/tor-sasl/sdaftuar] has joined #bitcoin-core-dev 15:50 -!- rc_423 [~r_423@cpe-75-185-100-189.cinci.res.rr.com] has quit [Read error: Connection reset by peer] 15:50 -!- rc_423 [~r_423@cpe-75-185-100-189.cinci.res.rr.com] has joined #bitcoin-core-dev 15:51 -!- rc_423 [~r_423@cpe-75-185-100-189.cinci.res.rr.com] has quit [Remote host closed the connection] 15:54 -!- rc_423 [~r_423@cpe-75-185-100-189.cinci.res.rr.com] has joined #bitcoin-core-dev 16:03 -!- ogo [~ogo@gateway/tor-sasl/ogo] has quit [Quit: Leaving] 16:04 -!- Randolf [~randolf@172.218.241.81] has joined #bitcoin-core-dev 16:08 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 16:32 -!- joelklabo [~textual@108-196-216-127.lightspeed.sntcca.sbcglobal.net] has quit [Quit: Textual IRC Client: www.textualapp.com] 16:43 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 16:44 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has quit [Ping timeout: 256 seconds] 16:46 -!- Evel-Knievel [~Evel-Knie@178-118-49-110.access.telenet.be] has joined #bitcoin-core-dev 16:47 -!- promag_ [~promag@188.250.84.129] has quit [Remote host closed the connection] 16:48 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 272 seconds] 16:50 -!- Evel-Knievel [~Evel-Knie@178-118-49-110.access.telenet.be] has quit [Read error: No route to host] 16:50 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has joined #bitcoin-core-dev 16:58 -!- kvaciral_ [~kvaciral@212.8.251.11] has joined #bitcoin-core-dev 17:00 -!- kvaciral [~kvaciral@212.8.251.11] has quit [Ping timeout: 240 seconds] 17:05 -!- jonatack [~jon@37.173.153.89] has quit [Ping timeout: 264 seconds] 17:08 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has quit [Remote host closed the connection] 17:08 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has joined #bitcoin-core-dev 17:22 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev 17:31 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has quit [Remote host closed the connection] 17:31 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has joined #bitcoin-core-dev 17:38 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Ping timeout: 268 seconds] 17:39 -!- narodism [~narodnik@37.223.80.136] has quit [Read error: Connection reset by peer] 17:40 -!- narodism [~narodnik@37.223.80.136] has joined #bitcoin-core-dev 17:40 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has quit [Ping timeout: 246 seconds] 17:47 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev 17:51 -!- ys0seri0us [75f7c56c@117.247.197.108] has joined #bitcoin-core-dev 17:58 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 18:01 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds] 18:05 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 18:12 -!- Randolf [~randolf@172.218.241.81] has quit [Quit: Leaving] 18:16 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 18:16 < bitcoin-git> [bitcoin] fanquake opened pull request #21159: test: fix sign comparison warning in socket tests (master...sign_compare_sock_tests) https://github.com/bitcoin/bitcoin/pull/21159 18:16 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 18:36 -!- narodism [~narodnik@37.223.80.136] has quit [Read error: Connection reset by peer] 18:37 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 18:37 -!- narodism [~narodnik@37.223.80.136] has joined #bitcoin-core-dev 18:42 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 268 seconds] 18:44 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev 18:45 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev 19:00 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-core-dev 19:02 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 264 seconds] 19:06 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 19:07 -!- rh0nj [~rh0nj@88.99.167.175] has joined #bitcoin-core-dev 19:14 -!- ys0seri0us [75f7c56c@117.247.197.108] has quit [Ping timeout: 240 seconds] 19:59 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 268 seconds] 20:24 -!- joelklabo [~textual@108-196-216-127.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev 20:35 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 20:38 -!- narodism [~narodnik@37.223.80.136] has quit [Read error: Connection reset by peer] 20:39 -!- narodism [~narodnik@37.223.80.136] has joined #bitcoin-core-dev 21:08 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 264 seconds] 21:55 -!- aricon1 [~aricon@195.140.213.38] has quit [Remote host closed the connection] 22:21 -!- binwiederhier1 [~binwieder@178.239.168.171] has joined #bitcoin-core-dev 22:33 -!- Kiminuo [~Kiminuo@141.98.103.124] has joined #bitcoin-core-dev 22:45 -!- Kiminuo [~Kiminuo@141.98.103.124] has quit [Ping timeout: 272 seconds] 22:54 -!- promag [~promag@188.250.84.129] has joined #bitcoin-core-dev 22:59 -!- promag [~promag@188.250.84.129] has quit [Ping timeout: 256 seconds] 23:05 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 23:11 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has joined #bitcoin-core-dev 23:17 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Ping timeout: 240 seconds] 23:20 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has quit [Ping timeout: 246 seconds] 23:22 -!- rh0nj [~rh0nj@88.99.167.175] has joined #bitcoin-core-dev 23:23 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has joined #bitcoin-core-dev 23:38 -!- mol_ [~mol@unaffiliated/molly] has quit [Read error: Connection reset by peer] 23:38 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-core-dev 23:38 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 23:46 -!- jungly [~jungly@host-79-54-255-196.retail.telecomitalia.it] has joined #bitcoin-core-dev 23:49 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-dev --- Log closed Fri Feb 12 00:00:27 2021