--- Log opened Fri Oct 28 00:00:00 2022
00:03 -!- mekster669494 [~mekster@user/mekster] has joined #bitcoin-core-dev
00:04 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
00:04 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
00:05 -!- mekster66949 [~mekster@user/mekster] has quit [Ping timeout: 260 seconds]
00:05 -!- mekster669494 is now known as mekster66949
00:11 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
00:11 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
00:12 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
00:16 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 276 seconds]
00:17 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
00:18 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
00:19 < bitcoin-git> [bitcoin] jbrr opened pull request #26408: test: Remove spam from debug log (master...2210-fix-noisy-tests) https://github.com/bitcoin/bitcoin/pull/26408
00:24 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
00:24 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
00:28 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
00:30 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
00:31 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
00:33 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Ping timeout: 255 seconds]
00:35 -!- dermoth [~dermoth@user/dermoth] has quit [Ping timeout: 244 seconds]
00:37 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
00:37 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
00:42 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
00:43 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
00:43 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
00:46 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
00:47 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
00:50 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
00:50 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
00:50 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Ping timeout: 240 seconds]
00:51 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 240 seconds]
00:56 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
00:56 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
01:03 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
01:03 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
01:04 -!- dviola [~diego@179.235.13.211] has left #bitcoin-core-dev []
01:06 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
01:06 -!- dviola [~diego@user/dviola] has joined #bitcoin-core-dev
01:09 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
01:09 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
01:16 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
01:16 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
01:23 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
01:23 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
01:30 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
01:30 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
01:36 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
01:36 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
01:38 -!- amovfx_ [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
01:42 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
01:43 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
01:45 -!- Evel-Knievel [~Evel-Knie@user/evel-knievel] has quit [Ping timeout: 272 seconds]
01:45 -!- Evel-Knievel [~Evel-Knie@user/evel-knievel] has joined #bitcoin-core-dev
01:49 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
01:49 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
01:52 -!- gnaf [~gnaf@212-83-182-127.rev.poneytelecom.eu] has joined #bitcoin-core-dev
01:56 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
01:56 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
02:00 -!- cotsuka [~cotsuka@user/cotsuka] has quit [Quit: You have been kicked for being idle]
02:02 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
02:03 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
02:09 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 246 seconds]
02:09 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
02:09 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
02:11 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #26409: refactor: Silence GCC Wmissing-field-initializers in ChainstateManagerOpts (master...2210-gcc-🏾) https://github.com/bitcoin/bitcoin/pull/26409
02:16 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
02:17 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
02:20 -!- dermoth [~dermoth@user/dermoth] has joined #bitcoin-core-dev
02:23 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
02:23 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
02:30 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
02:30 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
02:30 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
02:33 -!- robertnielsen [~robertnie@c-67-164-56-127.hsd1.ca.comcast.net] has quit [Quit: Client closed]
02:33 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/f37bd15d472f...1bad29fe0209
02:33 < bitcoin-git> bitcoin/master 884304e Hennadii Stepanov: test: Make `system_tests/run_command` locale agnostic
02:33 < bitcoin-git> bitcoin/master 1bad29f MacroFake: Merge bitcoin/bitcoin#26377: test: Make `system_tests/run_command` test lo...
02:33 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #26377: test: Make `system_tests/run_command` test locale and platform agnostic (master...221024-nonloc) https://github.com/bitcoin/bitcoin/pull/26377
02:34 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 276 seconds]
02:36 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
02:37 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
02:37 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
02:40 -!- amovfx_ [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Ping timeout: 255 seconds]
02:43 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
02:44 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
02:45 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 255 seconds]
02:47 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
02:50 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
02:50 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
02:53 -!- amovfx_ [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
02:56 -!- lowhope [~lowhope@2602:fffa:fff:108a:0:16:3e86:c70e] has quit [Remote host closed the connection]
02:56 -!- mikehu44_ [~quassel@159.65.11.175] has joined #bitcoin-core-dev
02:56 -!- lowhope [~lowhope@2602:fffa:fff:108a:0:16:3e86:c70e] has joined #bitcoin-core-dev
02:57 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
02:57 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
02:58 -!- amovfx_ [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Ping timeout: 276 seconds]
03:00 -!- mikehu44 [~quassel@159.65.11.175] has quit [Ping timeout: 250 seconds]
03:01 -!- mikehu44 [~quassel@159.65.11.175] has joined #bitcoin-core-dev
03:02 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Remote host closed the connection]
03:03 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
03:04 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
03:04 -!- mikehu44_ [~quassel@159.65.11.175] has quit [Ping timeout: 246 seconds]
03:04 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
03:09 < bitcoin-git> [bitcoin] fanquake opened pull request #26410: [24.x] rc3 backports (24.x...24_x_rc3) https://github.com/bitcoin/bitcoin/pull/26410
03:10 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
03:11 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
03:17 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
03:18 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
03:20 -!- jarthur_ [~jarthur@user/jarthur] has joined #bitcoin-core-dev
03:21 < bitcoin-git> [bitcoin] fanquake opened pull request #26411: [23.1] Backports (23.x...23_1_backports) https://github.com/bitcoin/bitcoin/pull/26411
03:22 -!- jarthur [~jarthur@user/jarthur] has quit [Ping timeout: 250 seconds]
03:24 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
03:24 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
03:26 -!- amovfx_ [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
03:29 -!- dviola [~diego@user/dviola] has quit [Ping timeout: 272 seconds]
03:31 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
03:31 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
03:38 -!- greypw2546002 [~greypw254@grey.pw] has quit [Remote host closed the connection]
03:38 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
03:45 -!- greypw2546002 [~greypw254@grey.pw] has quit [Read error: Connection reset by peer]
03:46 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
03:50 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 246 seconds]
03:54 -!- greypw2546002 [~greypw254@grey.pw] has quit [Quit: I'll be back!]
03:54 < bitcoin-git> [bitcoin] fanquake opened pull request #26413: [22.1] Backports (22.x...22_1_backports) https://github.com/bitcoin/bitcoin/pull/26413
03:56 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
03:58 -!- greypw2546002 [~greypw254@grey.pw] has quit [Client Quit]
04:03 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Remote host closed the connection]
04:07 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
04:12 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 255 seconds]
04:25 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
04:30 -!- amovfx_ [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Ping timeout: 252 seconds]
04:34 -!- dviola [~diego@user/dviola] has joined #bitcoin-core-dev
04:34 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
04:44 -!- greypw2546002 [~greypw254@grey.pw] has joined #bitcoin-core-dev
04:44 -!- Hariom [~Hariom@122.15.1.49] has joined #bitcoin-core-dev
04:45 -!- Hariom [~Hariom@122.15.1.49] has left #bitcoin-core-dev []
04:58 -!- amovfx_ [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
04:59 -!- Hariom [~Hariom@122.15.1.49] has joined #bitcoin-core-dev
05:03 -!- gnaf [~gnaf@212-83-182-127.rev.poneytelecom.eu] has quit [Quit: Konversation terminated!]
05:03 -!- amovfx_ [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Ping timeout: 246 seconds]
05:04 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 258 seconds]
05:04 -!- Hariom [~Hariom@122.15.1.49] has quit [Quit: Client closed]
05:18 -!- Hariom [~Hariom@122.15.1.49] has joined #bitcoin-core-dev
05:27 -!- Talkless [~Talkless@217.8.174.100] has joined #bitcoin-core-dev
05:29 -!- Talkless [~Talkless@217.8.174.100] has quit [Client Quit]
05:29 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 260 seconds]
05:32 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
05:42 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
05:42 -!- Guest10 [~Guest10@1.47.31.252] has joined #bitcoin-core-dev
05:46 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 246 seconds]
05:57 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has joined #bitcoin-core-dev
05:57 -!- yanmaani2 [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Remote host closed the connection]
05:58 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:e80b:bd98:c870:7b36] has joined #bitcoin-core-dev
05:59 -!- yanmaani2 [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
06:00 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
06:06 -!- Guest10 [~Guest10@1.47.31.252] has quit [Quit: Client closed]
06:13 -!- halosghost [~halosghos@user/halosghost] has joined #bitcoin-core-dev
06:36 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Ping timeout: 260 seconds]
06:50 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
06:53 < bitcoin-git> [bitcoin] instagibbs closed pull request #26265: POLICY: Relax MIN_STANDARD_TX_NONWITNESS_SIZE to 65 non-witness bytes (master...relax_too_small_tx) https://github.com/bitcoin/bitcoin/pull/26265
06:54 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Ping timeout: 260 seconds]
07:02 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 260 seconds]
07:11 < bitcoin-git> [bitcoin] kouloumos opened pull request #26414: test: Move tx creation to create_self_transfer_multi (master...modify-create_self_transfer) https://github.com/bitcoin/bitcoin/pull/26414
07:13 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
07:22 -!- mikehu44 [~quassel@159.65.11.175] has quit [Ping timeout: 276 seconds]
07:34 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #26278: test: Actually set sequence in MiniWallet create_self_transfer_multi (master...2210-test-seq-🕕) https://github.com/bitcoin/bitcoin/pull/26278
07:37 -!- pablomartin [~pablomart@82.180.147.184] has joined #bitcoin-core-dev
07:50 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
07:50 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:e80b:bd98:c870:7b36] has quit [Remote host closed the connection]
07:51 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:e80b:bd98:c870:7b36] has joined #bitcoin-core-dev
07:55 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 252 seconds]
07:55 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:e80b:bd98:c870:7b36] has quit [Ping timeout: 252 seconds]
08:05 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
08:10 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #25949: doc: clarify `blocksdir` setting (master...patch-1) https://github.com/bitcoin/bitcoin/pull/25949
08:19 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:e80b:bd98:c870:7b36] has joined #bitcoin-core-dev
08:20 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Ping timeout: 276 seconds]
08:23 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:e80b:bd98:c870:7b36] has quit [Ping timeout: 264 seconds]
08:27 < bitcoin-git> [bitcoin] andrewtoth opened pull request #26415: rpc,rest: read raw block in getblock verbosity 0 and rest_block bin and hex (master...read-raw-block) https://github.com/bitcoin/bitcoin/pull/26415
08:30 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:e80b:bd98:c870:7b36] has joined #bitcoin-core-dev
08:35 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:e80b:bd98:c870:7b36] has quit [Ping timeout: 246 seconds]
08:39 < willcl_ark> There are 10 PRs which have not responded to a request for update from achow101  in 16 days and could perhaps therefore be closed for inactivity?: https://gist.github.com/willcl-ark/23e36aba1bf270c686f51f52319e19b4
08:44 -!- brunoerg [~brunoerg@187.183.43.178] has joined #bitcoin-core-dev
08:50 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
08:51 -!- theStack [~theStack@95.179.145.232] has quit [Remote host closed the connection]
08:52 -!- pablomartin [~pablomart@82.180.147.184] has quit [Ping timeout: 246 seconds]
08:54 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Ping timeout: 255 seconds]
08:55 -!- lbia [~lbia@user/lbia] has quit [Ping timeout: 250 seconds]
08:57 -!- lbia [~lbia@user/lbia] has joined #bitcoin-core-dev
09:08 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
09:08 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 260 seconds]
09:10 < aureleoules> https://convos.home.aureleoules.com/file/1/HrX3FDfRx6R49yn5
09:11 < aureleoules> Hello!
09:11 < aureleoules> Since Drahtbot is now open-source, I would like to improve it so that the bot can create a summary comment at the top of every (new) pull request showing some information related to it.
09:12 < aureleoules> The comment would be live-updated with the current (N)ACKs, Concept (N)ACKs, Approach (N)ACKs, Code Review ACKs, Approach (N)ACKs, and Stale ACKs. The comment would also list the conflicting pulls.
09:12 < aureleoules> Whenever a user would push to the PR, raw ACKs will be removed from the summary comment and placed as "stale".
09:12 < aureleoules> This would allow reviewers to quickly glance at the review stage of the PR by looking at the top comment, before scrolling down to the potential hundreds of comments.
09:12 < aureleoules> This would require DrahtBot to comment on every new pull request to claim the first comment.
09:12 < aureleoules> Is this feature something that you would find useful?
09:12 < aureleoules> Here's a screenshot of what it could look like: https://user-images.githubusercontent.com/22493292/198647218-dab2c166-411f-4fe2-8069-196ad80d454a.png
09:12 < aureleoules> And here's the link to the GitHub thread where I'm discussing the idea with MacroFake and kouloumos: https://github.com/MarcoFalke/DrahtBot/pull/1#discussion_r1008144498
09:16 < darosior> Don't know about the ACKs. But wasn't that you who had a script to expand all the hidden comments on the page? That could be useful to have a tiny link in Drahbot's ubiquitous conflict message to expand all comments at once. The PRs where you want to unroll comments almost always have the conflict comment (since they tend to be large), so this
09:16 < darosior> would not need to add a new message to every PR.
09:16 < achow101> willcl_ark: I was planning on closing after 1 month
09:17 < achow101> aureleoules: I think it would be useful to have an ACK tracker
09:19 < aureleoules> darosior: that's me! Though since I wrote the script I found an amazing browser extension that does this (if you alt+click) on the 'Load more comments' button. And many other cool things: https://github.com/refined-github/refined-github if you're interested
09:20 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
09:21 < aureleoules> The conflict message can be found but IMO it still takes time to find it, whereas having it as the first comment is much easier. Other information useful to the PR could be added later such as whether the PR is stale, if there are unaddressed review comments?
09:22 < aureleoules> achow101: you mean as an external tool or in the summary comment as I described?
09:23 < achow101> in the summary comment
09:23 < achow101> if drahtbot could also always be the first comment, that'd be great
09:23 < achow101> sometimes it's slow to post
09:25 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 252 seconds]
09:33 -!- zeropoint [~alex@c-67-169-157-130.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
09:34 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
09:35 -!- yanmaani2 [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Remote host closed the connection]
09:37 -!- yanmaani2 [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
09:50 < jon_atack> aureleoules: nice, I agree that your first-comment ACK summary would be useful
09:52 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
09:56 < brunoerg> aureleoules: interesting idea, especially about the stale after a push
10:01 < aureleoules> great, thanks for the feedback achow101 jon_atack brunoerg
10:02 < aureleoules> the stale acks thing is kouloumos's original idea :)
10:10 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Ping timeout: 246 seconds]
10:24 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
10:29 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Ping timeout: 255 seconds]
10:38 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
10:38 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Quit: Leaving...]
10:40 < vasild> aureleoules: looks nice
10:43 < vasild> tACK is not mentioned in CONTRIBUTING.md, it is kind of unofficial
10:43 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 260 seconds]
10:45 < vasild> because there are usually less than ~10 ACKs maybe there is no such big need to group them. If you group then you have to consider what to do with all kinds of "semi ACK ...", "almost ACK ..." "I would ACK this if it is blue" "etc ACK and whatnot"
10:45 < aureleoules> The screenshot is not really up-to-date with what I'm going to implement. The ACKs that will be listed are (N)ACKs, Concept (N)ACKs, Approach (N)ACKs, Code Review ACKs, Approach (N)ACKs, and Stale ACKs. But some are aliased such as "crACK", "CR ACK", "re-crACK" for Code Review ACK, or tACK, utACK, reACK, re-ACK for `ACK` for example.
10:46 < aureleoules> usually if someone acks on a condition, such as a comment needs to be addressed, the commit hash is not provided (from what I've seen). So raw ACKs won't be taken into account if there PR HEAD's hash is not provided
10:47 < aureleoules> if the* PR HEAD's hash is not provided
10:47 < vasild> hmm, right
10:48 < vasild> cool stuff :)
10:49 < aureleoules> thanks :)
10:50 < bitcoin-git> [bitcoin] achow101 closed pull request #24975: bench: remove from available_coins with reference, vout size (master...pool_bench) https://github.com/bitcoin/bitcoin/pull/24975
10:51 < aureleoules> Though what I need to worry about are quoted ACKs when replying, someone might quote a Concept ACK or even a raw ACK
10:52 < aureleoules> that should be fixed by only taking into account ACKs that are the first words of a comment, which is usually the case i think?
10:54 < aureleoules> I don't think the maintainer merge-script checks for quoted acks by the way
10:56 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
10:58 -!- jarthur_ is now known as jarthur
11:06 -!- gnaf [~gnaf@212-83-182-127.rev.poneytelecom.eu] has joined #bitcoin-core-dev
11:07 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has left #bitcoin-core-dev [Closing Window]
11:26 < jon_atack> aureleoules: i'm not sure "comment starts with ACK" is a good enough heuristic, e.g. "This seems to address x, y, z, so Concept ACK for me", but I could be wrong in recalling seeing review comments like that.
11:27 < jon_atack> ah, unless you don't count ACKs without the commit hash
11:29 < brunoerg> aureleoules: Does it stale a "concept ACK" after a push? 
11:31 -!- jarthur [~jarthur@user/jarthur] has quit [Read error: Connection reset by peer]
11:31 < aureleoules> Concept ACKs don't need a commit hash, so you're right jon_atack it can't only be the first words of the sentence
11:32 < aureleoules> it should probably be enough to check that the line is not quoted (doesn't start with '>')
11:32 -!- jarthur [~jarthur@user/jarthur] has joined #bitcoin-core-dev
11:33 < aureleoules> so no brunoerg, Concept ACKs won't get stale, only ACKs (also tACK, utACK, reACKs etc)
11:34 < brunoerg> Cool, it's what i was thinking, thanks
11:42 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Ping timeout: 252 seconds]
11:45 -!- dongcarl [~dongcarl@cpe-66-65-184-36.nyc.res.rr.com] has joined #bitcoin-core-dev
11:54 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 252 seconds]
11:58 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 240 seconds]
12:07 < bitcoin-git> [bitcoin] achow101 opened pull request #26416: Initialize optional members of ChainstateManagerOpts to nullopt (master...fix-warnings) https://github.com/bitcoin/bitcoin/pull/26416
12:11 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 264 seconds]
12:11 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
12:16 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Ping timeout: 260 seconds]
12:19 < bitcoin-git> [bitcoin] achow101 closed pull request #26416: Initialize optional members of ChainstateManagerOpts to nullopt (master...fix-warnings) https://github.com/bitcoin/bitcoin/pull/26416
12:22 -!- Hariom [~Hariom@122.15.1.49] has quit [Quit: Client closed]
12:27 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
12:33 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 255 seconds]
12:38 < bitcoin-git> [bitcoin] achow101 pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/1bad29fe0209...8b050762b1b4
12:38 < bitcoin-git> bitcoin/master fa29ef0 MacroFake: refactor: Silence GCC Wmissing-field-initializers in ChainstateManagerOpts
12:38 < bitcoin-git> bitcoin/master 8b05076 Andrew Chow: Merge bitcoin/bitcoin#26409: refactor: Silence GCC Wmissing-field-initiali...
12:38 < bitcoin-git> [bitcoin] achow101 merged pull request #26409: refactor: Silence GCC Wmissing-field-initializers in ChainstateManagerOpts (master...2210-gcc-🏾) https://github.com/bitcoin/bitcoin/pull/26409
12:44 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
12:46 -!- brunoerg [~brunoerg@187.183.43.178] has quit []
12:47 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
12:59 -!- ExEric3 [~exeric3@dbox.miners-zone.net] has quit [Remote host closed the connection]
13:00 -!- ExEric3 [~exeric3@mail.miners-zone.net] has joined #bitcoin-core-dev
13:08 < bitcoin-git> [bitcoin] mzumsande opened pull request #26417: test: fix intermittent failure in feature_index_prune.py (master...202210_testfix_indexprune) https://github.com/bitcoin/bitcoin/pull/26417
13:23 -!- Guest9086 [~Guest90@86.32.48.152] has joined #bitcoin-core-dev
13:28 -!- Guest9086 [~Guest90@86.32.48.152] has left #bitcoin-core-dev []
13:29 -!- Guest904 [~Guest90@86.32.48.152] has joined #bitcoin-core-dev
13:29 -!- Guest904 [~Guest90@86.32.48.152] has quit [Client Quit]
13:43 -!- gnaf [~gnaf@212-83-182-127.rev.poneytelecom.eu] has quit [Quit: Konversation terminated!]
13:46 -!- NorrinRadd [~me@85.237.194.16] has joined #bitcoin-core-dev
13:49 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Ping timeout: 246 seconds]
13:49 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 246 seconds]
13:55 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
13:56 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
14:51 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
14:54 -!- halosghost [~halosghos@user/halosghost] has quit [Quit: WeeChat 3.7.1]
14:57 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
14:58 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
15:00 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 252 seconds]
15:04 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
15:49 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
16:15 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 246 seconds]
16:18 -!- yanmaani2 [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Remote host closed the connection]
16:18 -!- yanmaani2 [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
16:21 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Remote host closed the connection]
16:21 -!- amovfx_ [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
16:21 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
16:23 -!- amovfx_ [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Remote host closed the connection]
16:23 -!- amovfx_ [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
16:35 -!- amovfx_ [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Remote host closed the connection]
16:36 -!- amovfx_ [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
16:40 -!- amovfx_ [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Ping timeout: 240 seconds]
16:52 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 276 seconds]
16:54 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
16:59 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 246 seconds]
17:05 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
17:09 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
17:11 < bitcoin-git> [bitcoin] achow101 opened pull request #26418: Fix signing of multi_a and rawtr scripts with wallets that only have corresponding keys (master...fix-psbt-multia) https://github.com/bitcoin/bitcoin/pull/26418
17:12 < bitcoin-git> [bitcoin] jamesob opened pull request #26419: log: mempool: log removal reason in validation interface (master...2022-10-log-mempool-removal-reason) https://github.com/bitcoin/bitcoin/pull/26419
17:18 < BlueMatt[m]> oookayyy, so my question yesterday was hitting on a not-quite-bug-but-definitely-usability-issue
17:20 < BlueMatt[m]> the issue was basically that some folks were running bitcoin core on regtest and calling `generatetoaddress`, some software was seeing the block, persisting its "latest chain tip", then the bitcoin node was crashing (even after an hour, but basically docker container shutdown was just kill'ing) and on restart the block was gone. the aforementioned software would then later load its "latest chain tip", not have any idea where that
17:20 < BlueMatt[m]> is on the chain and get very sad cause it couldnt ask for the block.
17:22 < BlueMatt[m]> so, kinda annoying that no flush happens if bitcoin core is idle for an hour, but ultimately the issue could also appear in prod if there's a reorg while a node that just crashed is offline
17:22 < BlueMatt[m]> at least on regtest
17:22 < BlueMatt[m]> doubly annoying cause on regtest you're not generating large blocks, so flushing is rare, afaiu?
17:46 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Remote host closed the connection]
17:46 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has joined #bitcoin-core-dev
17:47 -!- amovfx [~amovfx@node-1w7jr9yi65te42f98qsv2cp22.ipv6.telus.net] has quit [Remote host closed the connection]
18:10 -!- amovfx_ [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 252 seconds]
18:22 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
18:23 -!- mudsip [~mudsip@user/mudsip] has joined #bitcoin-core-dev
18:27 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 276 seconds]
18:30 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
18:31 < luke-jr> BlueMatt[m]: "don't do that"
18:33 < luke-jr> killing a program forcefully bypassing its shutdown sequence is not reasonable behaviour. of course the program should recover, but not necessarily in the most efficient manner
18:34 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 260 seconds]
18:34 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 255 seconds]
18:35 -!- mudsip [~mudsip@user/mudsip] has quit []
18:36 < BlueMatt[m]> apparently that's "Just How Docker Works", cant help that.
18:36 < BlueMatt[m]> also, machines lose power 🤷
18:45 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
18:56 < luke-jr> yes, but the current behaviour is acceptable for power loss type scenarios
18:57 < luke-jr> can perhaps improve it, but I'd consider it a feature, not a bugfix
18:57 < luke-jr> IIRC the reason we don't flush more, is that it also clears the cache
18:57 < luke-jr> I think there's a PR to change that though
19:00 < luke-jr> here it is, #17487
19:00 <@gribble> https://github.com/bitcoin/bitcoin/issues/17487 | coins: allow write to disk without cache drop by jamesob · Pull Request #17487 · bitcoin/bitcoin · GitHub
19:01 < luke-jr> looks fairly ready to merge, but considering a prior version had a consensus bug, it could benefit from additional review BlueMatt[m]
19:03 < BlueMatt[m]> sure, but if you're talking about regtest and its been an hour, it seems like flush should be done :)
19:03 < sipa> I had no idea anyone was even interested in having a regtest node run for more than a few minutes
19:03 < luke-jr> special-casing for regtest seems not useful
19:04 -!- zeropoint [~alex@c-67-169-157-130.hsd1.ca.comcast.net] has quit [Quit: leaving]
19:04 < sipa> Regtest or not could change some default timeout for flush configuration option, perhaps.
19:05 < luke-jr> could, but I don't think it's worth that
19:05 < luke-jr> especially with 17487 around the corner enabling a more aggressive flush without drop
19:05 < sipa> I don't think 17487 changes much.
19:06 < sipa> Flushing without dropping the cache is fairly terrible for performance.
19:06 < sipa> I can imagine there are special cases where that's useful, but it's not a good idea to use it for normal regular flushes
19:07 < sipa> Hmm, actually, that's not true.
19:07 < sipa> You can't use it for cache-size-limit-exceeded flushes, but you could use it for just regular time-based one if the cache isn't full.
19:13 -!- mikehu44 [~quassel@159.65.11.175] has joined #bitcoin-core-dev
19:15 < luke-jr> I would think it would be ideal to flush after each block, outside of IBD
19:16 < luke-jr> and keep the cache for processing subsequent blocks
19:16 < sipa> That may make sense, or every few blocks.
19:18 < sipa> The main benefit of not flushing (whether you drop the cache or not) is avoiding that UTXOs, created before the flush point but spent shortly after, hit disk at all.
19:18 < sipa> But outside of IBD that's not nearly as important.
19:20 < luke-jr> right, it could perhaps be configurable for situations where I/O is more precious
19:20 < luke-jr> but I think the norm is that outside IBD, it's no big deal
19:21 < sipa> well one downside is that flushing does need a somewhat extended lock on the cache data structures, and if a block arrives in that time, processing it will be delayed (perhaps just a few ms, but possibly more)
19:22 < sipa> i can imagine that some network users prefer not to risk that latency hit
19:22 < luke-jr> hmm
19:22 < luke-jr> can abort the transaction in that case?
19:23 < luke-jr> maybe not so simple, since that would require 2 passes over the dbcache
19:23 < luke-jr> (one to do the actual flush, and another to update the flags)
19:45 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 260 seconds]
19:51 -!- mekster669494 [~mekster@user/mekster] has joined #bitcoin-core-dev
20:00 -!- mikehu44 [~quassel@159.65.11.175] has quit [Ping timeout: 272 seconds]
20:01 -!- mikehu44 [~quassel@159.65.11.175] has joined #bitcoin-core-dev
20:03 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
20:05 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
20:48 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
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:02 -!- yanmaani2 [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Remote host closed the connection]
21:04 -!- yanmaani2 [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
21:38 -!- mekster669494 [~mekster@user/mekster] has quit [Ping timeout: 240 seconds]
21:53 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 276 seconds]
21:59 -!- cm_ [~chaz@user/cm] has joined #bitcoin-core-dev
22:00 -!- cm [~chaz@user/cm] has quit [Ping timeout: 260 seconds]
22:00 -!- cm_ is now known as cm
22:22 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
22:27 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 246 seconds]
22:50 -!- mikehu44 [~quassel@159.65.11.175] has quit [Ping timeout: 250 seconds]
22:57 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
23:01 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has quit [Ping timeout: 246 seconds]
23:31 -!- amovfx [~amovfx@node-1w7jr9yi65te4fuxljle3u02k.ipv6.telus.net] has joined #bitcoin-core-dev
--- Log closed Sat Oct 29 00:00:01 2022