unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 33968-done@debbugs.gnu.org
Subject: bug#33968: errors in shepherd service constructors are not logged and lead to misleading status
Date: Thu, 15 Jun 2023 23:15:29 +0200	[thread overview]
Message-ID: <87y1kktojy.fsf@gnu.org> (raw)
In-Reply-To: <7c7f7030-a0f2-5fd0-7d02-f203277d7bba@gmail.com> (Florian Dold's message of "Thu, 3 Jan 2019 22:36:20 +0100")

Florian Dold <florian.dold@gmail.com> skribis:

> when defining a service type that extends shepherd-root-service-type and
> the 'start' function of the shepherd-service definition contains an
> error, the error is silently ignored.  No log output is generated at all.

[...]

> I generally feel like the state machine for services needs some work.
> In particular, it would be useful to distinguish between "failed" and
> "completed" services instead of conflating both states into "stopped".
> Or maybe have some more general mechanism for storing state about the
> service, instead of just the slot that usually contains the PID?

It’s been 4 years (!) but the good news is that all this is fixed as of
Shepherd 0.10.  Closing!

Ludo’.




      parent reply	other threads:[~2023-06-15 21:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 21:36 bug#33968: errors in shepherd service constructors are not logged and lead to misleading status Florian Dold
2021-05-20  3:00 ` bug#33968: errors in shepherd service constructors are not logged and lead to misleading status, hang boot Maxim Cournoyer
2023-06-15 21:15 ` 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

  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=87y1kktojy.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=33968-done@debbugs.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).