bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

Ludovic Courtès writes: > Janneke Nieuwenhuizen skribis: > >> Yeah, so I'm proposing the attached patch -- tested and works for me -- >> well, apart from having to set overload-threshold. I asked on #hurd and >> hopefully one of Damien's patch series >> >>

bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

Ludovic Courtès writes: > Janneke Nieuwenhuizen skribis: > >> Yeah, so I'm proposing the attached patch -- tested and works for me -- >> well, apart from having to set overload-threshold. I asked on #hurd and >> hopefully one of Damien's patch series >> >>

bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

Janneke Nieuwenhuizen skribis: > Yeah, so I'm proposing the attached patch -- tested and works for me -- > well, apart from having to set overload-threshold. I asked on #hurd and > hopefully one of Damien's patch series > > >

bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

Ludovic Courtès writes: Hey Ludo, > > Janneke Nieuwenhuizen skribis: > >> So, the problem is that our patch doesrn't disable the warnings after all. >> The guile-launcher has >> >> guile-launcher.c: >> >> #if defined __GNU__ >> /* XXX: On 32-bit GNU/Hurd (i586-gnu), libgc emits "Repeated alloca

bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

Hi Janneke, Janneke Nieuwenhuizen skribis: > So, the problem is that our patch doesrn't disable the warnings after all. > The guile-launcher has > > guile-launcher.c: > > #if defined __GNU__ > /* XXX: On 32-bit GNU/Hurd (i586-gnu), libgc emits "Repeated allocation" > warnings that are ann

bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

Ludovic Courtès writes: Hello! > skribis: > >> Anyway, using this patch 0001 it seems that suppressing the warnings >> works, I no longer get >> >> "GC Warning: Repeated allocation of very large block (appr. size 112 >> KiB):\n\tMay lead to memory leak and poor performance\n" >> >> >> but still

bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

Ludovic Courtès writes: Hello, > skribis: > >> Anyway, using this patch 0001 it seems that suppressing the warnings >> works, I no longer get >> >> "GC Warning: Repeated allocation of very large block (appr. size 112 >> KiB):\n\tMay lead to memory leak and poor performance\n" >> >> >> but still

bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

Ludovic Courtès writes: Hi, > skribis: > Anyway, using this patch 0001 it seems that suppressing the warnings works, I no longer get "GC Warning: Repeated allocation of very large block (appr. size 112 KiB):\n\tMay lead to memory leak and poor performance\n" >>

bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

Hello, skribis: >>> Anyway, using this patch 0001 it seems that suppressing the warnings >>> works, I no longer get >>> >>> "GC Warning: Repeated allocation of very large block (appr. size 112 >>> KiB):\n\tMay lead to memory leak and poor performance\n" >>> >>> >>> but still get >>> >>> unexpect

bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

Ludovic Courtès writes: Hi! > skribis: > >> Anyway, using this patch 0001 it seems that suppressing the warnings >> works, I no longer get >> >> "GC Warning: Repeated allocation of very large block (appr. size 112 >> KiB):\n\tMay lead to memory leak and poor performance\n" >> >> >> but still get

bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

Hello! skribis: > Anyway, using this patch 0001 it seems that suppressing the warnings > works, I no longer get > > "GC Warning: Repeated allocation of very large block (appr. size 112 > KiB):\n\tMay lead to memory leak and poor performance\n" > > > but still get > > unexpected build daemon err

bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

Ludovic Courtès writes: Hello, > skribis: > >> Ludovic Courtès writes: [..] >>> I see several possible things to do: >>> >>> 1. Disable GC warnings altogether in Guix by setting ‘GC_warn_proc’. >>> >>> 2. Make sure guix-daemon discards stderr from agents such as ‘guix >>> authenticate

bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

Hello, skribis: > Ludovic Courtès writes: [...] >> That warning comes from libgc and there’s no such warning when LC_ALL is >> left unset, which is why it works in that case. > > How about > >0. Unsetting LC_ALL on the Hurd > > would that work? I’m not sure, but if it does, it’s only “by

bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

Ludovic Courtès writes: Hi! > Ludovic Courtès skribis: > >> Inside the childhurd, we get: >> >> root@childhurd ~# tail -1 /var/log/guix-daemon.log >> 2024-09-09 21:09:03 unexpected build daemon error: stoi >> >> Last time we got that error was in commit >> 21deb89e287b5821975544118bf137562a91d4

bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

Ludovic Courtès skribis: > Inside the childhurd, we get: > > root@childhurd ~# tail -1 /var/log/guix-daemon.log > 2024-09-09 21:09:03 unexpected build daemon error: stoi > > Last time we got that error was in commit > 21deb89e287b5821975544118bf137562a91d4e1: guix-daemon was running with > incor

bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

As reported by yelninei on IRC, Guix on the Hurd is in half-broken state following the recent ‘core-updates’ merge. Specifically, sending store items over SSH (and thus breaks offloading too): --8<---cut here---start->8--- $ guix copy --to=localhost:10022 iduti