GNU bug report logs -
#55857
Odd Shepherd message on 'guix system reconfigure': (map (# ?) ?)
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 55857 in the body.
You can then email your comments to 55857 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#55857
; Package
guix
.
(Wed, 08 Jun 2022 18:58:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Wed, 08 Jun 2022 18:58:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hello Guix,
The following message is shown when reconfiguring Guix System:
--8<---------------cut here---------------start------------->8---
shepherd: Evaluating user expression (and (defined? (quote transient?)) (map (# ?) ?)).
--8<---------------cut here---------------end--------------->8---
It doesn't seem intended for end users to see; at least I have no clue
what it's supposed to tell me :-).
Thanks,
Maxim
Information forwarded
to
bug-guix <at> gnu.org
:
bug#55857
; Package
guix
.
(Fri, 10 Jun 2022 21:57:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 55857 <at> debbugs.gnu.org (full text, mbox):
Hi,
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:
> The following message is shown when reconfiguring Guix System:
>
> shepherd: Evaluating user expression (and (defined? (quote transient?)) (map (# ?) ?)).
>
> It doesn't seem intended for end users to see; at least I have no clue
> what it's supposed to tell me :-).
The question marks are HORIZONTAL ELLIPSIS not being displayed properly
because ‘guix’ is not running under a UTF-8 locale.
The message is produced by shepherd as a response to an expression that
‘guix system reconfigure’ tells it to evaluate, in (gnu services herd).
And all this happens as part of the live service upgrade mechanism.
Admittedly, this particular message is not something one cares about as
a user, but it seemed safer to print messages shepherd might send during
that operation.
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#55857
; Package
guix
.
(Tue, 14 Jun 2022 16:23:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 55857 <at> debbugs.gnu.org (full text, mbox):
Hi Ludovic,
Ludovic Courtès <ludo <at> gnu.org> writes:
> Hi,
>
> Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:
>
>> The following message is shown when reconfiguring Guix System:
>>
>> shepherd: Evaluating user expression (and (defined? (quote transient?)) (map (# ?) ?)).
>>
>> It doesn't seem intended for end users to see; at least I have no clue
>> what it's supposed to tell me :-).
>
> The question marks are HORIZONTAL ELLIPSIS not being displayed properly
> because ‘guix’ is not running under a UTF-8 locale.
>
> The message is produced by shepherd as a response to an expression that
> ‘guix system reconfigure’ tells it to evaluate, in (gnu services herd).
> And all this happens as part of the live service upgrade mechanism.
>
> Admittedly, this particular message is not something one cares about as
> a user, but it seemed safer to print messages shepherd might send during
> that operation.
Perhaps what we need is a proper logging infrastructure? The above
message could be flagged as a 'debug' level message. stdout/stderr
would only get to see the 'info' or higher level messages, the rest
would be logged only to syslog, keeping the user interface clean. I
know such a logging mechanism exists in Guile-Lib, as the (logging
logger) module [0].
What do you think?
Thanks,
Maxim
[0] https://www.nongnu.org/guile-lib/doc/ref/logging.logger/
Information forwarded
to
bug-guix <at> gnu.org
:
bug#55857
; Package
guix
.
(Tue, 14 Jun 2022 16:51:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 55857 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Maxim Cournoyer schreef op di 14-06-2022 om 12:22 [-0400]:
> Perhaps what we need is a proper logging infrastructure? The above
> message could be flagged as a 'debug' level message. stdout/stderr
> would only get to see the 'info' or higher level messages, the rest
> would be logged only to syslog, keeping the user interface clean. I
> know such a logging mechanism exists in Guile-Lib, as the (logging
> logger) module [0].
>
> What do you think?
Attila Lendvai has some ideas on logging, see
https://issues.guix.gnu.org/55242#2 and later patches.
Greetings,
Maxime.
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#55857
; Package
guix
.
(Wed, 15 Jun 2022 09:55:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 55857 <at> debbugs.gnu.org (full text, mbox):
Hi,
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:
> Ludovic Courtès <ludo <at> gnu.org> writes:
[...]
>> The message is produced by shepherd as a response to an expression that
>> ‘guix system reconfigure’ tells it to evaluate, in (gnu services herd).
>> And all this happens as part of the live service upgrade mechanism.
>>
>> Admittedly, this particular message is not something one cares about as
>> a user, but it seemed safer to print messages shepherd might send during
>> that operation.
>
> Perhaps what we need is a proper logging infrastructure?
The difficulty here is that the message comes from shepherd without a
priority/level flag. Usually those messages are well worth displaying
because they show what services got restarted, what failed, etc. But
this one message is the fly in the ointment…
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#55857
; Package
guix
.
(Wed, 15 Jun 2022 15:52:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 55857 <at> debbugs.gnu.org (full text, mbox):
Hello,
Ludovic Courtès <ludo <at> gnu.org> writes:
> Hi,
>
> Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:
>
>> Ludovic Courtès <ludo <at> gnu.org> writes:
>
> [...]
>
>>> The message is produced by shepherd as a response to an expression that
>>> ‘guix system reconfigure’ tells it to evaluate, in (gnu services herd).
>>> And all this happens as part of the live service upgrade mechanism.
>>>
>>> Admittedly, this particular message is not something one cares about as
>>> a user, but it seemed safer to print messages shepherd might send during
>>> that operation.
>>
>> Perhaps what we need is a proper logging infrastructure?
>
> The difficulty here is that the message comes from shepherd without a
> priority/level flag. Usually those messages are well worth displaying
> because they show what services got restarted, what failed, etc. But
> this one message is the fly in the ointment…
Yes, I wasn't clear but I meant *Shepherd* needs a proper logging
infrastructure (although it seems to me the logging library in Guile-Lib
could be used in any Guile project, Guix included -- the way the
'logging' module comes standard in Python and preferred to printing or
reinventing a logging system :-)).
Maxim
Information forwarded
to
bug-guix <at> gnu.org
:
bug#55857
; Package
guix
.
(Thu, 16 Jun 2022 10:44:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 55857 <at> debbugs.gnu.org (full text, mbox):
Hi,
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:
> Ludovic Courtès <ludo <at> gnu.org> writes:
[...]
>> The difficulty here is that the message comes from shepherd without a
>> priority/level flag. Usually those messages are well worth displaying
>> because they show what services got restarted, what failed, etc. But
>> this one message is the fly in the ointment…
>
> Yes, I wasn't clear but I meant *Shepherd* needs a proper logging
> infrastructure
Ah well, it has syslog! Syslog defines priorities and sources; we
should take advantage of that.
Ludo’.
Added tag(s) notabug.
Request was from
Ludovic Courtès <ludo <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Thu, 27 Apr 2023 13:31:02 GMT)
Full text and
rfc822 format available.
bug closed, send any further explanations to
55857 <at> debbugs.gnu.org and Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Request was from
Ludovic Courtès <ludo <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Thu, 27 Apr 2023 13:31:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#55857
; Package
guix
.
(Fri, 19 May 2023 03:35:01 GMT)
Full text and
rfc822 format available.
Message #30 received at 55857 <at> debbugs.gnu.org (full text, mbox):
Hi Ludo,
This bug was closed as notabug, but I still see it as an issue worth
fixing. Just using the (gnu services herd) API to query live services
ends up producing such a messages; I think from the 'resolve-transients'
procedure there that calls to eval-there unconditionally.
Perhaps the shepherd output could be redirected to /dev/null at that
specific place to avoid noisy output such as:
--8<---------------cut here---------------start------------->8---
2023-05-18 23:15:00 22491 /gnu/store/zmb73m7qgqagpb4vjhdd9jgkwp716p0m-wireguard-wg0-monitoring: running...
2023-05-18 23:15:00 22491 /gnu/store/zmb73m7qgqagpb4vjhdd9jgkwp716p0m-wireguard-wg0-monitoring: shepherd: Evaluating user expression (and (defined? (quote transient?)) (map (# ?) ?)).
2023-05-18 23:15:00 22491 /gnu/store/zmb73m7qgqagpb4vjhdd9jgkwp716p0m-wireguard-wg0-monitoring: completed in 0.029s
2023-05-18 23:20:00 22804 /gnu/store/zmb73m7qgqagpb4vjhdd9jgkwp716p0m-wireguard-wg0-monitoring: running...
2023-05-18 23:20:00 22804 /gnu/store/zmb73m7qgqagpb4vjhdd9jgkwp716p0m-wireguard-wg0-monitoring: shepherd: Evaluating user expression (and (defined? (quote transient?)) (map (# ?) ?)).
2023-05-18 23:20:00 22804 /gnu/store/zmb73m7qgqagpb4vjhdd9jgkwp716p0m-wireguard-wg0-monitoring: completed in 0.039s
2023-05-18 23:25:00 23849 /gnu/store/zmb73m7qgqagpb4vjhdd9jgkwp716p0m-wireguard-wg0-monitoring: running...
2023-05-18 23:25:00 23849 /gnu/store/zmb73m7qgqagpb4vjhdd9jgkwp716p0m-wireguard-wg0-monitoring: shepherd: Evaluating user expression (and (defined? (quote transient?)) (map (# ?) ?)).
2023-05-18 23:25:00 23849 /gnu/store/zmb73m7qgqagpb4vjhdd9jgkwp716p0m-wireguard-wg0-monitoring: completed in 0.028s
--8<---------------cut here---------------end--------------->8---
The above output is triggered by this code [0].
[0] https://issues.guix.gnu.org/63402#13-lineno225
--
Thanks,
Maxim
Information forwarded
to
bug-guix <at> gnu.org
:
bug#55857
; Package
guix
.
(Wed, 24 May 2023 13:50:02 GMT)
Full text and
rfc822 format available.
Message #33 received at 55857 <at> debbugs.gnu.org (full text, mbox):
Hi,
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:
> This bug was closed as notabug, but I still see it as an issue worth
> fixing. Just using the (gnu services herd) API to query live services
> ends up producing such a messages; I think from the 'resolve-transients'
> procedure there that calls to eval-there unconditionally.
I think the ‘eval-there’ call from ‘resolve-transients’ no longer
happens with shepherd 0.10.0, because the ‘transient?’ entry is always
present in the service alist.
Can you confirm?
Ludo’.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Thu, 22 Jun 2023 11:24:10 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 325 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.