From: Csepp <raingloom@riseup.net>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: guix-devel@gnu.org
Subject: Re: Understanding a Golang importer error
Date: Mon, 22 May 2023 08:38:58 +0200 [thread overview]
Message-ID: <878rdgsw94.fsf@riseup.net> (raw)
In-Reply-To: <CAFHYt57gGOJHD1ySpoDg0bf8r4OhRTjo=8Z7+Xz2_qvOFX-VnA@mail.gmail.com>
Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org> writes:
> Hi,
>
> The command
>
> guix import go -r github.com/google/certificate-transparency-go
>
> produces the output below. Which repo is missing the v0.41.1 tag,
> please? Thanks!
>
> Kind regards
> Felix
>
> * * *
>
> Backtrace:
> In srfi/srfi-1.scm:
> 586:29 19 (map1 _)
> 586:29 18 (map1 _)
> 586:29 17 (map1 _)
> 586:29 16 (map1 _)
> 586:29 15 (map1 _)
> 586:29 14 (map1 _)
> 586:17 13 (map1 (("go.opentelemetry.io/contrib/instrumentat…" …) …))
> In guix/import/utils.scm:
> 630:33 12 (lookup-node "go.opentelemetry.io/contrib/instrumentat…" …)
> In guix/memoization.scm:
> 98:0 11 (mproc "go.opentelemetry.io/contrib/instrumentation/go…" …)
> In unknown file:
> 10 (_ #<procedure 7f95afe55540 at guix/memoization.scm:17…> …)
> In guix/import/go.scm:
> 685:10 9 (_ _ #:version _ #:repo _)
> In ice-9/exceptions.scm:
> 406:15 8 (go-module->guix-package* . _)
> In ice-9/boot-9.scm:
> 1752:10 7 (with-exception-handler _ _ #:unwind? _ # _)
> In guix/import/go.scm:
> 511:19 6 (go-module->guix-package "go.opentelemetry.io/contrib/…" …)
> In guix/git.scm:
> 291:4 5 (update-cached-checkout _ #:ref _ #:recursive? _ # _ # _ …)
> 277:19 4 (resolve _)
> In git/reference.scm:
> 60:8 3 (_ _ _)
> In git/bindings.scm:
> 77:2 2 (raise-git-error _)
> In ice-9/boot-9.scm:
> 1685:16 1 (raise-exception _ #:continuable? _)
> 1683:16 0 (raise-exception _ #:continuable? _)
>
> ice-9/boot-9.scm:1683:16: In procedure raise-exception:
> Git error: reference 'refs/tags/v0.41.1' not found
Try re-running the commands with COLUMNS=0, I thiiink that's the magic
incantation to un-break the logs.
And for the record this is why I think truncating lines in Guile traces
is a very terrible idea. It usually hides a lot of important info and
makes it necessary to re-run expensive computations for no reason.
next prev parent reply other threads:[~2023-05-22 6:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 3:13 Understanding a Golang importer error Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-22 6:38 ` Csepp [this message]
2023-05-22 14:44 ` Attila Lendvai
2023-05-22 16:27 ` Simon Tournier
2023-05-25 2:29 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-25 14:09 ` Simon Tournier
2023-05-25 16:02 ` Simon Tournier
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=878rdgsw94.fsf@riseup.net \
--to=raingloom@riseup.net \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
/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).