12023-05-04T00:03:04 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
22023-05-04T00:09:48 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 240 seconds)
32023-05-04T00:14:33 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
42023-05-04T00:26:47 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
52023-05-04T00:31:28 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 248 seconds)
62023-05-04T00:44:23 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Ping timeout: 268 seconds)
72023-05-04T01:01:44 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Ping timeout: 240 seconds)
82023-05-04T01:03:49 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
92023-05-04T01:04:07 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
102023-05-04T01:08:08 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 240 seconds)
112023-05-04T01:43:35 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 246 seconds)
122023-05-04T01:49:37 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
132023-05-04T01:53:48 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 240 seconds)
142023-05-04T02:11:52 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
152023-05-04T02:16:08 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 240 seconds)
162023-05-04T02:26:49 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
172023-05-04T02:28:15 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
182023-05-04T02:32:28 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 240 seconds)
192023-05-04T02:34:24 *** montxero <montxero!~user@2402:6940:306:c00:9ee0:6279:bee8:d743> has joined #bitcoin-core-dev
202023-05-04T02:35:44 *** montxero <montxero!~user@2402:6940:306:c00:9ee0:6279:bee8:d743> has quit IRC (Remote host closed the connection)
212023-05-04T02:42:04 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
222023-05-04T02:45:34 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
232023-05-04T02:50:11 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 268 seconds)
242023-05-04T03:14:51 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Ping timeout: 268 seconds)
252023-05-04T03:21:07 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
262023-05-04T03:26:36 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 250 seconds)
272023-05-04T03:49:52 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
282023-05-04T03:54:20 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 260 seconds)
292023-05-04T04:01:01 *** cmirror <cmirror!~cmirror@4.53.92.114> has quit IRC (Remote host closed the connection)
302023-05-04T04:01:34 *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
312023-05-04T04:06:05 *** b_101 <b_101!~robert@189.236.59.209> has quit IRC (Ping timeout: 240 seconds)
322023-05-04T04:11:48 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
332023-05-04T04:16:31 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 268 seconds)
342023-05-04T04:25:07 *** cold <cold!~cold@user/cold> has quit IRC (Ping timeout: 276 seconds)
352023-05-04T04:27:02 *** cold <cold!~cold@user/cold> has joined #bitcoin-core-dev
362023-05-04T04:30:05 *** flooded <flooded!flooded@gateway/vpn/protonvpn/flood/x-43489060> has quit IRC (Ping timeout: 268 seconds)
372023-05-04T04:30:33 *** b_101 <b_101!~robert@189.236.59.209> has joined #bitcoin-core-dev
382023-05-04T04:30:47 *** flooded <flooded!~flooded@146.70.174.163> has joined #bitcoin-core-dev
392023-05-04T04:35:38 *** b_101 <b_101!~robert@189.236.59.209> has quit IRC (Ping timeout: 268 seconds)
402023-05-04T05:01:53 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
412023-05-04T05:06:08 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 240 seconds)
422023-05-04T05:13:29 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
432023-05-04T05:13:45 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
442023-05-04T05:17:44 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 246 seconds)
452023-05-04T05:24:15 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
462023-05-04T05:28:28 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 240 seconds)
472023-05-04T05:44:42 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Ping timeout: 268 seconds)
482023-05-04T05:47:00 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
492023-05-04T05:51:20 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 250 seconds)
502023-05-04T05:57:45 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
512023-05-04T06:02:08 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 240 seconds)
522023-05-04T06:20:08 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
532023-05-04T06:21:10 *** test_ <test_!~flooded@149.102.226.226> has joined #bitcoin-core-dev
542023-05-04T06:22:56 *** flooded <flooded!~flooded@146.70.174.163> has quit IRC (Ping timeout: 268 seconds)
552023-05-04T06:24:28 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 240 seconds)
562023-05-04T06:54:19 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
572023-05-04T07:04:24 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
582023-05-04T07:04:58 *** salvatoshi <salvatoshi!~salvatosh@genymobile-2-6-86.fib.nerim.net> has joined #bitcoin-core-dev
592023-05-04T07:09:10 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 260 seconds)
602023-05-04T07:10:34 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
612023-05-04T07:13:15 *** aielima <aielima!~aielima@user/aielima> has joined #bitcoin-core-dev
622023-05-04T07:15:00 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 252 seconds)
632023-05-04T07:16:37 *** b_101 <b_101!~robert@189.236.59.209> has joined #bitcoin-core-dev
642023-05-04T07:16:43 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
652023-05-04T07:21:14 *** b_101 <b_101!~robert@189.236.59.209> has quit IRC (Ping timeout: 252 seconds)
662023-05-04T07:45:45 *** b_101 <b_101!~robert@189.236.59.209> has joined #bitcoin-core-dev
672023-05-04T07:49:26 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
682023-05-04T07:51:05 *** aielima <aielima!~aielima@user/aielima> has quit IRC (*.net *.split)
692023-05-04T07:51:05 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (*.net *.split)
702023-05-04T07:51:05 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (*.net *.split)
712023-05-04T07:51:05 *** qxs <qxs!~qxs@gateway/tor-sasl/qxs> has quit IRC (*.net *.split)
722023-05-04T07:51:05 *** pharonix71 <pharonix71!~pharonix7@user/pharonix71> has quit IRC (*.net *.split)
732023-05-04T07:51:05 *** SpellChecker_ <SpellChecker_!~SpellChec@user/SpellChecker> has quit IRC (*.net *.split)
742023-05-04T07:51:05 *** yanmaani1 <yanmaani1!~yanmaani@gateway/tor-sasl/yanmaani> has quit IRC (*.net *.split)
752023-05-04T07:51:07 *** b_101 <b_101!~robert@189.236.59.209> has quit IRC (Ping timeout: 268 seconds)
762023-05-04T07:52:07 *** aielima <aielima!~aielima@user/aielima> has joined #bitcoin-core-dev
772023-05-04T07:52:07 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
782023-05-04T07:52:07 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
792023-05-04T07:52:07 *** qxs <qxs!~qxs@gateway/tor-sasl/qxs> has joined #bitcoin-core-dev
802023-05-04T07:52:07 *** pharonix71 <pharonix71!~pharonix7@user/pharonix71> has joined #bitcoin-core-dev
812023-05-04T07:52:07 *** SpellChecker_ <SpellChecker_!~SpellChec@user/SpellChecker> has joined #bitcoin-core-dev
822023-05-04T07:52:07 *** yanmaani1 <yanmaani1!~yanmaani@gateway/tor-sasl/yanmaani> has joined #bitcoin-core-dev
832023-05-04T07:54:05 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 260 seconds)
842023-05-04T08:01:05 *** puchka <puchka!~puchka@185.203.122.101> has quit IRC (Ping timeout: 240 seconds)
852023-05-04T08:06:14 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
862023-05-04T08:10:40 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 248 seconds)
872023-05-04T08:12:17 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
882023-05-04T08:16:50 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 260 seconds)
892023-05-04T08:20:27 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has quit IRC (Quit: Going offline, see ya! (www.adiirc.com))
902023-05-04T08:28:40 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
912023-05-04T08:33:02 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 246 seconds)
922023-05-04T08:40:41 *** puchka <puchka!~puchka@185.203.122.12> has joined #bitcoin-core-dev
932023-05-04T08:51:06 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
942023-05-04T08:55:28 *** puchka <puchka!~puchka@185.203.122.12> has quit IRC (Ping timeout: 240 seconds)
952023-05-04T08:57:40 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 260 seconds)
962023-05-04T08:59:08 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
972023-05-04T09:02:43 *** puchka <puchka!~puchka@102.161.66.205> has joined #bitcoin-core-dev
982023-05-04T09:04:32 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 248 seconds)
992023-05-04T09:09:26 *** puchka <puchka!~puchka@102.161.66.205> has quit IRC (Ping timeout: 268 seconds)
1002023-05-04T09:11:03 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
1012023-05-04T09:11:13 *** puchka <puchka!~puchka@185.203.122.59> has joined #bitcoin-core-dev
1022023-05-04T09:15:23 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 246 seconds)
1032023-05-04T09:38:50 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
1042023-05-04T09:43:28 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 248 seconds)
1052023-05-04T09:50:33 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
1062023-05-04T09:54:56 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 246 seconds)
1072023-05-04T09:56:47 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
1082023-05-04T10:01:22 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 250 seconds)
1092023-05-04T10:24:22 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
1102023-05-04T10:28:48 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 240 seconds)
1112023-05-04T10:42:13 <bitcoin-git> [bitcoin] MarcoFalke opened pull request #27570: refactor: Remove need to pass chainparams from BlockManager methods (master...2305-blockman-chain-params-) https://github.com/bitcoin/bitcoin/pull/27570
1122023-05-04T10:42:36 *** b_101 <b_101!~robert@189.236.59.209> has joined #bitcoin-core-dev
1132023-05-04T10:46:33 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
1142023-05-04T10:47:58 *** b_101 <b_101!~robert@189.236.59.209> has quit IRC (Ping timeout: 276 seconds)
1152023-05-04T10:49:50 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Quit: Leaving...)
1162023-05-04T10:51:12 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 248 seconds)
1172023-05-04T10:52:39 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
1182023-05-04T10:53:43 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
1192023-05-04T10:56:24 *** abubakarsadiq <abubakarsadiq!~abubakars@197.210.76.209> has joined #bitcoin-core-dev
1202023-05-04T10:56:48 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 240 seconds)
1212023-05-04T10:57:33 <bitcoin-git> [bitcoin] MarcoFalke opened pull request #27571: ci: Run iwyu on all src files (master...2305-ci-iwyu-) https://github.com/bitcoin/bitcoin/pull/27571
1222023-05-04T10:57:50 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
1232023-05-04T11:02:18 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
1242023-05-04T11:02:30 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 260 seconds)
1252023-05-04T11:11:43 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
1262023-05-04T11:16:16 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 248 seconds)
1272023-05-04T11:17:48 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
1282023-05-04T11:22:08 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 240 seconds)
1292023-05-04T11:28:41 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
1302023-05-04T11:33:14 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 250 seconds)
1312023-05-04T11:36:51 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has left #bitcoin-core-dev (Closing Window)
1322023-05-04T11:45:25 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
1332023-05-04T11:49:48 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 240 seconds)
1342023-05-04T12:02:28 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
1352023-05-04T12:11:25 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 240 seconds)
1362023-05-04T12:11:59 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
1372023-05-04T12:21:30 *** Guest46 <Guest46!~Guest46@bba-2-50-39-43.alshamil.net.ae> has joined #bitcoin-core-dev
1382023-05-04T12:22:41 <bitcoin-git> [bitcoin] theStack opened pull request #27572: test: dedup file hashing using `sha256sum_file` helper (master...test-refactor-use_sha256sum_file_helper) https://github.com/bitcoin/bitcoin/pull/27572
1392023-05-04T12:27:20 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Ping timeout: 240 seconds)
1402023-05-04T12:27:20 *** abubakarsadiq <abubakarsadiq!~abubakars@197.210.76.209> has quit IRC (Read error: Connection reset by peer)
1412023-05-04T12:30:02 *** Guest46 <Guest46!~Guest46@bba-2-50-39-43.alshamil.net.ae> has quit IRC (Quit: Client closed)
1422023-05-04T12:30:21 *** aielima <aielima!~aielima@user/aielima> has quit IRC (Quit: Ciao)
1432023-05-04T12:30:35 *** b_101 <b_101!~robert@189.236.59.209> has joined #bitcoin-core-dev
1442023-05-04T12:35:25 *** b_101 <b_101!~robert@189.236.59.209> has quit IRC (Ping timeout: 240 seconds)
1452023-05-04T12:39:37 *** test_ is now known as _flood
1462023-05-04T12:56:07 *** abubakarsadiq <abubakarsadiq!~abubakars@197.210.53.16> has joined #bitcoin-core-dev
1472023-05-04T12:57:41 <bitcoin-git> [bitcoin] fanquake closed pull request #27364: ci: set docker run --ulimit to workaround Valgrind assertion (master...native_fuzz_valgrind_docker_ulimit) https://github.com/bitcoin/bitcoin/pull/27364
1482023-05-04T12:57:43 *** MrFrancis <MrFrancis!~MrFrancis@2001:8a0:fa4c:901:bc04:5de1:60b6:807b> has joined #bitcoin-core-dev
1492023-05-04T12:58:13 *** MrFrancis <MrFrancis!~MrFrancis@2001:8a0:fa4c:901:bc04:5de1:60b6:807b> has quit IRC (Client Quit)
1502023-05-04T13:02:20 <jamesob> MacroFake: thanks. Eventually was able to repro locally by copying the conf flags exactly from the native_tsan ci/ shell script. Apparently just passing "--with-sanitizers=thread" wasn't sufficient to repro
1512023-05-04T13:21:02 *** abubakarsadiq <abubakarsadiq!~abubakars@197.210.53.16> has quit IRC (Ping timeout: 268 seconds)
1522023-05-04T13:22:43 *** abubakarsadiq <abubakarsadiq!~abubakars@197.210.77.50> has joined #bitcoin-core-dev
1532023-05-04T13:32:36 *** Murch <Murch!~murch@user/murch> has quit IRC (Quit: Bridge terminating on SIGTERM)
1542023-05-04T13:32:36 *** willcl_ark <willcl_ark!~willcl-ar@user/willcl-ark/x-8282106> has quit IRC (Quit: Bridge terminating on SIGTERM)
1552023-05-04T13:32:36 *** dunxen <dunxen!~dunxen@2001:470:69fc:105::1:fec1> has quit IRC (Quit: Bridge terminating on SIGTERM)
1562023-05-04T13:32:36 *** kayabanerve[m] <kayabanerve[m]!~kayabaner@2001:470:69fc:105::1:278> has quit IRC (Quit: Bridge terminating on SIGTERM)
1572023-05-04T13:32:36 *** sequences[m] <sequences[m]!~sequences@2001:470:69fc:105::2:ffee> has quit IRC (Quit: Bridge terminating on SIGTERM)
1582023-05-04T13:32:36 *** BlueMatt[m] <BlueMatt[m]!~bluemattm@2001:470:69fc:105::1:5092> has quit IRC (Quit: Bridge terminating on SIGTERM)
1592023-05-04T13:32:37 *** euclid[m] <euclid[m]!~euclidhni@2001:470:69fc:105::2b6f> has quit IRC (Quit: Bridge terminating on SIGTERM)
1602023-05-04T13:32:37 *** Fractal[m]1 <Fractal[m]1!~fractalma@2001:470:69fc:105::3:2fe2> has quit IRC (Quit: Bridge terminating on SIGTERM)
1612023-05-04T13:32:37 *** bohruz[m] <bohruz[m]!~bohruzmat@2001:470:69fc:105::1:59a4> has quit IRC (Quit: Bridge terminating on SIGTERM)
1622023-05-04T13:32:37 *** provoostenator <provoostenator!~provooste@user/provoostenator> has quit IRC (Quit: Bridge terminating on SIGTERM)
1632023-05-04T13:32:37 *** stratospher[m] <stratospher[m]!~stratosph@2001:470:69fc:105::2:728e> has quit IRC (Quit: Bridge terminating on SIGTERM)
1642023-05-04T13:32:37 *** sipa <sipa!~sipa@user/sipa> has quit IRC (Quit: Bridge terminating on SIGTERM)
1652023-05-04T13:32:37 *** denise[m] <denise[m]!~denisewui@2001:470:69fc:105::1:4ab8> has quit IRC (Quit: Bridge terminating on SIGTERM)
1662023-05-04T13:32:37 *** kakolainen[m] <kakolainen[m]!~kakolaine@2001:470:69fc:105::34f9> has quit IRC (Quit: Bridge terminating on SIGTERM)
1672023-05-04T13:32:39 *** wpaulino <wpaulino!~wpaulino@user/wpaulino> has quit IRC (Quit: Bridge terminating on SIGTERM)
1682023-05-04T13:32:40 *** bitcoin-git <bitcoin-git!~bitcoin-g@2001:470:69fc:105::2:690> has quit IRC (Quit: Bridge terminating on SIGTERM)
1692023-05-04T13:35:32 *** Murch <Murch!~murch@user/murch> has joined #bitcoin-core-dev
1702023-05-04T13:39:15 *** bitcoin-git <bitcoin-git!~bitcoin-g@2001:470:69fc:105::2:690> has joined #bitcoin-core-dev
1712023-05-04T13:39:15 *** willcl_ark <willcl_ark!~willcl-ar@user/willcl-ark/x-8282106> has joined #bitcoin-core-dev
1722023-05-04T13:39:15 *** kakolainen[m] <kakolainen[m]!~kakolaine@2001:470:69fc:105::34f9> has joined #bitcoin-core-dev
1732023-05-04T13:39:15 *** denise[m] <denise[m]!~denisewui@2001:470:69fc:105::1:4ab8> has joined #bitcoin-core-dev
1742023-05-04T13:39:15 *** sipa <sipa!~sipa@user/sipa> has joined #bitcoin-core-dev
1752023-05-04T13:39:15 *** stratospher[m] <stratospher[m]!~stratosph@2001:470:69fc:105::2:728e> has joined #bitcoin-core-dev
1762023-05-04T13:39:15 *** sequences[m] <sequences[m]!~sequences@2001:470:69fc:105::2:ffee> has joined #bitcoin-core-dev
1772023-05-04T13:39:15 *** kayabanerve[m] <kayabanerve[m]!~kayabaner@2001:470:69fc:105::1:278> has joined #bitcoin-core-dev
1782023-05-04T13:39:15 *** dunxen <dunxen!~dunxen@2001:470:69fc:105::1:fec1> has joined #bitcoin-core-dev
1792023-05-04T13:39:15 *** BlueMatt[m] <BlueMatt[m]!~bluemattm@2001:470:69fc:105::1:5092> has joined #bitcoin-core-dev
1802023-05-04T13:39:29 *** Fractal[m] <Fractal[m]!~fractalma@2001:470:69fc:105::3:2fe2> has joined #bitcoin-core-dev
1812023-05-04T13:39:30 *** euclid[m] <euclid[m]!~euclidhni@2001:470:69fc:105::2b6f> has joined #bitcoin-core-dev
1822023-05-04T13:39:30 *** provoostenator <provoostenator!~provooste@user/provoostenator> has joined #bitcoin-core-dev
1832023-05-04T13:39:31 *** wpaulino <wpaulino!~wpaulino@user/wpaulino> has joined #bitcoin-core-dev
1842023-05-04T13:45:43 *** b_101 <b_101!~robert@189.236.59.209> has joined #bitcoin-core-dev
1852023-05-04T13:50:43 *** b_101 <b_101!~robert@189.236.59.209> has quit IRC (Ping timeout: 260 seconds)
1862023-05-04T13:55:05 *** Guest16 <Guest16!~Guest16@46.166.179.211> has joined #bitcoin-core-dev
1872023-05-04T13:56:12 *** Guest16 <Guest16!~Guest16@46.166.179.211> has quit IRC (Client Quit)
1882023-05-04T14:10:44 *** abubakar1adiq <abubakar1adiq!~abubakars@197.210.77.96> has joined #bitcoin-core-dev
1892023-05-04T14:10:45 *** abubakarsadiq <abubakarsadiq!~abubakars@197.210.77.50> has quit IRC (Read error: Connection reset by peer)
1902023-05-04T14:15:19 *** b_101 <b_101!~robert@189.236.59.209> has joined #bitcoin-core-dev
1912023-05-04T14:15:22 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has joined #bitcoin-core-dev
1922023-05-04T14:20:35 *** b_101 <b_101!~robert@189.236.59.209> has quit IRC (Ping timeout: 264 seconds)
1932023-05-04T14:27:08 *** abubakar1adiq <abubakar1adiq!~abubakars@197.210.77.96> has quit IRC (Read error: Connection reset by peer)
1942023-05-04T14:44:10 *** jarthur <jarthur!~jarthur@user/jarthur> has joined #bitcoin-core-dev
1952023-05-04T15:09:04 <bitcoin-git> [bitcoin] achow101 pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/aebcd18c654a...30bf70c8b60f
1962023-05-04T15:09:05 <bitcoin-git> bitcoin/master afc2dd5 Sebastian Falbesoner: test: various `converttopsbt` check cleanups in rpc_psbt.py
1972023-05-04T15:09:05 <bitcoin-git> bitcoin/master 30bf70c Andrew Chow: Merge bitcoin/bitcoin#27325: test: various `converttopsbt` check cleanups ...
1982023-05-04T15:09:09 <bitcoin-git> [bitcoin] achow101 merged pull request #27325: test: various `converttopsbt` check cleanups in rpc_psbt.py (master...test_psbt_cleanups) https://github.com/bitcoin/bitcoin/pull/27325
1992023-05-04T15:11:40 *** preimage <preimage!~halosghos@user/halosghost> has joined #bitcoin-core-dev
2002023-05-04T15:17:20 *** b_101 <b_101!~robert@189.236.59.209> has joined #bitcoin-core-dev
2012023-05-04T15:38:34 *** aielima <aielima!~aielima@user/aielima> has joined #bitcoin-core-dev
2022023-05-04T15:46:33 *** flooded <flooded!~flooded@146.70.127.243> has joined #bitcoin-core-dev
2032023-05-04T15:46:45 *** salvatoshi <salvatoshi!~salvatosh@genymobile-2-6-86.fib.nerim.net> has quit IRC (Ping timeout: 240 seconds)
2042023-05-04T15:46:59 *** kevkevin_ <kevkevin_!~kevkevin@2601:241:8703:7b30:fdf9:a35f:16d7:9b75> has joined #bitcoin-core-dev
2052023-05-04T15:49:48 *** _flood <_flood!~flooded@149.102.226.226> has quit IRC (Ping timeout: 240 seconds)
2062023-05-04T16:05:44 *** nintendo1889 <nintendo1889!uid23646@id-23646.tinside.irccloud.com> has joined #bitcoin-core-dev
2072023-05-04T16:07:52 *** brunoerg_ <brunoerg_!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
2082023-05-04T16:07:59 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Read error: Connection reset by peer)
2092023-05-04T16:11:56 <instagibbs> fyi, github having a sads right now, pushes aren't seemingly working https://www.githubstatus.com/
2102023-05-04T16:12:08 *** bohruz[m] <bohruz[m]!~bohruzmat@2001:470:69fc:105::1:59a4> has joined #bitcoin-core-dev
2112023-05-04T16:12:23 <fanquake> must be time to knock off
2122023-05-04T16:12:37 <instagibbs> ð»
2132023-05-04T16:18:18 <preimage> I still don't understand why githubstatus has an indicator for githubstatus⦠is that just so they always get to have one green checkmark showing (or the page doesn't load at all)?
2142023-05-04T16:19:39 <bitcoin-git> [bitcoin] MarcoFalke opened pull request #27573: ci: Remove CI_EXEC bloat in test/06_script_b.sh (master...2305-ci-exec-no-) https://github.com/bitcoin/bitcoin/pull/27573
2152023-05-04T16:19:44 <bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/30bf70c8b60f...6c7ebcc14b79
2162023-05-04T16:19:44 <bitcoin-git> bitcoin/master 7e3d4f8 ismaelsadeeq: test: add coverage to ensure the first arg of scantxoutset is needed
2172023-05-04T16:19:44 <bitcoin-git> bitcoin/master 6c7ebcc fanquake: Merge bitcoin/bitcoin#27422: test: add coverage to rpc_scantxoutset.py
2182023-05-04T16:19:51 <bitcoin-git> [bitcoin] fanquake merged pull request #27422: test: add coverage to rpc_scantxoutset.py (master...2023-04-test-coverage-rpc_scantxoutset) https://github.com/bitcoin/bitcoin/pull/27422
2192023-05-04T16:29:23 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 260 seconds)
2202023-05-04T16:29:41 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2212023-05-04T16:34:21 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2222023-05-04T16:36:26 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 265 seconds)
2232023-05-04T16:44:30 <achow101> michaelfolkson: we (the maintainers) feel that we need a maintainer that understands our interfaces. We felt that ryanofsky was the obvious choice for this role as he has a lot of experience in that area and is a respected reviewer. This is a different situation from last year as we did not feel the need for another maintainer at that time.
2242023-05-04T16:45:45 *** Talkless <Talkless!~Talkless@mail.dargis.net> has joined #bitcoin-core-dev
2252023-05-04T16:56:04 <jamesob> incidentally, I'm really happy about ryanofsky being nominated for maintainer. I think he is one of the most experienced, kind devs on the project, and frequently provides detailed review and good feedback for a wide variety of changes. He's one of the only qualified reviewers for coins and other "validation" code.
2262023-05-04T16:57:17 *** Guest0 <Guest0!~Guest0@2804:7f1:e786:9838:6b47:74ae:9bcb:7b7a> has joined #bitcoin-core-dev
2272023-05-04T16:57:56 *** Guest0 <Guest0!~Guest0@2804:7f1:e786:9838:6b47:74ae:9bcb:7b7a> has quit IRC (Client Quit)
2282023-05-04T16:58:18 *** Guest0 <Guest0!~Guest0@2804:7f1:e786:9838:6b47:74ae:9bcb:7b7a> has joined #bitcoin-core-dev
2292023-05-04T17:08:52 *** puchka <puchka!~puchka@185.203.122.59> has quit IRC (Ping timeout: 276 seconds)
2302023-05-04T17:10:35 *** puchka <puchka!~puchka@185.203.122.61> has joined #bitcoin-core-dev
2312023-05-04T17:10:40 *** sr_gi[m] <sr_gi[m]!~srgimatri@2001:470:69fc:105::1:c14c> has joined #bitcoin-core-dev
2322023-05-04T17:12:21 *** sanket1729_ <sanket1729_!~sanket172@ec2-100-24-255-95.compute-1.amazonaws.com> has left #bitcoin-core-dev (Leaving)
2332023-05-04T17:13:11 *** ishaanam[m] <ishaanam[m]!~ishaanamm@2001:470:69fc:105::2:4078> has joined #bitcoin-core-dev
2342023-05-04T17:13:13 *** sanket1729_ <sanket1729_!~sanket172@ec2-100-24-255-95.compute-1.amazonaws.com> has joined #bitcoin-core-dev
2352023-05-04T17:32:59 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 248 seconds)
2362023-05-04T17:41:11 <bitcoin-git> [bitcoin] dergoegge opened pull request #27574: doc: Add post branch-off note about fuzz input pruning (master...2023-05-release-qa-prune) https://github.com/bitcoin/bitcoin/pull/27574
2372023-05-04T17:45:09 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2382023-05-04T17:49:52 <bitcoin-git> [bitcoin] hebasto opened pull request #27575: Introduce platform-agnostic `ALWAYS_INLINE` macro (master...230504-inline) https://github.com/bitcoin/bitcoin/pull/27575
2392023-05-04T18:12:29 <sdaftuar> jamesob: do you have a good workflow for testing assumeutxo? ie if i ran dumptxoutset on an existing node, what's the easiest way to load that in as a snapshot on a fresh node that i want to test?
2402023-05-04T18:24:34 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Quit: WeeChat 3.8)
2412023-05-04T18:25:32 *** nintendo1889 <nintendo1889!uid23646@id-23646.tinside.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
2422023-05-04T18:37:52 <glozow> Hi y'all, if you haven't already, 30minutes left to fill out the poll for a new irc meeting time https://doodle.com/meeting/participate/id/ax25vR3d
2432023-05-04T18:41:39 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2442023-05-04T18:59:54 *** abubakarsadiq <abubakarsadiq!~abubakars@102.91.53.60> has joined #bitcoin-core-dev
2452023-05-04T19:00:16 <achow101> #startmeeting
2462023-05-04T19:00:16 <core-meetingbot> Meeting started Thu May 4 19:00:16 2023 UTC. The chair is achow101. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings.
2472023-05-04T19:00:17 <core-meetingbot> Available commands: action commands idea info link nick
2482023-05-04T19:00:22 <hebasto> hi
2492023-05-04T19:00:25 <achow101> #bitcoin-core-dev Meeting: achow101 _aj_ amiti ariard aureleoules b10c BlueMatt brunoerg cfields darosior dergoegge dongcarl fanquake fjahr furszy gleb glozow hebasto instagibbs jamesob jarolrod jonatack josibake kallewoof kanzure kouloumos kvaciral laanwj LarryRuane lightlike luke-jr MacroFake Murch phantomcircuit pinheadmz promag provoostenator ryanofsky sdaftuar S3RK stickies-v sipa theStack vasild
2502023-05-04T19:00:31 <josie> hi
2512023-05-04T19:00:32 <dergoegge> hi
2522023-05-04T19:00:32 <theStack> hi
2532023-05-04T19:00:33 <instagibbs> hi
2542023-05-04T19:00:35 <willcl_ark> hi
2552023-05-04T19:00:38 <cfields> hi
2562023-05-04T19:00:39 <achow101> Welcome to the weekly general IRC meeting
2572023-05-04T19:00:39 <pinheadmz_> Hi
2582023-05-04T19:00:48 <b10c> hi
2592023-05-04T19:00:50 <Murch> Hi
2602023-05-04T19:00:51 <lightlike> hi
2612023-05-04T19:00:56 <stickies-v> hi
2622023-05-04T19:00:57 <achow101> we've got several topics today from CoreDev
2632023-05-04T19:01:02 <kanzure> hi
2642023-05-04T19:01:07 <glozow> hi
2652023-05-04T19:01:11 <furszy> hi
2662023-05-04T19:01:27 <achow101> #topic Project priorities
2672023-05-04T19:01:27 <core-meetingbot> topic: Project priorities
2682023-05-04T19:01:48 <achow101> At CoreDev last week, we discussed as a group that we wanted to try something new with having priority projects for the next release cycle.
2692023-05-04T19:01:56 <neha> hi
2702023-05-04T19:01:56 <achow101> Priority meaning that PRs in the priority project will take merging precedence if they are (close to being) ready for merge but conflict with another PR that is not part of a priority project.
2712023-05-04T19:02:09 <achow101> The priority projects will also become permanent topics in the IRC meetings until the next release (or are completed) so that we can get updates on the progress of the topics and figure out what to do next to move them forward.
2722023-05-04T19:02:23 <achow101> The goal of this is to have things that we can make progress on and have a better idea of the kinds of PRs to actually focus on.
2732023-05-04T19:03:12 <achow101> Obviously other PRs can still be worked on, and no one is being forced to work on or look at the priority projects
2742023-05-04T19:03:31 <achow101> and this is just an experiment for the next release, we can change things if it doesn't work out
2752023-05-04T19:03:51 *** Eric3 <Eric3!~exeric3@dbox.skgaming.net> has left #bitcoin-core-dev
2762023-05-04T19:03:59 *** ExEric3 <ExEric3!~exeric3@dbox.skgaming.net> has joined #bitcoin-core-dev
2772023-05-04T19:04:13 <achow101> To determine the projects, we discussed having a vote. Many of us voted in person, but we also want the votes of those who weren't able to make it
2782023-05-04T19:04:27 <achow101> The projects are: Multiprocess, Erlay, BIP 324, Kernel, AssumeUTXO, Legacy Wallet Removal, Package Relay, ASMap, and Silent Payments.
2792023-05-04T19:04:36 <josie> is there a place to track what the priority projects are? or are we reusing the "high priority for review"
2802023-05-04T19:04:43 <achow101> are there any others that we may want to add to that list?
2812023-05-04T19:05:01 <achow101> josie: I think reusing that board is a good idea
2822023-05-04T19:05:03 <glozow> I think we can add a new column to the high priority for review board for "prioritized projects" or something
2832023-05-04T19:05:07 <jonatack> hi
2842023-05-04T19:05:14 <achow101> and also pin the tracking issues/prs for those projects
2852023-05-04T19:05:22 <glozow> And keep the bug fixes etc, as we will obviously want to get those merged as well
2862023-05-04T19:05:26 <instagibbs> Ideally I'd like an issue per project, ala https://github.com/bitcoin/bitcoin/issues/27463
2872023-05-04T19:05:41 <josie> yeah, by tracking im less worried about "what" the projects are and more concerned about tracking the associated PR(s)
2882023-05-04T19:05:56 *** brunoerg_ <brunoerg_!~brunoerg@187.183.43.117> has quit IRC ()
2892023-05-04T19:05:57 <achow101> for the voting, please post your votes for 3 projects that you would like as priorities. we'll count them up and announce before the end of the meeting
2902023-05-04T19:06:06 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
2912023-05-04T19:06:09 <achow101> (obviously don't vote if you voted at coedev, we'll include those counts too)
2922023-05-04T19:06:22 <kanzure> not to nitpick but i'd like to call it a poll more than a vote *shrug*
2932023-05-04T19:06:23 <willcl_ark> We could also use temporary repo labels if that would help, but I think a tracking issue would probably be cleaner...
2942023-05-04T19:06:48 <josie> instagibbs: +1, having an issue to track PRs and discussion is nice. we could add the issues to the high priority for review board
2952023-05-04T19:07:13 <brunoerg> instagibbs: +1
2962023-05-04T19:07:20 <instagibbs> e.g., https://bip324.com/sections/code-review/ is stale, would be better imo to just have a tracking issue like package relay
2972023-05-04T19:07:52 <jonatack> "take merging precedence if they are (close to being) ready for merge but conflict with another PR" -> I thought this was informally the current practice
2982023-05-04T19:08:24 <fjahr> issues can go stale too but I agree it's a good idea
2992023-05-04T19:08:40 <achow101> instagibbs: yeah, we should followup with the project authors to get a tracking issue
3002023-05-04T19:08:54 <instagibbs> fjahr I think the expectation is that is kept fresh on a weekly basis for meetings, if it's a priority project?
3012023-05-04T19:09:14 <achow101> fjahr: we'll followup each week, so hopefully they don't go stale
3022023-05-04T19:09:16 <fanquake> That + it's easy for someone else to update a stale issue if need be
3032023-05-04T19:09:27 <glozow> instagibbs +1, that's how I'm using 27463. I've edited the issue a bunch of times
3042023-05-04T19:10:05 <glozow> jonatack: yes, but the point here is to get a sense of which projects to prioritize
3052023-05-04T19:10:13 <josie> fjahr: perhaps the unspoken assumption is that a priority project has a champion(s). if those individuals are not updating the issues and PRs, I assume it would eventually be removed from the priority list
3062023-05-04T19:10:19 <fanquake> If they do go stale, I'd assume they are no-longer a priotity. None of this works if the person "leading" the project isn't actively involved
3072023-05-04T19:10:36 <fjahr> Ok, that does make sense, if that is being done it's good. I had issue keeping the tracking issue for coinstatsindex up to date but if there are enough eyes on it it solve that problem
3082023-05-04T19:10:50 <glozow> if I'm merging I feel more comfortable prioritizing something that the group has said they want to prioritize
3092023-05-04T19:10:53 <lightlike> i think that in any case it will be more important for the success of this new approach to get a better concentration of review on these projects (rather than merge priority).
3102023-05-04T19:11:13 <josie> lightlike: +1
3112023-05-04T19:11:27 <instagibbs> lightlike it's both pieces
3122023-05-04T19:11:28 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
3132023-05-04T19:11:53 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Read error: Connection reset by peer)
3142023-05-04T19:12:25 <glozow> Hopefully talking about the projects weekly will help keep momentum going!
3152023-05-04T19:14:53 <achow101> if you haven't voted yet and would like to, please do so at some point during the meeting
3162023-05-04T19:15:07 <achow101> #topic add ryanofsky as maintainer
3172023-05-04T19:15:08 <core-meetingbot> topic: add ryanofsky as maintainer
3182023-05-04T19:15:09 <_aj_> it might make sense for each priority project to have a single "priority pr" that's actively being reviewed for merge real soon at any one time; then anything that conflicts with that PR can be considered blocked, but things that conflict with other PRs in the priority project can still go ahead
3192023-05-04T19:15:52 <Murch> I had interpreted the voting at Core Dev to be just exploratory and that the actual poll would be conducted out of band when the entire set of contributors could participate during or after meeting. TBH, it feels a bit unfair to make people that were not able to attend to vote here now in public
3202023-05-04T19:16:07 <fjahr> achow: I guess people can vote with a dm to you if they don't want to vote in public, right?
3212023-05-04T19:16:14 <josie> _aj_: it would be really nice if the issue tracked the current state of the project, i.e which PR is currently needing review
3222023-05-04T19:16:23 <achow101> fjahr: sure, or glozow
3232023-05-04T19:16:41 <Murch> fjahr: good idea
3242023-05-04T19:16:51 <jon_atack> "which projects to prioritize" -> fwiw I just use the high-prio board for this, coupled with a general idea of the larger projects
3252023-05-04T19:17:58 <achow101> We (the maintainers) felt that there was a need for a maintainer who understood our interfaces and modularization efforts well, and we think that ryanofsky is a good fit for that.
3262023-05-04T19:18:46 <fanquake> The high-prio board has clearly been a failure to (really) prioritize anything substantial. The project also needs a bit more direction than "everyone just toss up what they want reviewed at the moment"
3272023-05-04T19:19:53 <fjahr> Murch: +1 on the vote being pretty short notice. Maybe extend the voting period until the next meeting.
3282023-05-04T19:20:25 <glozow> I think the biggest problem with high-prio board is that we as a group don't collectively decide what goes on it. It's not a reflection of what "we" think is high priority.
3292023-05-04T19:20:34 <_aj_> it'd be nice to start prioritising projects and reviewing and merging them, rather than be bogged down in process for it for weeks...
3302023-05-04T19:20:47 <josie> _aj_: +1
3312023-05-04T19:20:52 <achow101> _aj_: agreed
3322023-05-04T19:20:53 <instagibbs> I have a feeling there are already 3/4 clear winners from last week
3332023-05-04T19:21:13 <glozow> Should we move on to the next topic?
3342023-05-04T19:21:17 <achow101> I think we can improve the process for next time, and there actually are some very clear winners
3352023-05-04T19:21:17 <fanquake> aussume utxo, bip324, kernel, package relay
3362023-05-04T19:22:00 <fjahr> yes, but we can not prioritize all of them
3372023-05-04T19:22:10 <Murch> _aj_: +1
3382023-05-04T19:22:20 <ajonas> when prioritizing projects and the champions fade or aren't moving things forward, what happens?
3392023-05-04T19:22:23 <achow101> fjahr: the plan was the pick the top 3
3402023-05-04T19:22:54 <achow101> ajonas: the project stalls until someone else wants to champion it? ideally there are multiple champions per project, but ultimately each pr only has one author
3412023-05-04T19:22:55 <fanquake> in that case, I think drop kernel from the list. As there is a minimal number of substantial PRs left for stage 1
3422023-05-04T19:23:12 <fanquake> I think they will be merged in the next week or two (ideally) regardless
3432023-05-04T19:23:17 <achow101> #topic project priorities (cont'd)
3442023-05-04T19:23:17 <core-meetingbot> topic: project priorities (cont'd)
3452023-05-04T19:23:24 <fanquake> and post that we could focus on the remaining 3
3462023-05-04T19:23:29 <fjahr> I think it would be better if we restrict it to an amount that is realistic to get into a release. So two probably.
3472023-05-04T19:23:40 *** Guest0 <Guest0!~Guest0@2804:7f1:e786:9838:6b47:74ae:9bcb:7b7a> has quit IRC (Quit: Client closed)
3482023-05-04T19:23:41 <fanquake> with kernel stage 2/exploration still happening in the background
3492023-05-04T19:24:02 <cfields> Yeah, it's worth mentioning this was titled "v26 priorities" in-person.
3502023-05-04T19:24:07 <hebasto> agree with fanquake
3512023-05-04T19:24:08 <achow101> fjahr: the point isn't to complete them, it's really just to get forward progress and momentum
3522023-05-04T19:24:14 <instagibbs> fjahr BIP324/package relay aren't going to make it into 26 in entirety... absolutely no way
3532023-05-04T19:24:24 <_aj_> ajonas: i think for apriority PR, we should expect it to make progress in ~3 weeks, then get either merged or removed as a blocker (and reconsidered if updated in another couple of weeks). if a priority project loses momentum, then it just doesn't have a priority PR for a while and no longer manages to block anything else
3542023-05-04T19:24:30 <fanquake> assume utxo is also nearly a point of "completion" (possibly) already
3552023-05-04T19:24:31 <jon_atack> Note that every suggestion to add process over the past years to add process hasn't been terribly successful, i believe...i'm not convinced that adding process is a solution in an ad hoc open source project like this. one that, if anything, ought to become more decentralized. but sure.
3562023-05-04T19:24:35 <Murch> achow101: I thought the idea was to focus on some things that realistically could be shipped with v26
3572023-05-04T19:24:54 <cfields> ^^
3582023-05-04T19:24:55 <instagibbs> fanquake right that one might get close in 26
3592023-05-04T19:24:57 <brunoerg> I had same thought than Murch
3602023-05-04T19:25:24 <fjahr> then maybe we should just focus on one, I have seen too many projects fail due to a lack of focus and prioritizing 3 huge things equally isn't focus
3612023-05-04T19:25:42 <jamesob> really late hi
3622023-05-04T19:25:46 <jon_atack> yes, assumeutxo seems likely for v26 imho
3632023-05-04T19:25:54 <_aj_> i think 324 and package relay could reasonably make it into 26 if we don't stall out on review
3642023-05-04T19:25:57 <jon_atack> as i commented on the current step PR
3652023-05-04T19:25:58 <fanquake> if that was the assumption, why did we even have a vote
3662023-05-04T19:25:59 <brunoerg> I thought we would choose a project that is really close to be ready and it's just needing a nudge on review/dev to get ready
3672023-05-04T19:26:08 <achow101> some things are impossible to do in the next release just due to rollout timing
3682023-05-04T19:26:08 <fanquake> the only obvious choice would be assumeutxo
3692023-05-04T19:26:18 <fanquake> obviously we aren't shipping any of the other projects in 26
3702023-05-04T19:26:19 <stickies-v> i don't think being able to ship in the next release should be a requirement for a project being high prio, although ideally *some* of the high prio projects are shippable
3712023-05-04T19:26:25 <instagibbs> _aj_ the whole project? the crypto library changes aren't even merged for bip213
3722023-05-04T19:26:32 <instagibbs> 324*
3732023-05-04T19:26:44 <instagibbs> we can make huge strides for sure
3742023-05-04T19:27:09 <josie> at least for starting out, not sure if the exact number matters, but if we make progress on one or more of the projects, then id say the prioritization experiment was a success. we can fiddle with the number and process as we go
3752023-05-04T19:27:28 <_aj_> instagibbs: yes?
3762023-05-04T19:27:34 <achow101> we can also aim to ship them, but it's not necessarily failure to not ship
3772023-05-04T19:27:51 <hebasto> achow101: +1
3782023-05-04T19:27:54 <achow101> and the priorities aren't supposed to be things that prevent us from shipping a release
3792023-05-04T19:27:59 <ajonas> if the goal is to get big things in, we need to create an environment where reviewers on focused on those rather than working around the edges. They ship when they ship.
3802023-05-04T19:28:27 <instagibbs> _aj_ I'd love to be proven wrong ofc
3812023-05-04T19:28:33 <josie> ajonas: +1
3822023-05-04T19:28:35 <stickies-v> ajonas: josie +1
3832023-05-04T19:29:08 <_aj_> instagibbs: for me, the main point is being able to pick a PR that's ready to merge, then work on reviewing and merging it, without that work being interrupted by conflicts that force it to get rebased
3842023-05-04T19:29:20 <cfields> As I understood it, we were picking projects that we'd prioritize for a release cycle. For ex, given 2 long-lasting conflicting PR's, one being a priority and one not, the priority project would get the implied focus and merge when ready, potentially relegating the other to a later release. But that doesn't mean that the priority item would be a release blocker.
3852023-05-04T19:29:38 <achow101> cfields: +1
3862023-05-04T19:30:19 <_aj_> instagibbs: i don't see why we couldn't be doing that for all four of the projects above for the next ~5 months or whatever, and have 324 and pkg relay provide usable features in 26
3872023-05-04T19:30:25 <jon_atack> cfields: right. (i reckon that can be resolved on an ad hoc basis when it happens tho)
3882023-05-04T19:30:27 <glozow> fwiw I split package relay into 3 milestones, and I think each one is a reasonable sprint for a release cycle if reviewers are there. I'll commit to responding to feedback and keeping issues updated as fast as possible â
3892023-05-04T19:30:44 <instagibbs> _aj_ definitely, I just didn't think everything would be deliverable
3902023-05-04T19:30:49 <instagibbs> sub-deliverables 100%
3912023-05-04T19:31:17 <achow101> I think we're all relatively on the same page
3922023-05-04T19:31:17 <_aj_> instagibbs: i'd rather be optimistic than give up in advance *shrug*
3932023-05-04T19:31:25 <achow101> we've got more topics for today
3942023-05-04T19:31:42 <achow101> #topic add ryanofsky as maintainer (take 2)
3952023-05-04T19:31:42 <core-meetingbot> topic: add ryanofsky as maintainer (take 2)
3962023-05-04T19:31:44 <instagibbs> _aj_ I like the energy
3972023-05-04T19:31:46 <instagibbs> (sorrY)
3982023-05-04T19:31:52 <achow101> We (the maintainers) felt that there was a need for a maintainer who understood our interfaces and modularization efforts well, and we think that ryanofsky is a good fit for that.
3992023-05-04T19:31:54 <Murch> So, it sounds like we more or less have picked the priorities and clarified what the criteria for a priority and the goal of the process are
4002023-05-04T19:31:55 <jamesob> ACK RUSS
4012023-05-04T19:31:56 <sdaftuar> ack russ
4022023-05-04T19:32:02 <Murch> ACK Russ
4032023-05-04T19:32:04 <jamesob> sdaftuar gets it
4042023-05-04T19:32:08 <hebasto> ACK on Russel
4052023-05-04T19:32:09 <josie> ACK russ
4062023-05-04T19:32:12 <dergoegge> ACK russ
4072023-05-04T19:32:16 <brunoerg> ACK russ
4082023-05-04T19:32:18 <theStack> ACK russ
4092023-05-04T19:32:28 <fjahr> I don't know who russ is but ACK Ryan of Sky
4102023-05-04T19:32:38 <ryanofsky> ack ryan
4112023-05-04T19:32:53 <cfields> ACK Russ
4122023-05-04T19:33:03 <_aj_> ack ryan
4132023-05-04T19:33:14 <lightlike> ACK russ
4142023-05-04T19:33:16 <achow101> seems uncontroversial, we'll take it to github as usual
4152023-05-04T19:33:18 <b10c> ryan ack
4162023-05-04T19:33:18 <instagibbs> ACK russ
4172023-05-04T19:33:19 <furszy> ACK ryan
4182023-05-04T19:33:20 <fanquake> have my ACK russ tshirt on
4192023-05-04T19:33:23 <glozow> ACK
4202023-05-04T19:33:29 <jamesob> fanquake: nice
4212023-05-04T19:33:33 <sipa> ACK russ
4222023-05-04T19:33:37 <cfields> I can't imagine a less controversial candidate :)
4232023-05-04T19:33:40 <BlueMatt> ACK russ (but my vote doesn't count)
4242023-05-04T19:33:58 <josie> BlueMatt: not a vote ;)
4252023-05-04T19:34:18 <stickies-v> ACK russ
4262023-05-04T19:34:36 <achow101> #topic Change IRC meeting time (glozow)
4272023-05-04T19:34:36 <core-meetingbot> topic: Change IRC meeting time (glozow)
4282023-05-04T19:34:43 <glozow> Our current meeting time was decided in 2015 when the group of contributors was fairly different wrt geographic distribution. Several people have expressed wanting to change the meeting time to better-suit our current set of contributors.
4292023-05-04T19:34:49 <glozow> Last week I sent out a doodle. You can see the results here: https://doodle.com/meeting/participate/id/ax25vR3d
4302023-05-04T19:34:59 <jon_atack> I'm not sure what the point of voting on IRC is, as after we saw similar support for Vasil, it became clear that it didn't matter
4312023-05-04T19:35:14 <glozow> 14-15UTC has the most votes.
4322023-05-04T19:35:14 <glozow> Therefore I propose we change our weekly meeting time to Thursdays 14UTC, starting next week (May 11).
4332023-05-04T19:35:14 <jon_atack> and that the real decision was made at a different level
4342023-05-04T19:35:24 <cfields> jon_atack: is that a nack?
4352023-05-04T19:35:48 <jon_atack> cfields: ACK russ, but i think the process is problematic
4362023-05-04T19:35:49 <achow101> jon_atack: it is to get an idea whether to bother opening the github pr in the first place
4372023-05-04T19:36:00 *** Talkless <Talkless!~Talkless@mail.dargis.net> has quit IRC (Quit: Konversation terminated!)
4382023-05-04T19:36:09 <jon_atack> russ is an experienced and dedicated reviewer and long-term contributor
4392023-05-04T19:36:18 <josie> jon_atack: again, just to be clear, not a vote
4402023-05-04T19:36:20 <achow101> the irc meeting is meant for more discussion, if there is any
4412023-05-04T19:36:21 <hebasto> ACK on 1400 UTC
4422023-05-04T19:36:22 <jon_atack> he's clearly passionate about this projet
4432023-05-04T19:36:26 <cfields> jon_atack: roger, thanks for clarifying :)
4442023-05-04T19:36:37 <achow101> ACK on 1400 UTC
4452023-05-04T19:36:40 <stickies-v> ACK 14 UTC
4462023-05-04T19:36:51 <instagibbs> I didn't vote, I was suppressed!!! (I like the change)
4472023-05-04T19:36:51 <_aj_> that's -5 hours to the current time, and still not changing for daylight savings, right?
4482023-05-04T19:36:58 <achow101> _aj_: yes
4492023-05-04T19:37:12 <theStack> ACK 1400 UTC
4502023-05-04T19:37:18 <instagibbs> effective next week ?
4512023-05-04T19:37:22 <achow101> instagibbs: gotta check irc more :) we posted it multiple times
4522023-05-04T19:37:24 <glozow> Yes, effective next week, on May 11
4532023-05-04T19:37:28 <jamesob> 1400 UTC works
4542023-05-04T19:37:28 <fjahr> ACK 14 UTC
4552023-05-04T19:37:33 <brunoerg> ACK 14 UTC
4562023-05-04T19:37:36 <_aj_> and 1 hour before the optech review twitter space i think?
4572023-05-04T19:37:42 <josie> ACK 14 UTC
4582023-05-04T19:37:49 <dergoegge> ACK 14 UTC
4592023-05-04T19:37:51 <fanquake> ACK 14 UTC
4602023-05-04T19:37:54 <instagibbs> achow101 my room temp iq couldnt figure out the poll UX
4612023-05-04T19:37:57 <fanquake> better than 8:00pm
4622023-05-04T19:38:08 <b10c> ACK 14 UTC
4632023-05-04T19:38:18 <b10c> instagibbs: yea the site is terrible UX
4642023-05-04T19:38:38 <instagibbs> to be clear: ACK 14 UTC
4652023-05-04T19:38:43 <jon_atack> 14 UTC isn't a time I'll be able to make
4662023-05-04T19:38:45 <Murch> ACK 14 UTC
4672023-05-04T19:39:27 <achow101> jon_atack: that is unfortunate, but it seems to be the best time for the most contributors
4682023-05-04T19:39:31 <fanquake> sounds like rough consensus
4692023-05-04T19:39:33 <lightlike> 14 utc works for me.
4702023-05-04T19:39:37 <fanquake> ship it next week
4712023-05-04T19:40:09 <Murch> _aj_: Good point, itâs actually in parallel to the Optech Recap :(
4722023-05-04T19:40:48 <josie> Murch: any possibility of moving the optech recap?
4732023-05-04T19:40:54 <_aj_> Murch: oh, is optech on dst?
4742023-05-04T19:41:24 <Murch> We switched it from 15 UTC because it was interfering with Lunch :p
4752023-05-04T19:41:57 <fanquake> not sure your lunch is a higher priority than this meeting tbh
4762023-05-04T19:42:06 <instagibbs> "you can't skip lunch"
4772023-05-04T19:42:09 <sdaftuar> i think there might be other days of the week
4782023-05-04T19:42:25 <fanquake> mate you're making me skip dinner
4792023-05-04T19:42:27 <cfields> Ok, can everyone agree to take lunch at 14utc, meeting at 15utc? :P
4802023-05-04T19:42:33 <ajonas> fanquake: burn +1
4812023-05-04T19:43:08 <glozow> should we have a poll for a different day of the week?
4822023-05-04T19:43:23 <dergoegge> no optech should move the day
4832023-05-04T19:43:27 <achow101> meh
4842023-05-04T19:43:28 <b10c> sunday?
4852023-05-04T19:43:31 <Murch> haha, fanquake: Donât worry, weâre gonna move our thing rather than lobbying for moving the coredev meeting
4862023-05-04T19:43:34 <sdaftuar> yeah i was talking to murch, sorry :)
4872023-05-04T19:43:44 <achow101> Murch: phew
4882023-05-04T19:43:44 <glozow> ah okay
4892023-05-04T19:43:55 <furszy> we can move lunch to sunday
4902023-05-04T19:44:01 <instagibbs> you are allowed to bitch about it for 2 episodes
4912023-05-04T19:44:03 <josie> glozow was already prepping the next doodle for day of week
4922023-05-04T19:44:06 <glozow> Great. Starting next week (May 11), we'll meet at 14UTC.
4932023-05-04T19:44:30 <glozow> nah I never want to use doodle again ð
4942023-05-04T19:44:36 <Murch> as if all of you are listening to our Recap live or smth
4952023-05-04T19:44:40 <achow101> #topic project priorities (what they actually are)
4962023-05-04T19:44:40 <core-meetingbot> topic: project priorities (what they actually are)
4972023-05-04T19:44:42 * Murch shakes his head
4982023-05-04T19:44:56 <glozow> I have not received any DMs
4992023-05-04T19:45:07 <achow101> nor I
5002023-05-04T19:45:27 <dergoegge> well then just take the poll results from core dev
5012023-05-04T19:45:34 <achow101> final counts are Multiprocess - 3, Erlay - 3, BIP 324 - 21, Kernel - 12, AssumeUTXO - 11, Legacy Wallet Removal - 6, Package Relay - 19, ASMap - 3, Silent Payments - 5
5022023-05-04T19:46:03 <achow101> so that would be BIP 324, Package relay, and kernel as our priorities for 26.0?
5032023-05-04T19:46:34 <sdaftuar> can you remind us of the champions of each project?
5042023-05-04T19:46:35 <fanquake> I would suggest swapping kernel for assumeutxo. I think kernel stage 1 will complete shortly, and stage 2 wont interfere with other priorities
5052023-05-04T19:46:38 <glozow> Can we hear from the people who are championing these projects?
5062023-05-04T19:46:51 <theStack> fanquake: +1
5072023-05-04T19:47:04 <fanquake> is thecharlatan here?
5082023-05-04T19:47:09 <jamesob> What I'll say is that assumeutxo is "nice to have" relative to BIP324 and package relay, albeit it's pretty close
5092023-05-04T19:47:09 <Murch> TheCharlatan: ?
5102023-05-04T19:47:10 <achow101> BIP 324 is sipa, package relay is glozow, and kernel is TheCharlatan
5112023-05-04T19:47:14 <_aj_> why not both assumeutxo and kernel?
5122023-05-04T19:47:17 *** jonatack1 <jonatack1!~jonatack@user/jonatack> has joined #bitcoin-core-dev
5132023-05-04T19:47:21 <instagibbs> jamesob is assumeutxo
5142023-05-04T19:47:23 <jamesob> (i.e. BIP324 and package relay are more critical IMO)
5152023-05-04T19:47:26 <TheCharlatan> yes, still need to catch up
5162023-05-04T19:47:27 <fanquake> _aj_: yea that's what I mean essentiallyu
5172023-05-04T19:47:33 <achow101> _aj_: that seems possible too
5182023-05-04T19:47:55 <jamesob> kernel IMO needs some time to bake in terms of itnerface design... that can't be done overnight
5192023-05-04T19:47:57 <_aj_> if four projects is too many, we'll hopefully realise it at the weekly priority reviews relatively quickly
5202023-05-04T19:48:00 <jamesob> *interface
5212023-05-04T19:48:06 <fjahr> Again, three priorities isn't really focus. We will see the same result as with the high priorities board IMO.
5222023-05-04T19:48:09 <fanquake> Kernel is going to progress in any case, but once the finaly stage 1 prs are done, which they are not many of, it'll be out of the way, and stage 2 is more exploratory/non-conflicting, so can progress, and assumeutxo can be completed
5232023-05-04T19:48:15 <_aj_> and if a priority project just doesn't have a priority pr for a few weeks, that seems fine?
5242023-05-04T19:48:28 <instagibbs> fjahr pick the two you like then, if everyone picks two...
5252023-05-04T19:49:25 <fjahr> instagibbs It's not on me to decide, I am fine with the two that got the most votes
5262023-05-04T19:49:35 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 260 seconds)
5272023-05-04T19:50:01 <sdaftuar> i think the main issue is reviewers; knowing that there are a lot of people stating an interest in review is helpful, as is knowing who those people are (so they can be bugged when needed)
5282023-05-04T19:50:04 <jonatack1> in any case, people doing review is what moves the dial
5292023-05-04T19:50:15 <achow101> fjahr: I don't think it will be the same as we will be asking for updates each week
5302023-05-04T19:50:38 <stickies-v> If kernel is gonna be merged in a few weeks then it'll stop being high prio at that point and we can vote on a next high prio, e.g. assumeutxo?
5312023-05-04T19:50:46 <stickies-v> (phase 1)
5322023-05-04T19:51:06 <_aj_> it might be worth having 3 or 4 reviewers stick their hands up for each priority project, as well as a champion? (perhaps you can only be a nominated reviewer for one project, even if you're actually review multiple ones)
5332023-05-04T19:51:08 <sdaftuar> for my part -- i'm happy to review package relay and assumeutxo in the near term.
5342023-05-04T19:51:32 <sdaftuar> (assuming that others are lined up as well!)
5352023-05-04T19:51:41 <_aj_> 324+pkgrelay for me
5362023-05-04T19:51:46 <achow101> someone will need to make a bip324 tracking issue
5372023-05-04T19:51:47 <TheCharlatan> ACK for swapping as fanquake suggested, there's maybe like 2-3 stage 1 PRs left. 1 to clean the left over gArgs that I should draft on second thought, and by the looks of it 2 for handling shutdown.
5382023-05-04T19:51:50 <instagibbs> I'll be focusing on BIP324 and package relay. I can champion either in limited ways
5392023-05-04T19:52:34 <jamesob> I'm going to be looking at 324, as well as staying on top of assumeutxo as best I can. I have little doubt that others are going to want to see more automated testing than I have built for those changes currently.
5402023-05-04T19:52:38 <stickies-v> Package relay and kernel for me
5412023-05-04T19:52:40 <lightlike> I'll review the non-crypto content from bip324, plus the p2p content from pkgrelay
5422023-05-04T19:52:40 <fanquake> instagibbs: i'll get you a participation trophy
5432023-05-04T19:53:00 <achow101> TheCharlatan: is there a tracking issue for kernel?
5442023-05-04T19:53:11 <instagibbs> fanquake CoC violation
5452023-05-04T19:53:19 <TheCharlatan> I'm working on a new one.
5462023-05-04T19:53:28 <fanquake> Carl had one, but it likely needs some updating. Maybe we can start a-fresh for V2 atleast
5472023-05-04T19:53:40 <fanquake> TheCharlatan: great
5482023-05-04T19:53:45 <theStack> i'll focus mainly on bip324 review (mostly non-secp stuff, ofc)
5492023-05-04T19:54:21 <achow101> added draft items for kernel and 324. will followup later
5502023-05-04T19:54:36 <jonatack1> kernel and assumeutxo for me, most likely. more generally, i think what makes a difference is incentivizing the importance of reviewers as the key role.
5512023-05-04T19:54:49 <instagibbs> achow101 you'll make sure someone is making tracking issues for those two projects you're saying?
5522023-05-04T19:54:55 <achow101> instagibbs: yes
5532023-05-04T19:54:59 <instagibbs> thanks
5542023-05-04T19:55:01 <glozow> for package relay. I'm happy to keep the tracking issue updated and give weekly updates at the meetings (now that we have a new meeting time). Sometimes it might take me some time to implement things but I'll be as responsive as possible. please feel free to ping me in this channel. I nominate _aj_, sdaftuar, instagibbs as potential champions if I get hit by a bus. for those of you who said you'll review, I will take liberties in nagging
5552023-05-04T19:55:01 <glozow> y'all :P
5562023-05-04T19:56:08 <instagibbs> 4 minutes left
5572023-05-04T19:56:17 <achow101> Any other topics?
5582023-05-04T19:56:36 <fanquake> Test the most recent release candidates
5592023-05-04T19:56:53 <fanquake> bins are available
5602023-05-04T19:57:00 <Murch> Iâm making progress on fuzzing for the qa-assets
5612023-05-04T19:57:17 <achow101> yeah, 24.1rc2 and 25.0rc1 are both up
5622023-05-04T19:57:30 <fanquake> We'll cut a 24.1 quite soon, if no issues come up
5632023-05-04T19:57:33 <Murch> Oh, should I also fuzz for 24.1?
5642023-05-04T19:57:45 <achow101> #endmeeting
5652023-05-04T19:57:45 <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
5662023-05-04T19:57:46 <core-meetingbot> Meeting ended Thu May 4 19:57:45 2023 UTC.
5672023-05-04T19:57:46 <core-meetingbot> Minutes: https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/2023/bitcoin-core-dev.2023-05-04-19.00.moin.txt
5682023-05-04T19:57:48 <Murch> Iâve just been fuzzing for 25.0
5692023-05-04T19:58:03 <glozow> Great meeting
5702023-05-04T19:58:26 <josie> glozow: make irc lively again
5712023-05-04T19:58:28 <fanquake> #productive
5722023-05-04T19:58:36 <sdaftuar> jamesob: i managed to load a utxo set (i think). hacked in a new rpc that takes a dumptxoutset from another node. however! it is taking forever to flush the chainstate to disk. is that what you have observed as well or is my computer just bad?
5732023-05-04T19:58:40 <Murch> glozow: +1
5742023-05-04T19:59:01 <jamesob> sdaftuar: yep, that's the longest part of the load process for sure. How long we talking?
5752023-05-04T19:59:05 <achow101> TheCharlatan: what's the next pr for kernel?
5762023-05-04T19:59:15 <jamesob> Shouldn't be more than ~10 minutes...
5772023-05-04T19:59:26 <sdaftuar> i'm at over 20 already, still going
5782023-05-04T19:59:30 <jamesob> zoinks
5792023-05-04T19:59:37 <jamesob> spinning disk or ssd?
5802023-05-04T19:59:44 <sdaftuar> close to 30 minutes. spinning disk yeah
5812023-05-04T19:59:53 <_aj_> https://github.com/bitcoin-core/bitcoin-devwiki/wiki/Priorities -- if anyone wants to add themselves there, maybe
5822023-05-04T20:00:05 <sdaftuar> also maybe my btrfs filesystem is not optimized for this... i think i might have mirroring of data enabled
5832023-05-04T20:00:31 <jamesob> for what it's worth I've got a bunch of new changes on #15606 as of the last few days... once CI passes, I'll be posting comprehensive instructions for testing it out
5842023-05-04T20:00:33 <gribble> https://github.com/bitcoin/bitcoin/issues/15606 | assumeutxo by jamesob · Pull Request #15606 · bitcoin/bitcoin · GitHub
5852023-05-04T20:00:38 <achow101> _aj_: also revamping the high priority board: https://github.com/orgs/bitcoin/projects/1/views/1
5862023-05-04T20:00:38 <sdaftuar> oh sweet
5872023-05-04T20:00:55 <sdaftuar> i'm going to try to test some download logic... if this flush every finishes!
5882023-05-04T20:01:06 <jamesob> :)
5892023-05-04T20:01:09 <fanquake> meeting barely over and there's already assumeutxo progress
5902023-05-04T20:01:16 <fjahr> jamesob: turns out assumeutxo is slower than syncing the chain? ;)
5912023-05-04T20:01:32 <jamesob> fjahr: don't send me into retirement
5922023-05-04T20:01:55 <_aj_> achow101: drop the "needs rebase" ad-hoc entries and pkg relay from chasing concept ack?
5932023-05-04T20:03:42 <achow101> _aj_: done
5942023-05-04T20:05:12 <fjahr> achow101: did you change your mind about dropping the board? I thought you put that on the agenda as a topic :)
5952023-05-04T20:06:21 <TheCharlatan> achow101 next one is getting rid of whatever gArgs are still left over (I'll open it in a bit). Still working on shutdown, so don't know when that will be ready.
5962023-05-04T20:06:52 <achow101> fjahr: yeah, I did
5972023-05-04T20:06:57 <cfields> TheCharlatan: oh, you decided to tackle shutdown afterall? What approach?
5982023-05-04T20:06:57 *** abubakarsadiq <abubakarsadiq!~abubakars@102.91.53.60> has quit IRC (Read error: Connection reset by peer)
5992023-05-04T20:07:55 <cfields> Or you mean more like dealing with our current shutdown behavior?
6002023-05-04T20:07:56 <jonatack1> jamesob: nice, i'll be looking out for those changes on 15606 and the testing info
6012023-05-04T20:14:13 <TheCharlatan> cfields, yeah, the discussion you brought up at last week's meeting made me think it over. Currently I am tending towards a polymorphic solution that either wraps the current behaviour, or provides kernel users with enough context to handle destruction.
6022023-05-04T20:14:16 *** kevkevin_ <kevkevin_!~kevkevin@2601:241:8703:7b30:fdf9:a35f:16d7:9b75> has quit IRC (Remote host closed the connection)
6032023-05-04T20:16:46 <cfields> TheCharlatan: ack. I had been thinking it through since the discussion and arrived at throwing and catching at our boundary, then bubbling up to the user from there as an error and letting them handle as you mentioned.
6042023-05-04T20:17:09 <cfields> happy to review or work through it with you. It's kept me up plenty of nights :)
6052023-05-04T20:17:43 <cfields> Also I have commits which demonstrate the callgraphs if that'd be helpful...
6062023-05-04T20:18:49 <TheCharlatan> cfields: yes, it would :)
6072023-05-04T20:21:50 <cfields> TheCharlatan: roger. Will generate it for you tomorrow.
6082023-05-04T20:30:39 <theStack> sdaftuar: just to understand your assumeutxo test scenario better (as i also plan to play around with it soon), what's the difference between the `loadtxoutset` RPC in #15606 and the one you hacked in?
6092023-05-04T20:30:40 <gribble> https://github.com/bitcoin/bitcoin/issues/15606 | assumeutxo by jamesob · Pull Request #15606 · bitcoin/bitcoin · GitHub
6102023-05-04T20:36:42 *** ChanServ sets mode: +o achow101
6112023-05-04T20:37:40 *** ChanServ sets mode: -o achow101
6122023-05-04T20:38:18 *** ChanServ changes topic to "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/ | Weekly Meeting Thursday @ 14:00 UTC | Meeting topics http://gnusha.org/bitcoin-core-dev/proposedmeetingtopics.txt / http://gnusha.org/bitcoin-core-dev/proposed"
6132023-05-04T20:46:41 *** Guest82 <Guest82!~Guest82@24-116-104-19.cpe.sparklight.net> has joined #bitcoin-core-dev
6142023-05-04T20:47:59 *** Guest82 <Guest82!~Guest82@24-116-104-19.cpe.sparklight.net> has quit IRC (Client Quit)
6152023-05-04T21:08:47 <sdaftuar> theStack: oh, thanks for the link! I didn't know where to find james' implementation
6162023-05-04T21:09:28 <sdaftuar> i think my implementation is a worse version of jamesob's, but accomplishes the same thing :)
6172023-05-04T21:10:11 <sdaftuar> i did have to add the blockhash from my dumptxoutset command (and the block height) to chainparams as a valid assumeutxo value.
6182023-05-04T21:33:02 *** jonatack1 <jonatack1!~jonatack@user/jonatack> has quit IRC (Quit: WeeChat 3.8)
6192023-05-04T21:33:46 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
6202023-05-04T21:36:43 <bitcoin-git> [bitcoin] TheCharlatan opened pull request #27576: kernel: Remove args, chainparams, chainparamsbase from kernel library (master...rmKernelArgs) https://github.com/bitcoin/bitcoin/pull/27576
6212023-05-04T21:41:44 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Remote host closed the connection)
6222023-05-04T21:42:58 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
6232023-05-04T21:47:08 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 240 seconds)
6242023-05-04T21:49:05 *** kevkevin <kevkevin!~kevkevin@144.121.170.186> has joined #bitcoin-core-dev
6252023-05-04T21:54:15 *** preimage <preimage!~halosghos@user/halosghost> has quit IRC (Quit: WeeChat 3.8)
6262023-05-04T21:59:30 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
6272023-05-04T22:03:48 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 240 seconds)
6282023-05-04T22:12:15 <ariard> ACK Russ maintainer + ACK 1400 UTC Thurs. new meeting schedule + package relay as my review prio
6292023-05-04T22:14:00 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
6302023-05-04T22:21:25 <bitcoin-git> [bitcoin] mzumsande opened pull request #27577: p2p: give seednodes time before falling back to fixed seeds (master...202304_seednode_fixedseed_interaction) https://github.com/bitcoin/bitcoin/pull/27577
6312023-05-04T22:21:43 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
6322023-05-04T22:26:08 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 248 seconds)
6332023-05-04T22:27:47 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
6342023-05-04T22:28:17 <_aj_> TheCharlatan: thought you mean remove kernel/chainparams*.cpp from kernel when i saw that title :)
6352023-05-04T22:32:27 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 260 seconds)
6362023-05-04T22:33:02 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
6372023-05-04T22:35:38 *** aielima <aielima!~aielima@user/aielima> has quit IRC (Quit: Ciao)
6382023-05-04T22:37:28 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 240 seconds)
6392023-05-04T22:37:40 <glozow> ariard: ððð
6402023-05-04T22:46:35 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
6412023-05-04T22:51:30 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 265 seconds)
6422023-05-04T22:57:22 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
6432023-05-04T23:03:13 *** kevkevin <kevkevin!~kevkevin@144.121.170.186> has quit IRC (Remote host closed the connection)
6442023-05-04T23:04:39 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 260 seconds)
6452023-05-04T23:07:27 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 265 seconds)
6462023-05-04T23:11:01 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
6472023-05-04T23:12:57 <bitcoin-git> [bitcoin] benthecarman opened pull request #27578: Allow accepting non-standard transactions on mainnet (master...non-std-tx-mainnet) https://github.com/bitcoin/bitcoin/pull/27578
6482023-05-04T23:16:07 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 268 seconds)
6492023-05-04T23:17:44 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
6502023-05-04T23:24:47 <theStack> sdaftuar: nice! that's very instructive for sure. i'm going the way easier testing route, running james' pr (which already has the assumeutxo values filled in for height 788000) and trying to load the snapshot
6512023-05-04T23:25:31 <theStack> ./contrib/devtools/utxo_snapshot.sh is useful btw for creating a snapshot at height N, only discovered that after doing the rewind manually
6522023-05-04T23:33:51 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
6532023-05-04T23:38:43 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 260 seconds)
6542023-05-04T23:42:37 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has quit IRC (Quit: Leaving)
6552023-05-04T23:44:38 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
6562023-05-04T23:49:30 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 265 seconds)
6572023-05-04T23:50:42 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has joined #bitcoin-core-dev
6582023-05-04T23:55:08 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:4453:70a1:fac9:eff9> has quit IRC (Ping timeout: 240 seconds)