2025-08-06T00:07:48 acidsys: Aarrrghh gitlab.infra.o.o still never works properly because of the silly v4/v6 stuff. I have about a 1/3rd chance to get to it any day :( 2025-08-06T00:08:36 well as we already discussed there is no A record for gitlab.i.o.o, you are the only person having issues with something not having an A record 2025-08-06T00:10:34 Argh youre right what the fuck 2025-08-06T00:11:30 do other vpn-only websites work for you, like idm.i.o.o 2025-08-06T00:11:54 I'm restarting the vpn service now 2025-08-06T00:11:57 Today is a bad day :( 2025-08-06T00:12:09 it just started raining! 2025-08-06T00:12:20 Also the key format thing is already solved there is a release today 2025-08-06T00:12:43 neat) 2025-08-06T00:14:20 Did anything on the vpn change in the last 24 hours that you know of? 2025-08-06T00:15:27 automatic update of libsqlite3 which I assume is not relevant :P 2025-08-06T00:17:08 Yeah, probably not 2025-08-06T00:17:15 This is one of those days where everything is going wrong. 2025-08-06T01:28:46 acidsys: The log issue is fixed in 1.7.1 2025-08-06T01:30:38 oh cool so 1.7.0 is just an unlucky one 2025-08-06T01:30:49 Yeah 2025-08-06T01:30:55 There was an issue with the logging crate we used. 2025-08-06T01:31:38 I'm about to SR it now. 2025-08-06T01:31:45 I'm having to do a lot today, we have a P1 case too :( 2025-08-06T01:31:55 wondering about a joke about shipping logs in a crate 2025-08-06T01:31:59 no rush 2025-08-06T01:32:15 Hahaha 2025-08-06T01:33:41 There is now a feature in the crate that means that if there is a span (say client_request, the noisy one) it only prints if there are events associated to it. 2025-08-06T01:33:52 That way you won't get lets of single line noise, only events which have relevant data attached. 2025-08-06T01:34:21 ah that sounds useful 2025-08-06T10:04:37 *** teepee_ is now known as teepee 2025-08-06T21:12:38 *** teepee_ is now known as teepee