GNU bug report logs - #35379
Long lines in `guix` output are truncated at screen width

Previous Next

To reply to this bug, email your comments to 35379 AT debbugs.gnu.org.

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

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

From: rendaw <7e9wc56emjakcm <at> s.rendaw.me>
To: submit <at> debbugs.gnu.org
Subject: Long lines in `guix` output are truncated at screen width
Date: Tue, 23 Apr 2019 00:55:57 +0900

I get logs like:

/gnu/store/6zkimxsfyn0gdc7p4ikxlrhilpnpblsi-grub-efi-2.02/sbin/grub-install:
error:
/gnu/store/6zkimxsfyn0gdc7p4ikxlrhilpnpblsi-grub-efi-2.02/lib/grub/i386-pc/modinfo.sh
doesn't exist. Please spe.

cut off neatly with a period at the edge of the console.  I'm not sure I
lost important information here, but I have in other places (ex: using
`display` to show a value).

Via a suggestion from nckx I exported `COLUMNS=`, but this gets reset at
some point during the build - I think qemu or something resets the
terminal state (very vague speculation here).

IMO long lines should only be truncated if explicitly requested - it's
easy to truncate at the CLI but impossible to restore data lost via
truncation after all.

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

From: rendaw <7e9wc56emjakcm <at> s.rendaw.me>
To: 35379 <at> debbugs.gnu.org
Subject: Re: bug#35379: Acknowledgement (Long lines in `guix` output are
 truncated at screen width)
Date: Tue, 23 Apr 2019 01:07:17 +0900

Package: guix

Version: 0.16.0

On 4/23/19 12:57 AM, GNU bug Tracking System wrote:
> Thank you for filing a new bug report with debbugs.gnu.org.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  help-debbugs <at> gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 35379 <at> debbugs.gnu.org.
>
> Please do not send mail to help-debbugs <at> gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: rendaw <7e9wc56emjakcm <at> s.rendaw.me>
Cc: 35379 <at> debbugs.gnu.org
Subject: Re: bug#35379: Long lines in `guix` output are truncated at screen
 width
Date: Tue, 23 Apr 2019 15:13:39 +0200

Hi rendaw,

rendaw <7e9wc56emjakcm <at> s.rendaw.me> skribis:

> I get logs like:
>
> /gnu/store/6zkimxsfyn0gdc7p4ikxlrhilpnpblsi-grub-efi-2.02/sbin/grub-install:
> error:
> /gnu/store/6zkimxsfyn0gdc7p4ikxlrhilpnpblsi-grub-efi-2.02/lib/grub/i386-pc/modinfo.sh
> doesn't exist. Please spe.

Hmm weird.  Can you tell exactly how to reproduce this issue?
I don’t see what could be truncating these lines.

Thanks in advance,
Ludo’.

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

From: rendaw <7e9wc56emjakcm <at> s.rendaw.me>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 35379 <at> debbugs.gnu.org
Subject: Re: bug#35379: Long lines in `guix` output are truncated at screen
 width
Date: Wed, 24 Apr 2019 03:30:17 +0900

On 4/23/19 10:13 PM, Ludovic Courtès wrote:
> Hi rendaw,
>
> rendaw <7e9wc56emjakcm <at> s.rendaw.me> skribis:
>
>> I get logs like:
>>
>> /gnu/store/6zkimxsfyn0gdc7p4ikxlrhilpnpblsi-grub-efi-2.02/sbin/grub-install:
>> error:
>> /gnu/store/6zkimxsfyn0gdc7p4ikxlrhilpnpblsi-grub-efi-2.02/lib/grub/i386-pc/modinfo.sh
>> doesn't exist. Please spe.
> Hmm weird.  Can you tell exactly how to reproduce this issue?
> I don’t see what could be truncating these lines.
>
> Thanks in advance,
> Ludo’.

I thought this was normal, but I tried reproducing it in a vm.

It appears that the truncation starts after qemu starts the image in

```

guix system disk-image my-config.scm -v 10

```

and the truncation continues thereafter.  I tested by doing:

```

(display (iota 200))

(display "\n")

(force-output)

(display (iota 200))

```

This prints before and after the qemu step of the build.  Before the
qemu process it looks like lines are wrapped properly.  After the qemu
process the lines are truncated.  And lines are truncated before+after
for subsequent builds until I reset the vm.

I can send the Vagrantfile and provisioning script + what I did manually
to do the build if you'd like.

The main issue is the build fails, I turn -v 10 on to see the verbose
logs, but then the logs I need (during/post qemu) are truncated so I'm
still not getting the important information.

Previous Next

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