From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Artyom Poptsov <poptsov.artyom@gmail.com>, 42740@debbugs.gnu.org
Subject: bug#42740: Segfault in libssh during ‘guix copy’
Date: Tue, 15 Sep 2020 09:48:28 -0400 [thread overview]
Message-ID: <87h7rz1783.fsf@gmail.com> (raw)
In-Reply-To: <87tuvz8ni8.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 15 Sep 2020 10:14:55 +0200")
Hi Ludovic,
Ludovic Courtès <ludo@gnu.org> writes:
> Hi Maxim,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>
>> What is the manifestation of the current guile-ssh remaining problems?
>
> To me, the Guile-SSH problems were successfully worked around on our
> side with 61fe9ced7da7eefceb931af0cb7363b721f5bdd6. It could be that
> you found an issue we didn’t address.
>
>> Is it like the error message below?
>>
>> guix offload: error: corrupt input while restoring archive from #<input: string 7ff371d9e7e0>
>>
>> I just had this today during guix offload.
>
> Hmm. Is it reproducible? Can you show the 10-or-so lines above, to see
> if the build completed, whether the error happened while sending build
> results, etc.?
Sorry for the noise, I cannot reproduce after restarting guix-daemon. I
guess I just hadn't restarted it in a long time (the recent testing I
did for the fix was with a locally started daemon in my guix checkout).
Thank you,
Maxim
next prev parent reply other threads:[~2020-09-15 13:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 9:24 bug#42740: Segfault in libssh during ‘guix copy’ Ludovic Courtès
2020-08-07 18:36 ` Artyom V. Poptsov
2020-08-09 8:48 ` Artyom Poptsov
2020-08-17 3:31 ` Maxim Cournoyer
2020-08-23 16:31 ` Ludovic Courtès
2020-09-15 2:05 ` Maxim Cournoyer
2020-09-15 8:14 ` Ludovic Courtès
2020-09-15 13:48 ` Maxim Cournoyer [this message]
2020-08-29 13:31 ` Ludovic Courtès
2020-08-29 14:31 ` Ludovic Courtès
2020-09-01 13:56 ` Maxim Cournoyer
2020-09-01 20:57 ` Ludovic Courtès
2020-09-02 21:19 ` Ludovic Courtès
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=87h7rz1783.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=42740@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=poptsov.artyom@gmail.com \
/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).