GNU bug report logs - #46168
terminal-window-size breaks with ssh

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 46168 in the body.
You can then email your comments to 46168 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: raingloom <raingloom <at> riseup.net>
To: Guix Bugs <bug-guix <at> gnu.org>
Subject: terminal-window-size breaks with ssh
Date: Wed, 27 Jan 2021 23:09:34 +0100

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.

Message #10 received at 46168 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: raingloom <raingloom <at> riseup.net>
Cc: 46168 <at> debbugs.gnu.org
Subject: Re: bug#46168: terminal-window-size breaks with ssh
Date: Thu, 04 Feb 2021 13:55:04 +0100

Hi,

raingloom <raingloom <at> 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).

Which revision (as returned by ‘guix describe’) behaves like this for
you?

Thanks,
Ludo’.

Message #13 received at 46168 <at> debbugs.gnu.org (full text, mbox):

From: raingloom <raingloom <at> riseup.net>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 46168 <at> debbugs.gnu.org
Subject: Re: bug#46168: terminal-window-size breaks with ssh
Date: Sat, 6 Feb 2021 01:48:44 +0100

On Thu, 04 Feb 2021 13:55:04 +0100
Ludovic Courtès <ludo <at> gnu.org> wrote:

> Hi,
> 
> raingloom <raingloom <at> 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).
> 
> Which revision (as returned by ‘guix describe’) behaves like this for
> you?
> 
> Thanks,
> Ludo’.

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


...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...

Message #16 received at 46168 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: raingloom <raingloom <at> riseup.net>
Cc: 46168 <at> debbugs.gnu.org
Subject: Re: bug#46168: terminal-window-size breaks with ssh
Date: Tue, 09 Feb 2021 09:32:04 +0100

Hi,

raingloom <raingloom <at> riseup.net> skribis:

> On Thu, 04 Feb 2021 13:55:04 +0100
> Ludovic Courtès <ludo <at> gnu.org> wrote:
>
>> Hi,
>> 
>> raingloom <raingloom <at> 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’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.