19:15:04 <selsta> sech1: any idea? https://github.com/monero-project/monero-gui/issues/4239
19:17:54 <sech1> I think I saw it before: https://www.reddit.com/r/MoneroMining/comments/17lkpj0/problems_with_solo_mining/
19:17:58 <sech1> no idea why it's happening
19:21:17 <sech1> Maybe it's even the same person
19:22:28 <sech1> And it crashes in the very weird spot
19:23:48 <sech1> I mean, it added peers from the first domain, but it didn't even print that it started adding peers from the second domain
19:26:22 <sech1> https://paste.debian.net/hidden/a464c6cb/
19:26:46 <sech1> there's not even a 0.0001 second between the last line of their log and what should've been next in the log
19:32:50 <sech1> Maybe it's Windows 11 specific issue. But I have p2pool sync tests that run on Windows Server 2022 in Github CI and those pass. Windows Server 2022 = kind of a server version of Windows 11
19:36:42 <selsta> ok ty, let's see if they reply
19:36:56 <selsta> first issue about this so far on the GUI repo
20:03:13 <sech1> It's not the same person - they have different number of CPU threads. So it's two different instances of this bug so far.
22:40:15 <paulio_uk> just a shot in the dark, its not something to do with ipv6 being in the node list is it?