propellor/src/Propellor/Message.hs, branch mastergnusosa's centralized propellor repository for hosts spin-up.
https://git.gnusosa.net/propellor/atom?h=master2017-08-01T17:30:48ZImprove PROPELLOR_TRACE output so serialized trace values always come on their own line, not mixed with title setting.2017-08-01T17:30:48ZJoey Hessjoeyh@joeyh.name2017-08-01T17:30:48Zurn:sha1:63be08678829f5b83c39f2f6a9d44cc920b7892fMerge branch 'master' into joeyconfig2017-07-30T15:30:05ZJoey Hessjoeyh@joeyh.name2017-07-30T15:30:05Zurn:sha1:15f292d177ee96f5a1d384ce50f5246e3f7ea630Expand the Trace data type.2017-07-29T21:24:24ZJoey Hessjoeyh@joeyh.name2017-07-29T21:24:24Zurn:sha1:236ba63c7eece6adccae589fc0acc1425918d4eb
Technically this is an API change, but the only thing I'm breaking at this
point is my own unreleased software.
display end trace after displaying normal end message2017-07-29T19:48:42ZJoey Hessjoeyh@joeyh.name2017-07-29T19:48:42Zurn:sha1:8b1e077caff64fb6e538aebbb8f7c7d9deb4735aAdded PROPELLOR_TRACE environment variable2017-07-29T19:43:57ZJoey Hessjoeyh@joeyh.name2017-07-29T19:43:57Zurn:sha1:ef7f2bb7fd6a79ee3e9d0abbaf6f002c146f3fbc
which can be set to 1 to make propellor output serialized
Propellor.Message.Trace values, for consumption by another program.
This commit was sponsored by Ewen McNeill.
avoid buffering container chain output2017-07-05T17:52:29ZJoey Hessjoeyh@joeyh.name2017-07-05T17:52:29Zurn:sha1:2b9d5ca90f053ad21fbbab89b3045bd0822400d5
When provisioning a container, output was buffered until the whole process
was done; now output will be displayed immediately.
I know this didn't used to be a problem. I belive it was introduced by
accident when propellor started using concurrent-output. I know I've seen
it for a while and never was bothered enough to get to the bottom of it;
apparently "a while" was longer than I thought.
Also refactored code to do with chain provisioning to all be in
Propellor.Engine and avoided some duplication.
This commit was sponsored by Anthony DeRobertis on Patreon.
Revert "speed up chain output displaying"2017-07-05T17:23:33ZJoey Hessjoeyh@joeyh.name2017-07-05T17:23:33Zurn:sha1:4eb2a663e4d4ff00d121c5f595f2eb7248b98199
This reverts commit c59ce983999ddbfe6cb8b27e4f376b5c37d7f853.
That was wrong because only the *last* line of chain output is a Result.
It could be that a previous line is able to be read as a Result, and
the commit would make processing bail out at that point.
propellor spin2017-07-05T17:15:26ZJoey Hessjoeyh@joeyh.name2017-07-05T17:15:26Zurn:sha1:88c02486abcf45067483bd6a138b046397491889speed up chain output displaying2017-07-05T17:10:59ZJoey Hessjoeyh@joeyh.name2017-07-05T17:10:59Zurn:sha1:c59ce983999ddbfe6cb8b27e4f376b5c37d7f853
Avoid needing to wait for a subsequent line before displaying the
previous line.
Display error and warning messages to stderr, not stdout.2017-06-18T20:20:12ZJoey Hessjoeyh@joeyh.name2017-06-18T20:20:12Zurn:sha1:86232b50062b7129da0cac2dd2059fce3db9276b