From: Maxime Devos <maximedevos@telenet.be>
To: Thiago Jung Bauermann <bauermann@kolabnow.com>, 56005@debbugs.gnu.org
Cc: control@debbugs.gnu.org
Subject: bug#56005: "write_wait_fd: unimplemented" during downloading substitutes
Date: Thu, 16 Jun 2022 09:58:24 +0200 [thread overview]
Message-ID: <31d325076ae0c552cc04a010956faed27dc35d2c.camel@telenet.be> (raw)
In-Reply-To: <87o7yt71sc.fsf@kolabnow.com>
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
retitle 56006 "write_wait_fd: unimplemented" during downloading substitutes
thanks
Thiago Jung Bauermann via Bug reports for GNU Guix schreef op wo 15-06-
2022 om 23:40 [-0300]:
> I had a quick look at ‘fetch-narinfos’ but I couldn't figure out what
> could be calling into this unimplemented function ‘write_wait_fd’…
Untested hypothesis: maybe writing to the TLS-wrapped port constructed
in (guix build download) blocked, so Guile's port code ran
'write_wait_fd', which was not set for the TLS port (in the GnuTLS
library)? Alternatively: maybe 'make-custom-binary-input/output-port'
in (guix build download) was used incorrectly?
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-16 7:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 2:40 bug#56005: exception while downloading substitutes Thiago Jung Bauermann via Bug reports for GNU Guix
2022-06-16 7:58 ` Maxime Devos [this message]
2022-06-30 11:48 ` bug#56005: In procedure write_wait_fd: unimplemented Attila Lendvai
2022-06-30 11:51 ` bug#56005: during substitution: " Maxime Devos
2022-06-30 11:55 ` Maxime Devos
2022-06-30 11:56 ` Maxime Devos
2022-07-16 3:34 ` Thiago Jung Bauermann via Bug reports for GNU Guix
2022-07-19 19:50 ` Maxime Devos
2023-04-23 22:27 ` bug#56005: Nathan Dehnel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=31d325076ae0c552cc04a010956faed27dc35d2c.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=56005@debbugs.gnu.org \
--cc=bauermann@kolabnow.com \
--cc=control@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).