Long lines in `guix` output are truncated at screen width

  • Open
  • quality assurance status badge
Details
3 participants
  • rendaw
  • Ludovic Courtès
  • Glenn Morris
Owner
unassigned
Submitted by
rendaw
Severity
normal
R
R
rendaw wrote on 22 Apr 2019 17:55
(address . submit@debbugs.gnu.org)
42f3ade8-5d7c-9f9d-6d8d-886734b1ffa2@s.rendaw.me
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.
R
R
rendaw wrote on 22 Apr 2019 18:07
Re: bug#35379: Acknowledgement (Long lines in `guix` output are truncated at screen width)
(address . 35379@debbugs.gnu.org)
cac6a272-3ac9-09c3-e7de-c5f41c870da5@s.rendaw.me
Package: guix

Version: 0.16.0

On 4/23/19 12:57 AM, GNU bug Tracking System wrote:
Toggle quote (17 lines)
> 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@gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 35379@debbugs.gnu.org.
>
> Please do not send mail to help-debbugs@gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>
G
G
Glenn Morris wrote on 22 Apr 2019 18:41
control message for bug 35379
(address . control@debbugs.gnu.org)
E1hIc0T-0002z1-UQ@fencepost.gnu.org
reassign 35379 guix
L
L
Ludovic Courtès wrote on 23 Apr 2019 15:13
Re: bug#35379: Long lines in `guix` output are truncated at screen width
(name . rendaw)(address . 7e9wc56emjakcm@s.rendaw.me)(address . 35379@debbugs.gnu.org)
87ftq8j24c.fsf@gnu.org
Hi rendaw,

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

Toggle quote (7 lines)
> 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’.
R
R
rendaw wrote on 23 Apr 2019 20:30
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 35379@debbugs.gnu.org)
c84ac514-ba59-fb0c-bc1d-e3fa6e080861@s.rendaw.me
On 4/23/19 10:13 PM, Ludovic Courtès wrote:
Toggle quote (16 lines)
> Hi rendaw,
>
> rendaw <7e9wc56emjakcm@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.
?