From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>, clement@lassieur.org
Cc: 33030@debbugs.gnu.org
Subject: bug#33030: Crash in progress-bar
Date: Fri, 16 Nov 2018 19:04:12 +0100 [thread overview]
Message-ID: <87sh00vqzn.fsf@gnu.org> (raw)
In-Reply-To: <87r2frwcyr.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 11 Nov 2018 21:55:56 +0100")
Hello,
Ricardo Wurmus <rekado@elephly.net> skribis:
> I’ve just got the very same error:
>
> downloading from https://berlin.guixsd.org/nar/gzip/iql35g1g5q9dkap5splc7f9ggskr31vl-NamesList.txt...
> Backtrace:
> In guix/scripts/package.scm:
> 913:10 19 (_)
> In guix/status.scm:
> 600:4 18 (call-with-status-report _ _)
> In guix/scripts/package.scm:
> 921:14 17 (_)
> 873:19 16 (process-actions #<build-daemon 256.98 1b9ff50> _)
> 598:4 15 (options->installable ((upgrade . #f) (verbosity . 0) (graft? . #t) (substitutes? . #t) (# . #t) # # …) …)
> In srfi/srfi-1.scm:
> 501:18 14 (fold-right #<procedure 1b98700 at guix/scripts/package.scm:598:16 (entry transaction)> _ _ . _)
> In guix/scripts/package.scm:
> 238:37 13 (transaction-upgrade-entry _ #<<manifest-transaction> install: (#<<manifest-entry> name: "qtractor" ve…>)
> In guix/packages.scm:
> 881:14 12 (cache! #<weak-table 970/1759> #<package alsa-plugins@1.1.6 gnu/packages/linux.scm:1060 2d9c300> (. #) _)
> In unknown file:
> 11 (_ #<procedure thunk ()> #<procedure list _> #<undefined>)
> In guix/grafts.scm:
> 303:4 10 (graft-derivation #<build-daemon 256.98 1b9ff50> #<derivation /gnu/store/cy3q34absx81bfygp33ji4nxi7m1…> …)
> 181:4 9 (references-oracle #<build-daemon 256.98 1b9ff50> #<derivation /gnu/store/cy3q34absx81bfygp33ji4nxi7m1…>)
> 190:20 8 (_ _ _)
> In guix/store.scm:
> 1100:15 7 (_ #<build-daemon 256.98 1b9ff50> _ _)
> 661:13 6 (process-stderr _ _)
> In unknown file:
> 5 (display "@ download-progress /gnu/store/iql35g1g5q9dkap5splc7f9ggskr31vl-NamesList.txt https://berli…" …)
> In guix/status.scm:
> 521:16 4 (write! _ _ _)
> 439:6 3 (_ (download-progress "/gnu/store/iql35g1g5q9dkap5splc7f9ggskr31vl-NamesList.txt" "https://berlin.…" …) …)
> In guix/progress.scm:
> 208:33 2 (display-download-progress _ _ #:start-time _ #:transferred _ #:log-port _)
> 183:12 1 (progress-bar _ _)
> In unknown file:
> 0 (make-string -51 #\space)
>
> ERROR: In procedure make-string:
> Value out of range 0 to 18446744073709551615: -51
Clément just pushed a couple of fixes in this area. Clément, is this
what you fixed?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-11-16 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 2:53 bug#33030: Crash in progress-bar Leo Famulari
2018-10-13 22:39 ` Mark H Weaver
2018-10-15 9:20 ` Ludovic Courtès
2018-10-16 4:57 ` Leo Famulari
2018-10-16 11:32 ` Ludovic Courtès
2018-11-11 20:55 ` Ricardo Wurmus
2018-11-16 18:04 ` Ludovic Courtès [this message]
2018-11-19 9:48 ` Clément Lassieur
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=87sh00vqzn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33030@debbugs.gnu.org \
--cc=clement@lassieur.org \
--cc=rekado@elephly.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).