From: "Ludovic Courtès" <ludo@gnu.org>
To: raingloom <raingloom@riseup.net>
Cc: 46168@debbugs.gnu.org
Subject: bug#46168: terminal-window-size breaks with ssh
Date: Tue, 09 Feb 2021 09:32:04 +0100 [thread overview]
Message-ID: <87v9b1vdyz.fsf@gnu.org> (raw)
In-Reply-To: <20210206014844.0f21d518@riseup.net> (raingloom@riseup.net's message of "Sat, 6 Feb 2021 01:48:44 +0100")
Hi,
raingloom <raingloom@riseup.net> skribis:
> On Thu, 04 Feb 2021 13:55:04 +0100
> Ludovic Courtès <ludo@gnu.org> wrote:
>
>> Hi,
>>
>> raingloom <raingloom@riseup.net> skribis:
>>
>> > Try running `ssh example.com guix pull` or something else that uses
>> > progress bars. You'll get an "Inappropriate ioctl for device"
>> > instead of Guix simply doing the sensible thing: disabling progress
>> > bars.
>>
>> I can’t reproduce this with c852d897551f514de95c224fa79e748f48808068.
>> Specifically, ‘ssh HOST guix pull’ shows me the Git progress bar
>> (while updating channels), and then there are no progress bars for
>> downloads but dots instead (as expected).
[...]
> Of course it does work now. :D
> Looking at `guix pull --list-generations`, the last two before the bug
> are:
> Generation 6 Dec 13 2020 01:47:37
> guix 1adeb74
> Generation 7 Jan 23 2021 16:47:02
> guix 0288e21
The problem you observed might have been fixed by
d613c1771a1986d3c0f1e034155fde41f32f9b8e (Dec. 17, 2020).
> ...aaaand I can't see later ones because guix just got killed. Maybe
> the code that computes the differences between generations is not
> terribly memory efficient...
I’m not aware of that. Could you please report a new bug if you have
more info?
Thanks,
Ludo’.
prev parent reply other threads:[~2021-02-09 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 22:09 bug#46168: terminal-window-size breaks with ssh raingloom
2021-02-04 12:55 ` Ludovic Courtès
2021-02-06 0:48 ` raingloom
2021-02-09 8:32 ` Ludovic Courtès [this message]
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=87v9b1vdyz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=46168@debbugs.gnu.org \
--cc=raingloom@riseup.net \
/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).