In August, the loggo package was changed to make it log ANSI-terminal
colour escape sequences by default.
I'm not sure that was the right decision, for a couple of reasons:
- daemons are often given a pseudo tty to run in, so the log files
produced by our running services are now obscured by esca
I've proposed an initial PR to address this:
https://github.com/juju/loggo/pull/25
On 21 February 2017 at 14:02, roger peppe wrote:
> In August, the loggo package was changed to make it log ANSI-terminal
> colour escape sequences by default.
>
> I'm not sure that was the right decision, for a c
On Tue, Feb 21, 2017 at 10:02 PM roger peppe
wrote:
> In August, the loggo package was changed to make it log ANSI-terminal
> colour escape sequences by default.
>
> I'm not sure that was the right decision, for a couple of reasons:
>
> - daemons are often given a pseudo tty to run in, so the log
Hi folks,
Just merged into the "devel" branch (will be 2.2 branch) is a change in
the library Juju is using for websockets.
Hopefully you won't notice a thing, but if you do see strange
interactions I'd love to know.
I did test with new CLI / old controller, and it works, and tested with
n
Tech board says "yes let's do it", I'll respond to PR.
On 22/02/17 14:15, Andrew Wilkins wrote:
On Tue, Feb 21, 2017 at 10:02 PM roger peppe mailto:roger.pe...@canonical.com>> wrote:
In August, the loggo package was changed to make it log ANSI-terminal
colour escape sequences by default
