Mark Stosberg

The advantage of using PSGI-native solutions is that you can deploy in PSGI, mod_perl or CGI with no code changes. :) @miketonks, also see #7 which discusses a completely PSGI-native...

We also generate an internal "ParseError" I have not checked to confirm it returns a string or an object as the "error" value.

I think this issue can be closed. Multiple comments have documented solutions that don't require modifying the code here.

@JMagers There's been no feedback since 2015-- how about releasing your own fork and opening your own issue tracker for the project?

The sway devs seem unlikely to add native systemd support any time soon. I think this issue can be closed.

@alextsits My ultimate solution was to use the "sway-systemd" project which does not run Sway as a systemd service but provides other systemd integrations: https://github.com/alebastr/sway-systemd I don't use this sway-services...

At first I thought I wanted to run `sway` as a systemd service myself, but found it more complex than I expected when I looked into it. The approach put...

What do you think should happen in the case where `msg` is provided in the object and as a string? log.info({"msg":"boom"},"zoom") Both before and after this patch, one of the...

@jbunton-atlassian In my project I override bunyan and *do* throw an error now if we call bunyan wrong. We didn't used to do that and were accidentally overriding the `name`...

Thanks for the recommendation. I'll have to investigate to see if it's "safer by default" than bunyan. On Thu, Oct 10, 2019 at 5:06 PM jbunton-atlassian wrote: > Also check...