--- Log opened Thu Jan 20 00:00:35 2022
00:00 -!- rex4539_ [~rex4539@gateway/tor-sasl/rex4539] has quit [Quit: No Ping reply in 180 seconds.]
00:02 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
00:03 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
00:06 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te4q69sddkrvdfm.ipv6.telus.net] has quit [Ping timeout: 240 seconds]
00:15 -!- jesseposner [~jesse@c-24-5-105-39.hsd1.ca.comcast.net] has quit [Ping timeout: 250 seconds]
00:16 -!- _flood [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Remote host closed the connection]
00:17 -!- _flood [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
00:23 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
00:28 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 268 seconds]
00:30 -!- _flood [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 240 seconds]
00:36 -!- gleb7454 [~gleb@178.150.137.228] has joined #bitcoin-core-dev
00:57 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
01:00 -!- bitcoin_alien[m] [~bitcoinal@2001:470:69fc:105::1:5503] has quit [Quit: You have been kicked for being idle]
01:02 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 250 seconds]
01:14 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te4q69sddkrvdfm.ipv6.telus.net] has joined #bitcoin-core-dev
01:21 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Remote host closed the connection]
01:22 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
01:23 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Client Quit]
01:23 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
01:33 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
01:37 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Ping timeout: 256 seconds]
01:57 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
01:57 < bitcoin-git> [bitcoin] w0xlt opened pull request #24108: Replace RecursiveMutex `cs_addrLocal` with Mutex, and rename it (master...change_cs_addrLocal) https://github.com/bitcoin/bitcoin/pull/24108
01:57 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
01:59 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has joined #bitcoin-core-dev
02:00 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has quit [Client Quit]
02:02 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev
02:02 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has joined #bitcoin-core-dev
02:03 -!- kexkey [~kexkey@89.36.78.167] has quit [Ping timeout: 240 seconds]
02:05 -!- kexkey [~kexkey@89.36.78.183] has joined #bitcoin-core-dev
02:09 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
02:13 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 268 seconds]
02:17 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te4q69sddkrvdfm.ipv6.telus.net] has quit [Ping timeout: 240 seconds]
02:21 -!- jesseposner [~jesse@c-24-5-105-39.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
02:24 -!- arowser [~quassel@111.192.100.78] has joined #bitcoin-core-dev
02:44 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
02:48 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 240 seconds]
03:05 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te4q69sddkrvdfm.ipv6.telus.net] has joined #bitcoin-core-dev
03:10 -!- morcos_ [~morcos@gateway/tor-sasl/morcos] has joined #bitcoin-core-dev
03:12 -!- Aaronvan_ [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
03:12 -!- morcos [~morcos@gateway/tor-sasl/morcos] has quit [Ping timeout: 276 seconds]
03:12 -!- morcos_ is now known as morcos
03:13 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
03:14 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Ping timeout: 256 seconds]
03:25 -!- vysn [~vysn@user/vysn] has joined #bitcoin-core-dev
03:31 -!- paulo [paulo@user/paulo/x-9032687] has quit [Ping timeout: 256 seconds]
03:32 -!- meshcollider [meshcollid@user/meshcollider] has quit [Ping timeout: 256 seconds]
03:43 < michaelfolkson> fanquake: Thanks for the blocking notifications
04:08 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te4q69sddkrvdfm.ipv6.telus.net] has quit [Ping timeout: 250 seconds]
04:12 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Ping timeout: 276 seconds]
04:24 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has quit [Quit: ZzzZ]
04:24 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
04:44 -!- arowser [~quassel@111.192.100.78] has quit [Remote host closed the connection]
04:55 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:02 -!- Dezzy [~Dezzy@197.210.28.213] has joined #bitcoin-core-dev
05:13 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te6wy8l4pph467h.ipv6.telus.net] has joined #bitcoin-core-dev
05:25 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Remote host closed the connection]
05:29 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
05:35 -!- pergaminho [~pergaminh@user/pergaminho] has joined #bitcoin-core-dev
05:39 -!- _flood [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
05:41 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
05:41 < bitcoin-git> [bitcoin] fanquake opened pull request #24111: build: force CRCCheck in Windows installer (master...force_win_installer_crccheck) https://github.com/bitcoin/bitcoin/pull/24111
05:41 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
05:41 -!- Guest57 [~Guest57@103.39.242.109] has joined #bitcoin-core-dev
05:42 -!- Guest57 [~Guest57@103.39.242.109] has quit [Client Quit]
05:59 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
05:59 < bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/63fc2f5cce6a...1824644a363b
05:59 < bitcoin-git> bitcoin/master a7da140 w0xlt: scripted-diff: rename cs_mapLocalHost -> g_maplocalhost_mutex
05:59 < bitcoin-git> bitcoin/master 5e7e4c9 w0xlt: refactor: replace RecursiveMutex g_maplocalhost_mutex with Mutex
05:59 < bitcoin-git> bitcoin/master 1824644 MarcoFalke: Merge bitcoin/bitcoin#24099: Replace `RecursiveMutex cs_mapLocalHost` with...
05:59 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
05:59 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
05:59 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #24099: Replace `RecursiveMutex cs_mapLocalHost` with Mutex, and rename it (master...mutex-mapLocalHost) https://github.com/bitcoin/bitcoin/pull/24099
05:59 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:00 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Remote host closed the connection]
06:04 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
06:08 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 250 seconds]
06:15 -!- Dezzy [~Dezzy@197.210.28.213] has quit [Quit: Ping timeout (120 seconds)]
06:15 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te6wy8l4pph467h.ipv6.telus.net] has quit [Ping timeout: 240 seconds]
06:32 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
06:32 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Remote host closed the connection]
06:34 -!- Nikhil [~Nikhil@2402:3a80:196b:e0b7:f33a:469d:772f:98ad] has joined #bitcoin-core-dev
06:35 -!- Nikhil23 [~Nikhil@2402:3a80:196b:e0b7:f33a:469d:772f:98ad] has joined #bitcoin-core-dev
06:36 -!- Nikhil23 [~Nikhil@2402:3a80:196b:e0b7:f33a:469d:772f:98ad] has quit [Client Quit]
06:36 -!- Nikhil09 [~Nikhil09@2402:3a80:196b:e0b7:f33a:469d:772f:98ad] has joined #bitcoin-core-dev
06:36 -!- Nikhil09 [~Nikhil09@2402:3a80:196b:e0b7:f33a:469d:772f:98ad] has quit [Client Quit]
06:36 -!- Nikhil [~Nikhil@2402:3a80:196b:e0b7:f33a:469d:772f:98ad] has quit [Client Quit]
06:40 -!- Guest15 [~Guest15@static.184.157.181.135.clients.your-server.de] has joined #bitcoin-core-dev
06:46 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te6wy8l4pph467h.ipv6.telus.net] has joined #bitcoin-core-dev
06:48 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
06:49 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:49 < bitcoin-git> [bitcoin] fanquake opened pull request #24112: build: pass win32-dll to LT_INIT() (master...libtool_init_win32_dll) https://github.com/bitcoin/bitcoin/pull/24112
06:49 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:49 -!- kabaum [~kabaum@h-46-59-13-35.A163.priv.bahnhof.se] has joined #bitcoin-core-dev
06:49 < hebasto> nice to see how #19303 is being fulfilled
06:49 <@gribble> https://github.com/bitcoin/bitcoin/issues/19303 | Replace all of the RecursiveMutex instances with the Mutex ones · Issue #19303 · bitcoin/bitcoin · GitHub
06:50 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te6wy8l4pph467h.ipv6.telus.net] has quit [Ping timeout: 250 seconds]
06:52 -!- grettke [~grettke@cpe-65-29-228-30.wi.res.rr.com] has joined #bitcoin-core-dev
06:52 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te6wy8l4pph467h.ipv6.telus.net] has joined #bitcoin-core-dev
06:53 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 250 seconds]
06:53 -!- kabaum [~kabaum@h-46-59-13-35.A163.priv.bahnhof.se] has quit [Ping timeout: 250 seconds]
06:56 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te6wy8l4pph467h.ipv6.telus.net] has quit [Ping timeout: 240 seconds]
07:09 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te6wy8l4pph467h.ipv6.telus.net] has joined #bitcoin-core-dev
07:12 < theStack_> hebasto: indeed \o/ will be tough when it comes to cs_main, the final boss
07:14 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
07:14 < bitcoin-git> [bitcoin] jonatack opened pull request #24113: test, refactor: add GetTransaction() coverage, part 2 (master...rpc_rawtransaction-test-followups) https://github.com/bitcoin/bitcoin/pull/24113
07:14 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
07:23 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
07:27 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 240 seconds]
07:39 -!- jb55 [~jb55@user/jb55] has joined #bitcoin-core-dev
07:40 -!- jarthur [~jarthur@cpe-70-114-198-37.austin.res.rr.com] has joined #bitcoin-core-dev
07:41 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te6wy8l4pph467h.ipv6.telus.net] has quit [Remote host closed the connection]
07:41 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te6wy8l4pph467h.ipv6.telus.net] has joined #bitcoin-core-dev
07:52 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
08:01 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Remote host closed the connection]
08:02 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
08:04 -!- Guest15 [~Guest15@static.184.157.181.135.clients.your-server.de] has quit [Ping timeout: 256 seconds]
08:16 -!- Guyver2_ [Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev
08:19 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has quit [Ping timeout: 256 seconds]
08:19 -!- Guyver2_ is now known as Guyver2
08:30 -!- Guest [~Guest@223.233.78.191] has joined #bitcoin-core-dev
08:31 -!- salvatoshi [~salvatosh@genymobile-2-6-86.fib.nerim.net] has quit [Ping timeout: 250 seconds]
08:31 -!- gleb7454 [~gleb@178.150.137.228] has quit [Ping timeout: 256 seconds]
08:31 -!- Guest [~Guest@223.233.78.191] has quit [Client Quit]
08:43 -!- jb55 [~jb55@user/jb55] has quit [Ping timeout: 256 seconds]
08:43 -!- michagogo [uid14316@user/michagogo] has joined #bitcoin-core-dev
08:52 -!- salvatoshi [~salvatosh@lfbn-idf3-1-717-248.w86-252.abo.wanadoo.fr] has joined #bitcoin-core-dev
08:57 -!- gleb7454 [~gleb@178.150.137.228] has joined #bitcoin-core-dev
09:06 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Remote host closed the connection]
09:07 -!- Guest15 [~Guest15@static.184.157.181.135.clients.your-server.de] has joined #bitcoin-core-dev
09:08 -!- Guest15 [~Guest15@static.184.157.181.135.clients.your-server.de] has quit [Client Quit]
09:12 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
09:12 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/1824644a363b...b60c477d54bb
09:12 < bitcoin-git> bitcoin/master faedb11 MarcoFalke: refactor tests to fix ubsan suppressions
09:12 < bitcoin-git> bitcoin/master b60c477 MarcoFalke: Merge bitcoin/bitcoin#23629: refactor tests to fix ubsan suppressions
09:12 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
09:12 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
09:12 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #23629: refactor tests to fix ubsan suppressions (master...2111-testInt) https://github.com/bitcoin/bitcoin/pull/23629
09:12 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
09:13 -!- gleb74543 [~gleb@178.150.137.228] has joined #bitcoin-core-dev
09:13 -!- gleb7454 [~gleb@178.150.137.228] has quit [Ping timeout: 256 seconds]
09:13 -!- gleb74543 is now known as gleb7454
09:15 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
09:21 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
09:22 -!- Kaizen_K_ [~Kaizen_Ki@d137-186-173-166.abhsia.telus.net] has joined #bitcoin-core-dev
09:22 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te6wy8l4pph467h.ipv6.telus.net] has quit [Ping timeout: 240 seconds]
09:23 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
09:23 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
09:28 -!- gleb7454 [~gleb@178.150.137.228] has quit [Ping timeout: 240 seconds]
09:42 -!- salvatoshi [~salvatosh@lfbn-idf3-1-717-248.w86-252.abo.wanadoo.fr] has quit [Ping timeout: 240 seconds]
09:42 -!- jb55 [~jb55@user/jb55] has joined #bitcoin-core-dev
09:43 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
09:43 < bitcoin-git> [bitcoin] achow101 pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/b60c477d54bb...e3ce019667fb
09:43 < bitcoin-git> bitcoin/master 36012ef Antoine Poinsot: qa: test descriptors with mixed xpubs and const pubkeys
09:43 < bitcoin-git> bitcoin/master e3ce019 Andrew Chow: Merge bitcoin/bitcoin#23171: qa: test descriptors with mixed xpubs and con...
09:43 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
09:44 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
09:44 < bitcoin-git> [bitcoin] achow101 merged pull request #23171: qa: test descriptors with mixed xpubs and const pubkeys (master...desc_test_mix) https://github.com/bitcoin/bitcoin/pull/23171
09:44 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
09:51 -!- drnet [~drnet@178.197.235.244] has joined #bitcoin-core-dev
09:51 -!- kabaum [~kabaum@h-46-59-13-35.A163.priv.bahnhof.se] has joined #bitcoin-core-dev
09:54 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev
09:57 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Remote host closed the connection]
09:57 -!- kabaum [~kabaum@h-46-59-13-35.A163.priv.bahnhof.se] has quit [Ping timeout: 256 seconds]
10:03 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 240 seconds]
10:03 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
10:08 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Ping timeout: 256 seconds]
10:10 -!- kabaum [~kabaum@h-46-59-13-35.a163.priv.bahnhof.se] has joined #bitcoin-core-dev
10:14 -!- Kaizen_K_ [~Kaizen_Ki@d137-186-173-166.abhsia.telus.net] has quit [Remote host closed the connection]
10:15 -!- kabaum [~kabaum@h-46-59-13-35.a163.priv.bahnhof.se] has quit [Ping timeout: 256 seconds]
10:15 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te66oclonkh96li.ipv6.telus.net] has joined #bitcoin-core-dev
10:17 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
10:17 < bitcoin-git> [bitcoin] prusnak opened pull request #24115: ARMv8 SHA2 Intrinsics (master...armv8-shani) https://github.com/bitcoin/bitcoin/pull/24115
10:17 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
10:19 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te66oclonkh96li.ipv6.telus.net] has quit [Ping timeout: 250 seconds]
10:28 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Remote host closed the connection]
10:29 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
10:34 -!- gleb74543 [~gleb@178.150.137.228] has joined #bitcoin-core-dev
10:37 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
10:38 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te66oclonkh96li.ipv6.telus.net] has joined #bitcoin-core-dev
10:41 -!- Lightsword [~Lightswor@user/lightsword] has quit [Ping timeout: 256 seconds]
10:42 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 268 seconds]
10:44 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
10:46 -!- Lightsword [~Lightswor@user/lightsword] has joined #bitcoin-core-dev
11:00 -!- b10c_ is now known as b10c
11:01 < laanwj> #startmeeting
11:01 < core-meetingbot`> Meeting started Thu Jan 20 19:01:22 2022 UTC.  The chair is laanwj. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings.
11:01 < core-meetingbot`> Available commands: action commands idea info link nick
11:01 < sipsorcery> hi
11:01 < b10c> hi
11:01 < laanwj> #bitcoin-core-dev Meeting: achow101 _aj_ amiti ariard BlueMatt cfields Chris_Stewart_5 darosior digi_james dongcarl elichai2 emilengler fanquake fjahr gleb glozow gmaxwell gwillen hebasto instagibbs jamesob jarolrod jb55 jeremyrubin jl2012 jnewbery jonasschnelli jonatack jtimon kallewoof kanzure kvaciral laanwj larryruane lightlike luke-jr maaku marcofalke meshcollider michagogo moneyball
11:01 < laanwj> morcos nehan NicolasDorier paveljanik petertodd phantomcircuit promag provoostenator ryanofsky sdaftuar sipa vasild
11:01 < hebasto> hi
11:01 < jonatack> hi
11:01 < MarcoFalke> hi
11:01 < achow101> hi
11:01 < _aj_> hi
11:01 < lightlike> hi
11:02 < kvaciral[m]> hi
11:02 < laanwj> hi
11:02 < laanwj> it looks like there have been no proposed meeting topics this week (this can be done using #proposedmeetingtopic <topic>), any last-minute ones?
11:02 < jarolrod> Hi
11:03 < jeremyrubin> hi
11:03 < sipa> hi
11:04 < laanwj> #topic High priority for review
11:04 < core-meetingbot`> topic: High priority for review
11:05 < MarcoFalke> Can I have #23438 pls
11:05 < laanwj> https://github.com/bitcoin/bitcoin/projects/8  : 9 blockers, 1 chasing concept ACK
11:05 <@gribble> https://github.com/bitcoin/bitcoin/issues/23438 | refactor: Use spans of std::byte in serialize by MarcoFalke · Pull Request #23438 · bitcoin/bitcoin · GitHub
11:06 < laanwj> MarcoFalke: added
11:06 < MarcoFalke> thx
11:06 < cfields> hi
11:08 < laanwj> anything else to add/remove, or is anything ready for merge?
11:09 < _aj_> i think #23508 is rfm but it needs a few more acks :)
11:09 <@gribble> https://github.com/bitcoin/bitcoin/issues/23508 | Add getdeploymentinfo RPC by ajtowns · Pull Request #23508 · bitcoin/bitcoin · GitHub
11:09 < jonatack> #23604 had 4 ACKs before the last rebase, should be close
11:09 <@gribble> https://github.com/bitcoin/bitcoin/issues/23604 | Use Sock in CNode by vasild · Pull Request #23604 · bitcoin/bitcoin · GitHub
11:09 < laanwj> ah yes #23604 should definitely be close, and #23508 too
11:09 <@gribble> https://github.com/bitcoin/bitcoin/issues/23604 | Use Sock in CNode by vasild · Pull Request #23604 · bitcoin/bitcoin · GitHub
11:09 <@gribble> https://github.com/bitcoin/bitcoin/issues/23508 | Add getdeploymentinfo RPC by ajtowns · Pull Request #23508 · bitcoin/bitcoin · GitHub
11:10 -!- bomb-on [~bomb-on@194.144.47.113] has joined #bitcoin-core-dev
11:10 < jonatack> #22932 had acks by hebasto, achow101 and vasild. I updated it to take review feedback, re-acks welcome
11:10 <@gribble> https://github.com/bitcoin/bitcoin/issues/22932 | Add CBlockIndex lock annotations, guard nStatus/nFile/nDataPos/nUndoPos by cs_main by jonatack · Pull Request #22932 · bitcoin/bitcoin · GitHub
11:11 < fjahr> hi
11:11 < jonatack> it now contains a few commits by hebasto and vasild
11:11 -!- rottenstonks_ [~rottensto@user/rottenstonks] has joined #bitcoin-core-dev
11:11 < jonatack> will look at #23508
11:11 <@gribble> https://github.com/bitcoin/bitcoin/issues/23508 | Add getdeploymentinfo RPC by ajtowns · Pull Request #23508 · bitcoin/bitcoin · GitHub
11:11 < laanwj> great!
11:12 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
11:12 < fjahr> already started reviewing #23508, should be done soon as well
11:12 <@gribble> https://github.com/bitcoin/bitcoin/issues/23508 | Add getdeploymentinfo RPC by ajtowns · Pull Request #23508 · bitcoin/bitcoin · GitHub
11:13 -!- rottenstonks_ is now known as rottenstonks
11:14 < laanwj> any other topics?
11:15 < _aj_> is the 23.0 milestone up to date?
11:15 < jeremyrubin> if there's nothing else i think it's interesting to talk about making a style-change epoch after split-off 
11:16 < laanwj> _aj_: i don't know, do you see anything off?
11:16 < laanwj> style change epoch? oh no...
11:16 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 250 seconds]
11:16 < _aj_> laanwj: just wonering if i should go through that a few times before feature freeze
11:16 < MarcoFalke> Yeah, let us know if anything is missing from it or should be removed
11:16 -!- Guest21 [~Guest21@dynamic-190-25-170-252.dynamic.etb.net.co] has joined #bitcoin-core-dev
11:17 < MarcoFalke> https://github.com/bitcoin/bitcoin/milestone/52 
11:18 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!]
11:19 < laanwj> #topic Style change after split-off (jeremyrubin)
11:19 < core-meetingbot`> topic: Style change after split-off (jeremyrubin)
11:19 < jeremyrubin> see #22969
11:19 <@gribble> https://github.com/bitcoin/bitcoin/issues/22969 | Release schedule for 23.0 · Issue #22969 · bitcoin/bitcoin · GitHub
11:19 < jeremyrubin> the concept would be that after split off for T days bigger cleanups can be prioritized
11:20 < jeremyrubin> and then after T days, cleanups would not really be considered
11:20 < laanwj> not a fan of all-over-the-place changes that break every other PR just for style's sake tbh
11:20 < sipa> concept nack in general on invasive style changes
11:20 < laanwj> yeah
11:20 < jeremyrubin> this is to allow for cleanups while minimizing rebase work
11:20 < sipa> refactors that are useful for other reasons... sure, on a case-by-case basis
11:20 < laanwj> not sure anyone cares anymore but we used to not do this and i think for good reason
11:20 < jeremyrubin> i am nack on the invasive changes as well, but it seems people do continually want things like changing all C style casts 
11:21 < laanwj> nack on the casts change, not only is it invasive it's risky
11:21 < _aj_> https://github.com/bitcoin/bitcoin/issues/15465 maybe relevant history/context
11:21 < jeremyrubin> or things like moving class A from file X to file Y to clean a linker supression
11:22 < _aj_> personally i like/prefer the "do useful work, and clean up as you go" approach that we're already doing
11:22 < laanwj> you mean breaking circular dependencies? yeah, that can be valid
11:22 < MarcoFalke> [20:20] <sipa> refactors that are useful for other reasons... sure, on a case-by-case basis
11:22 < jeremyrubin> e.g. #17786
11:22 < MarcoFalke> Agree with sipa that this is a case-by-case decision
11:22 <@gribble> https://github.com/bitcoin/bitcoin/issues/17786 | refactor: Nuke policy/fees->mempool circular dependencies by hebasto · Pull Request #17786 · bitcoin/bitcoin · GitHub
11:22 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te66oclonkh96li.ipv6.telus.net] has quit [Read error: Connection reset by peer]
11:22 < sipa> aj: agreew
11:22 < laanwj> i don't see that as much of a style thing
11:23 < jeremyrubin> well the point would more be to still do these things when they make sense, but contain it to a minimally disruptive part of the release cycle
11:23 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te66oclonkh96li.ipv6.telus.net] has joined #bitcoin-core-dev
11:23 < laanwj> circular dependencies are just bad design
11:23 < jeremyrubin> laanwj: but you can see how that's very disruptive for rebasing
11:23 < laanwj> sure
11:23 < jeremyrubin> so the point of a cleanup epoch would be to do cleanups like that only in e.g. the first month after split off
11:23 < _aj_> it's maximally disruptive for anything we want to backport to the latest release though?
11:24 < MarcoFalke> jeremyrubin: Why would a specific epoch be minimally disruptive? I'd say it depends on the case
11:24 < sipa> I conceptually agree that there are better/worse times to make invasive changes (assuming they're justified)... but they also have to be ready at that point.
11:24 < jeremyrubin> yeah i'm not tied to a specific time
11:24 < sipa> And indeed, when that is depends on the case.
11:24 < MarcoFalke> If you are touching a part of the code that no one else is touching, then the time doesn't matter
11:24 < jeremyrubin> just thinking that it might be something that leads to less contributor frustration
11:25 < jeremyrubin> if people who work on these things know when it is appropriate and people who don't don't have to argue for not merging a conflict
11:25 < MarcoFalke> If you are touding a part of the code that is touched by others, then you'll have to order the changes anyway
11:25 < sipa> Right, but the risk is that we designate a specific timeframe for refactors... and then we get a torrent of refactors in that time that all conflict with each other.
11:26 < jeremyrubin> possibly. although it's not clear it's a bigger problem than as is v.s. just more apparent 
11:27 < jeremyrubin> if we queue up the refactors and people discuss them before investing time maybe that can help mitigate it
11:27 < MarcoFalke> I'd also expect it will be harder to find reviewers if there is a time pressure/specific time slot
11:28 -!- mode/#bitcoin-core-dev [-b *!*@103.131.239.33] by ChanServ
11:28 < jonatack> seems best to remain ad hoc about it (as it is currently)
11:29 < MarcoFalke> If you are worries about invensting time, you can also ask during the meeting if the concept makes sense (or in an issue)
11:29 < jeremyrubin> i guess so, it seems sad though because i think it does contribute to burn out and frustration.
11:30 < jeremyrubin> i dont spend time on refactors like this anymore afaik so not really concerned for me
11:30 < MarcoFalke> Generally writing code is trivial compared to reading and reviewing not so
11:30 < MarcoFalke> s/not so//g
11:30 < jeremyrubin> i think the main benefit is for people not working on these
11:31 < jeremyrubin> If i have a feature/improvement X and there is also a refactor Y in the pipe that would confilict does it makes sense for me to refactor/rebase X?
11:31 < jeremyrubin> If I knew that the cleanup work would not pre-empt, i might spend time more actively on X rather than speculating on Y
11:31 < jonatack> one can make the argument that adding process can contribute to dev frustration as well
11:32 < jeremyrubin> jonatack: good point, process ==bureaucracy, however, it also leads to getting a clear answer on when or how something can proceed 
11:33 < sipa> I think most frustration is simply due to lack of review feedback. I don't think that designating times for certain kinds of changes will improve that (and it may even work the other way around... "I was told this was the time for this kind of change, and I *still* don't get feedback!?")
11:33 < jeremyrubin> i personally favor clear answers v.s. unclear ones
11:33 < MarcoFalke> If you think that X should go before Y (or the other way round), you should say so in a review comment
11:33 < _aj_> drahtbot already says that when it reports conflicting prs
11:34 < jeremyrubin> _aj_ afaict drahbot doesn't analyze for merge order, just for conflicts
11:34 < jeremyrubin> and it's buggy w.r.t. silent conflicts
11:34 < _aj_> jeremyrubin: no it tells you to figure out which one should go first
11:34 < jeremyrubin> (err unsolvable)
11:34 < MarcoFalke> Jup, it was the intention behind the comment to focus reviewers on one of the conflicts
11:35 < MarcoFalke> DrahtBot re-runs all CI every 9 days, so (some) silent conflicts are now detected
11:35 < laanwj> that's good!
11:35 < jeremyrubin> anyhow it sounds like most people are happy with the status quo on this stuff so it's not a hill i'd die on
11:35 < MarcoFalke> DrahtBot can't tell you which order to merge. This is up to the reviewers
11:36 < sipa> I wouldn't say I'm happy - the frustration you speak of, and the impact on contributors is certainly real. I however don't think your suggestion will improve it.
11:36 < MarcoFalke> I mean frustration is certainly real, but I think a "refactor window" is not a clear and trivial to solve that.
11:36 < lightlike> seems in practice it's more up to the maintainers - I rarely see discussions about merge order amongst reviewers
11:36 < laanwj> it would be an indication to the maintainers
11:37 < MarcoFalke> lightlike: It is implicit in where people put their ACKs
11:37 < jeremyrubin> sipa: fair, i'm not tied to any specific suggestion. is there something else you think might be an improvement? 
11:37 < sipa> I'm afraid I don't have concrete suggestions.
11:37 < laanwj> it definitely happens that someone asks for something to be merged before/after another PR
11:38 < jeremyrubin> is this a harmful thing to try over e.g. 2 releases?
11:38 < laanwj> not often, but it's also not often necessary
11:38 < jeremyrubin> or do we feel confident the problems would exceed the benefit?
11:39 < jeremyrubin> i'm all for trying something if the status quo isn't happy and if it doesnt help trying something else
11:39 < laanwj> that kind of coordination tends to be pretty hard to do in this project tbh
11:40 < sipa> I think it's such a case-by-case thing that trying to institute a process for it isn't helpful.
11:40 < MarcoFalke> Jup, would be hard to announce that the next 12 days from today are the "refactor window" and explain what that even means in practice
11:41 < _aj_> are there any refactoring tools that make it easy to see "oh you're just changing from Foo* x and x->bar to Foo& x and x.bar" these days?
11:42 < jeremyrubin> scripted-diff?
11:42 < MarcoFalke> "--word-diff-regex=." ?
11:42 < _aj_> i mean syntax aware, rather than textual
11:42 < jeremyrubin> there's no tooling for AFAIU testing a scripted diff against all current reported conflicting branches
11:43 < MarcoFalke> _aj_: You can write one based on https://github.com/llvm-mirror/clang/blob/master/tools/clang-diff/ClangDiff.cpp ;)
11:43 < _aj_> syntax aware can see I'm changing Foo::bar to Foo::m_bar and see that Baz::bar is unrelated while scripted-diff generally can't eg
11:44 < laanwj> syntax/structure aware refactoring tools for c++ are really difficult to do, people have been trying for decades at least
11:44 < laanwj> i think clang has some tooling nowadays but it's eally fiddly
11:45  * MarcoFalke Let's use clang-refactor in a scripted-diff *hides
11:45 < laanwj> for easier to parse languages like java it's quite common
11:45 < laanwj> lol
11:46 < laanwj> any other topics?
11:46 < _aj_> MarcoFalke: yes, exactly! thanks!
11:46 < laanwj> #endmeeting
11:46 < 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:46 < core-meetingbot`> Meeting ended Thu Jan 20 19:46:54 2022 UTC.  
11:46 < core-meetingbot`> Minutes:        https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/2022/bitcoin-core-dev.2022-01-20-19.01.moin.txt
11:49 -!- drnet [~drnet@178.197.235.244] has quit [Quit: Leaving]
11:50 < jonatack>  i've found a good cure for wanting more process is to go into consulting or industry and work on a process/buzzword/ritual-heavy agile/scrum software project :)
11:51 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has joined #bitcoin-core-dev
11:52 < jeremyrubin> noted
11:52 < jeremyrubin> hey random question, how does https://en.cppreference.com/w/cpp/thread/call_once work?
11:52 < sipa> What do you mean by "how"?
11:52 < jeremyrubin> oh nvm
11:52 < jeremyrubin> i get it now
11:53 < jeremyrubin> i missed you have to pass in your own atomic flag
11:53 -!- michagogo [uid14316@user/michagogo] has quit [Quit: Connection closed for inactivity]
11:53 < jeremyrubin> but still, kinda curious how the flag works practically with exception handling mostly
11:54 < sipa> An `std::once_flag` could theoretically be simpler than an `std::atomic<bool>`, as it needs no means of going back from true to false.
11:54 < jeremyrubin> well in this case the call_once permits functions that throw
11:54 < jeremyrubin> and the others get 'queued up'
11:55 < jeremyrubin> and then released once the call finishes sucessfully
11:55 < jeremyrubin> and then all side effects can be seen
11:55 < jeremyrubin> byt the other callers
11:56 -!- Guest21 [~Guest21@dynamic-190-25-170-252.dynamic.etb.net.co] has left #bitcoin-core-dev []
11:57 < sipa> It doesn't sound hard to implement that using a mutex and a condition variable.
11:57 < jeremyrubin> yeah but this is just using an atomic flag
11:57 < sipa> Though I suspect most platforms offer far more efficient ways of accomplishing that (pthreads has a primitive for it, I think).
11:57 < jeremyrubin> ah ok
11:58 < jeremyrubin> would it be totally wild to use this in rewriting some of the caching logic for CTV to be cache-on-first-use?
11:58 < sipa> I have no opinion on that.
11:59 < jeremyrubin> no concerns about using call_once at all from consensus/script interpreter code?
12:02 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
12:07 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 268 seconds]
12:16 -!- kabaum [~kabaum@185.213.154.240] has joined #bitcoin-core-dev
12:18 -!- vysn [~vysn@user/vysn] has quit [Ping timeout: 240 seconds]
12:33 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit []
12:34 -!- MarcoFalke [~none@198.12.116.246] has quit [Ping timeout: 245 seconds]
12:35 -!- rottenstonks_ [~rottensto@user/rottenstonks] has joined #bitcoin-core-dev
12:37 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
12:38 -!- rottenstonks [~rottensto@user/rottenstonks] has quit [Ping timeout: 256 seconds]
12:42 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 240 seconds]
12:44 -!- ZeroMaster [~webirc@95-42-105-42.ip.btc-net.bg] has quit [Read error: Connection reset by peer]
12:51 -!- jarthur [~jarthur@cpe-70-114-198-37.austin.res.rr.com] has quit [Read error: Connection reset by peer]
12:52 -!- Guest49 [~Guest49@80.71.136.204.ipv4.parknet.dk] has joined #bitcoin-core-dev
12:52 -!- Guest49 [~Guest49@80.71.136.204.ipv4.parknet.dk] has quit [Client Quit]
12:56 -!- jarthur [~jarthur@2603-8080-1540-002d-dc67-681f-ccd6-3dd0.res6.spectrum.com] has joined #bitcoin-core-dev
12:57 -!- MarcoFalke [~none@198.12.116.246] has joined #bitcoin-core-dev
13:04 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has quit [Ping timeout: 256 seconds]
13:11 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
13:16 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Ping timeout: 250 seconds]
13:18 < jeremyrubin> is there a convenient way to attach GDB from a functional test?
13:19 < jeremyrubin> i want to test the node, not the test
13:26 < achow101> jeremyrubin: you can pause the test with pdb, then attach gdb to the pid of the bitcoind you want to debug
13:26 < achow101> there's a doc somewhere describing how to do this
13:27 -!- pergaminho [~pergaminh@user/pergaminho] has quit []
13:30 < achow101> jeremyrubin: https://gist.github.com/fjahr/2cd23ad743a2ddfd4eed957274beca0f#debugging-from-functional-tests (substitute lldb with gdb, it should work)
13:33 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te66oclonkh96li.ipv6.telus.net] has quit [Remote host closed the connection]
13:33 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te66oclonkh96li.ipv6.telus.net] has joined #bitcoin-core-dev
13:35 < jeremyrubin> yeah makes sense... maybe i will add a flag for it 
13:35 < jeremyrubin> key word "convenient" :)
13:36 < jeremyrubin> maybe some shell aliases or smth
13:36 < achow101> you could probably shell alias it
13:36 < achow101> although that might be more difficult if the test has multiple nodes and you are trying to debug a specific one
13:38 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te66oclonkh96li.ipv6.telus.net] has quit [Ping timeout: 240 seconds]
13:38 < cfields> jeremyrubin: there's also --wait_for_debugger
13:38 < cfields> Oh, whoops, functional. nm.
13:45 < jeremyrubin> problem chased down anyways... another victim to a =default constructor lol
13:46 < jeremyrubin> still may patch a way to have the node run in debugger of choice and drop to a console on fault
13:46 < jeremyrubin> is that something anyone else would like? test.py --with-debugger=lldb|gdb?
13:48 < sipa> That sounds useful. But how do you control which node gets debugged?
13:51 -!- sudoforge [~sudoforge@wireguard/tunneler/sudoforge] has joined #bitcoin-core-dev
13:58 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
13:58 < bitcoin-git> [bitcoin] thonkle opened pull request #24116: Document listening on port 0 assigns a random unused port (master...doc-port-0) https://github.com/bitcoin/bitcoin/pull/24116
13:58 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
13:59 -!- jamesob [~jamesob@pool-108-31-54-223.washdc.fios.verizon.net] has joined #bitcoin-core-dev
14:01 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
14:02 < jeremyrubin> sipa: whichever one crashes i guess...
14:02 < jeremyrubin> but good point
14:03 < sipa> Ah, it only attaches a debugger when a node crashes? That's also useful. And perhaps enough... just add an assert(false) in the codebase where you want to debug.
14:04 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te66oclonkh96li.ipv6.telus.net] has joined #bitcoin-core-dev
14:06 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 268 seconds]
14:08 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te66oclonkh96li.ipv6.telus.net] has quit [Ping timeout: 250 seconds]
14:16 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
14:16 < bitcoin-git> [bitcoin] mzumsande opened pull request #24117: index: make indices robust against init aborts (master...202201_index_startup) https://github.com/bitcoin/bitcoin/pull/24117
14:16 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
14:19 < jeremyrubin> sipa: well you need to attach before it crashes I guess? but i spose it's not too bad to run test once, report which node *did* crash fail, and run again?
14:19 < jeremyrubin> (run again specifying to attach that one
14:21 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
14:21 < bitcoin-git> [bitcoin] Xekyo opened pull request #24118: Add 'sweep' RPC (master...sweep-wallet-rpc) https://github.com/bitcoin/bitcoin/pull/24118
14:21 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
14:22 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te66oclonkh96li.ipv6.telus.net] has joined #bitcoin-core-dev
14:24 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
14:24 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Remote host closed the connection]
14:27 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te66oclonkh96li.ipv6.telus.net] has quit [Ping timeout: 250 seconds]
14:40 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
14:40 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te66oclonkh96li.ipv6.telus.net] has joined #bitcoin-core-dev
14:44 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 250 seconds]
15:05 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
15:10 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
15:10 < bitcoin-git> [gui] jonatack opened pull request #526: Add address relay/processed/rate-limited fields to peer details (master...add-addr-fields-to-peer-details) https://github.com/bitcoin-core/gui/pull/526
15:10 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
15:10 < sugarpuff_> hi guys, I realize this question might not be considered "development" per se, but it is development related: right now the developers (y'all) are under legal attack by Craig Wright. Afaict, Wright is being used a new means of attack against Bitcoin. The last time I witnessed such a serious attack was BitcoinXT, except this time I think the threat is even greater.
15:11 < sugarpuff_> My question is: what are the bitcoin developers doing (other than trying to switch to pseudonymous development) to defend against this? I have seen gmaxwell repeatedly call Wright a fraud. If Maxwell actually believes this, then why is he avoiding the legal challenge? I think Bitcoin could lose if this sort of approach (of running away from Wright) continues.
15:12 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
15:17 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 268 seconds]
15:21 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has quit [Quit: ZzzZ]
15:21 -!- tla2k21 [~tla2k21@gateway/tor-sasl/tla2k21] has quit [Remote host closed the connection]
15:26 -!- jonatack [jonatack@user/jonatack] has quit [Ping timeout: 250 seconds]
15:35 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has joined #bitcoin-core-dev
15:36 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has quit [Client Quit]
15:37 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has joined #bitcoin-core-dev
15:45 -!- prayank [~andr0irc@103.211.191.71] has joined #bitcoin-core-dev
15:48 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
15:51 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 268 seconds]
15:51 -!- mekster669 [~mekster@user/mekster] has quit [Quit: mekster669]
15:51 < prayank> sugarpuff_: 1. Legal issues are handled by people involved in different ways. Recently few organizations and individuals have tried to support the devs. 2.  Greg Maxwell does not directly contribute to Bitcoin anymore as shared by him multiple times. He can respond to your questions on reddit as they are not related to Bitcoin Core. 3. Bitcoin is fine and CSW or any such scammers will not be able to do much. There was a tweet thread which clearl
15:52 -!- prayank [~andr0irc@103.211.191.71] has quit [Quit: irc thread exit]
15:52 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 268 seconds]
15:54 -!- mekster6694 [~mekster@user/mekster] has joined #bitcoin-core-dev
15:56 < michaelfolkson> sugarpuff_: For more details on a Bitcoin Legal Defense fund feel free to email the address contained in this https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019741.html
15:56 < michaelfolkson> "If you have questions or concerns, you can email info at bitcoindefensefund.org. Will share more information in the near future."
15:56 < michaelfolkson> Other than that don't think there's anything to discuss here
15:59 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Remote host closed the connection]
15:59 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
16:00 < sugarpuff_> Thanks michaelfolkson, I don't think anyone will answer that email, and my questions aren't directed to Jack Dorsey :P.
16:00 < sugarpuff_> prayank nipped out before finishing what he wrote... Greg Maxwell no longer contributes to bitcoin - isn't that because of the lawsuit? If so, then Craig can continue to sue the remaining developers and kick everyone out if nobody goes to court against him. I don't think anyone here can really give me an answer, since this is a decision they have to make on their own (or together), but I just wanted to share my 
16:00 < sugarpuff_> thoughts, etc.
16:02 < sipa> This is off-topic
16:16 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
16:26 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
16:38 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
16:43 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Ping timeout: 256 seconds]
16:45 -!- Aaronvan_ [~AaronvanW@user/AaronvanW] has quit [Quit: Leaving...]
16:48 -!- bomb-on [~bomb-on@194.144.47.113] has quit [Quit: aллилѹіа!]
16:53 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 268 seconds]
16:54 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
16:55 -!- jonatack [jonatack@user/jonatack] has joined #bitcoin-core-dev
17:05 -!- BUSY [~BUSY@user/busy] has quit [Read error: Connection reset by peer]
17:06 -!- BUSY [~BUSY@user/busy] has joined #bitcoin-core-dev
17:07 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
17:08 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 240 seconds]
17:08 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
17:11 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
17:16 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 268 seconds]
17:22 -!- belcher [~belcher@user/belcher] has joined #bitcoin-core-dev
17:30 -!- vysn [~vysn@user/vysn] has joined #bitcoin-core-dev
17:43 -!- arowser [~quassel@111.192.100.78] has joined #bitcoin-core-dev
17:48 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has quit [Quit: ZzzZ]
18:05 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has joined #bitcoin-core-dev
18:09 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:b8cd:7a20:7963:7278] has quit [Ping timeout: 250 seconds]
18:22 -!- jarthur_ [~jarthur@2603-8080-1540-002d-8485-0ba6-5ca5-89ec.res6.spectrum.com] has joined #bitcoin-core-dev
18:24 -!- jarthur [~jarthur@2603-8080-1540-002d-dc67-681f-ccd6-3dd0.res6.spectrum.com] has quit [Ping timeout: 240 seconds]
18:27 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:355d:db20:bc40:ab7e] has joined #bitcoin-core-dev
18:31 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:355d:db20:bc40:ab7e] has quit [Ping timeout: 250 seconds]
18:34 -!- outfox [~outfox@user/outfox] has quit [Ping timeout: 256 seconds]
18:36 -!- outfox [~outfox@213.144.147.16] has joined #bitcoin-core-dev
18:36 -!- outfox [~outfox@213.144.147.16] has quit [Changing host]
18:36 -!- outfox [~outfox@user/outfox] has joined #bitcoin-core-dev
18:37 -!- Earnestly [~earnest@user/earnestly] has quit [Ping timeout: 240 seconds]
19:01 < fanquake> Blocked shahinfe from the /bitcoin org. Also for spamming the /bips wiki
19:02 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:355d:db20:bc40:ab7e] has joined #bitcoin-core-dev
19:06 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:355d:db20:bc40:ab7e] has quit [Ping timeout: 268 seconds]
19:19 -!- arowser [~quassel@111.192.100.78] has quit [Remote host closed the connection]
19:34 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
19:39 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Ping timeout: 250 seconds]
19:43 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
20:07 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
20:10 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:355d:db20:bc40:ab7e] has joined #bitcoin-core-dev
20:15 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:355d:db20:bc40:ab7e] has quit [Ping timeout: 240 seconds]
20:35 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has joined #bitcoin-core-dev
20:45 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:355d:db20:bc40:ab7e] has joined #bitcoin-core-dev
20:49 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:355d:db20:bc40:ab7e] has quit [Ping timeout: 268 seconds]
21:01 -!- cmirror [~cmirror@4.53.92.114] has quit [Remote host closed the connection]
21:01 -!- cmirror [~cmirror@4.53.92.114] has joined #bitcoin-core-dev
21:12 -!- jarthur_ [~jarthur@2603-8080-1540-002d-8485-0ba6-5ca5-89ec.res6.spectrum.com] has quit [Quit: jarthur_]
21:14 -!- NorrinRadd [~username@154.6.21.250] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
21:23 -!- morcos [~morcos@gateway/tor-sasl/morcos] has quit [Ping timeout: 276 seconds]
21:24 -!- morcos [~morcos@gateway/tor-sasl/morcos] has joined #bitcoin-core-dev
21:29 -!- dviola [~diego@user/dviola] has joined #bitcoin-core-dev
21:29 -!- jarthur [~jarthur@2603-8080-1540-002d-8485-0ba6-5ca5-89ec.res6.spectrum.com] has joined #bitcoin-core-dev
21:32 -!- gleb74543 [~gleb@178.150.137.228] has quit [Ping timeout: 240 seconds]
21:36 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
21:38 -!- ryanofsky [~russ@jumpy.yanofsky.org] has quit [Ping timeout: 250 seconds]
21:38 -!- ryanofsky [~russ@jumpy.yanofsky.org] has joined #bitcoin-core-dev
21:40 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Ping timeout: 256 seconds]
21:47 -!- johnzwen- [~johnzweng@zweng.at] has quit [Quit: Leaving...]
21:48 -!- johnzweng [~johnzweng@zweng.at] has joined #bitcoin-core-dev
21:49 -!- grettke [~grettke@cpe-65-29-228-30.wi.res.rr.com] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
21:50 -!- johnzweng [~johnzweng@zweng.at] has quit [Client Quit]
21:53 -!- johnzweng [~johnzweng@zweng.at] has joined #bitcoin-core-dev
21:55 -!- gleb74543 [~gleb@178.150.137.228] has joined #bitcoin-core-dev
21:57 -!- johnzweng [~johnzweng@zweng.at] has quit [Client Quit]
21:58 -!- johnzweng [~johnzweng@zweng.at] has joined #bitcoin-core-dev
22:04 -!- sudoforge [~sudoforge@wireguard/tunneler/sudoforge] has quit [Quit: 404]
22:08 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has quit [Quit: ZzzZ]
22:11 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:355d:db20:bc40:ab7e] has joined #bitcoin-core-dev
22:13 -!- knorrium[m] [~knorriumb@2001:470:69fc:105::1:56b8] has quit [Quit: Client limit exceeded: 20000]
22:15 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:355d:db20:bc40:ab7e] has quit [Ping timeout: 240 seconds]
22:22 -!- jarthur [~jarthur@2603-8080-1540-002d-8485-0ba6-5ca5-89ec.res6.spectrum.com] has quit [Ping timeout: 240 seconds]
22:29 -!- jarthur [~jarthur@2603-8080-1540-002d-d873-1113-a348-98f0.res6.spectrum.com] has joined #bitcoin-core-dev
22:46 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:355d:db20:bc40:ab7e] has joined #bitcoin-core-dev
22:51 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:355d:db20:bc40:ab7e] has quit [Ping timeout: 250 seconds]
23:00 -!- salvatoshi [~salvatosh@lfbn-idf3-1-717-248.w86-252.abo.wanadoo.fr] has joined #bitcoin-core-dev
23:06 -!- vasild [~vd@user/vasild] has quit [Remote host closed the connection]
23:06 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-dev
23:07 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
23:07 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
23:20 -!- ryanofsky [~russ@jumpy.yanofsky.org] has quit [Ping timeout: 256 seconds]
23:20 -!- ryanofsky [russ@jumpy.yanofsky.org] has joined #bitcoin-core-dev
23:22 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
23:26 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Ping timeout: 250 seconds]
23:30 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
23:43 -!- salvatoshi [~salvatosh@lfbn-idf3-1-717-248.w86-252.abo.wanadoo.fr] has quit [Ping timeout: 240 seconds]
23:45 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 268 seconds]
23:46 -!- sipsorcery [~sipsorcer@37.228.225.67] has joined #bitcoin-core-dev
23:56 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:355d:db20:bc40:ab7e] has joined #bitcoin-core-dev
--- Log closed Fri Jan 21 00:00:36 2022