* [sup-talk] logging and internal API changes in next
@ 2009-08-17 19:50 William Morgan
2009-08-17 20:31 ` Andrei Thorp
0 siblings, 1 reply; 2+ messages in thread
From: William Morgan @ 2009-08-17 19:50 UTC (permalink / raw)
Dear Suppers,
I've merged the aforementioned internal API changes, and a pretty big
rewrite of the logging system (branch "logging"), into next. It works
for me, but please report any problems you see.
All logging messages are now categorized by level (debug, info, warn,
error) and will only be output when the global logging level is <= the
message level. The global logging level is determined by the environment
variable SUP_LOG_LEVEL; when unset, the default is "info". You'll notice
that the majority of the messages you saw before are now "debug"
messages, so the log buffer is much quieter.
This change also applies to the various sup-* scripts.
If you use this code and then switch to a branch without these changes,
you may encounter errors because labels are now represented on disk as
Sets instead of arrays. The solution is to edit your sources.yaml file
and manually change the Sets back to arrays; it should be obvious how to
do this. I don't anticipate this affecting too many people. If it does,
we can transform labels to arrays before storing to make this easier,
but hopefully it's just a temporary issue.
I would like to merge these changes down to master sooner rather than
later, because they're so far-reaching.
--
William <wmorgan-sup at masanjin.net>
^ permalink raw reply [flat|nested] 2+ messages in thread
* [sup-talk] logging and internal API changes in next
2009-08-17 19:50 [sup-talk] logging and internal API changes in next William Morgan
@ 2009-08-17 20:31 ` Andrei Thorp
0 siblings, 0 replies; 2+ messages in thread
From: Andrei Thorp @ 2009-08-17 20:31 UTC (permalink / raw)
Excerpts from William Morgan's message of Mon Aug 17 15:50:52 -0400 2009:
> Dear Suppers,
>
> I've merged the aforementioned internal API changes, and a pretty big
> rewrite of the logging system (branch "logging"), into next. It works
> for me, but please report any problems you see.
>
> All logging messages are now categorized by level (debug, info, warn,
> error) and will only be output when the global logging level is <= the
> message level. The global logging level is determined by the environment
> variable SUP_LOG_LEVEL; when unset, the default is "info". You'll notice
> that the majority of the messages you saw before are now "debug"
> messages, so the log buffer is much quieter.
>
> This change also applies to the various sup-* scripts.
>
> If you use this code and then switch to a branch without these changes,
> you may encounter errors because labels are now represented on disk as
> Sets instead of arrays. The solution is to edit your sources.yaml file
> and manually change the Sets back to arrays; it should be obvious how to
> do this. I don't anticipate this affecting too many people. If it does,
> we can transform labels to arrays before storing to make this easier,
> but hopefully it's just a temporary issue.
>
> I would like to merge these changes down to master sooner rather than
> later, because they're so far-reaching.
Looking forward to it, thanks.
--
Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-08-17 20:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-08-17 19:50 [sup-talk] logging and internal API changes in next William Morgan
2009-08-17 20:31 ` Andrei Thorp
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox