bug#76589: [PATCH] Exclude the finalizer thread from the ‘all-threads’ result.

I think that this change is fine, but it could be better when it comes to testing for multi-threaded environment. First, a Guile internal thread is leaked in the list of threads, which users are not expecting. Perhaps there's code out there that is handling this fine but would break by removing

bug#76589: [PATCH] Exclude the finalizer thread from the ‘all-threads’ result.

Fixes . Fixes a bug whereby “echo '(environ)' | guile” would wrongfully trigger the multiple-thread warning. * libguile/finalizers.c (finalizer_thread): New variable. (finalization_thread_proc): Set it. (scm_i_is_finalizer_thread): New function. (run_finalization_threa

bug#70645: Reliable HTTPS networking

Christopher Baines skribis: > As described in the GnuTLS documentation on Asynchronous operation, > GNUTLS_NONBLOCK should be passed to gnutls_init, and the Guile > equivalent is passing connection-flag/nonblock to make-session. > > Additionally, error/again or error/interrupted should lead to a

bug#75997: (ice-9 match): warning: unused variable `failure'

Tomas Volf <~@wolfsden.cz> skribis: > (lambda (expr) > (let* ((v expr) > (failure >(lambda () > ((@@ (ice-9 match) throw) > 'match-error > "match" > "no matching pattern" > v) > #f))) > #f)

bug#69998: [PATCH guile-web] libraries: Use guile-gnunet’s real name.

Hi, Florian Pelz skribis: > * website/apps/base/libraries-page.scm (guix->package)[real-name]: > Add special case. Finally applied. It won’t show up until someone redeploys the web site though… Ludo’.