From: "Ludovic Courtès" <ludo@gnu.org>
To: Vladilen Kozin <vladilen.kozin@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: guix system container and friends fail to report intermediate errors
Date: Mon, 17 Apr 2023 18:07:26 +0200 [thread overview]
Message-ID: <87sfcycx1d.fsf@gnu.org> (raw)
In-Reply-To: <CACw=CXPG53DDq=Ew0apYBCYtunyK=ys8eSf3Wgu6usXmXHsNeg@mail.gmail.com> (Vladilen Kozin's message of "Mon, 27 Mar 2023 14:52:26 +0100")
Hi!
Vladilen Kozin <vladilen.kozin@gmail.com> skribis:
> Hello. Is it possible to get better error reporting in the following
> example?
>
> $ sudo guix system -K -L /home/vlad/Code/fullmeta-guix/channel container
> os.scm
>
> And our os.scm imports some services defined in our channel above. Should
> there be an error in one of them, however, the stack trace only talks about
> inability to find that service symbol but otherwise fails to report any
> errors that may've happened when loading modules from our -L location above.
>
> Case in point. In one of the modules, I habitually used Clojury syntax and
> wrote:
>
> (define foo [1 2])
>
> (define foo-service
> (list
> (shepherd-service ... #$foo ...)))
>
> (define foo-service-type ...)
>
> Running the above OS derivation reports:
> ```
> Backtrace:
> In guix/store.scm:
> ... bt here ...
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> error: foo-service-type: unbound variable
> ```
If I understand correctly what’s happening, the module file that defines
‘foo’ and ‘foo-service’ fails to load with a “Wrong type to apply”
error. Consequently, you end up with that “unbound variable” error in
your OS file. Do I get it right?
Thanks,
Ludo’.
prev parent reply other threads:[~2023-04-17 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 13:52 guix system container and friends fail to report intermediate errors Vladilen Kozin
2023-03-27 18:10 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-04-17 16:07 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfcycx1d.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=vladilen.kozin@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.