You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Additive configuration is problematic - suggest overriding instead #21
The problem is that the stream configurations are additive. So in the development environment we end up logging two streams to STDOUT: one using color and the other using json. This makes development very difficult to read and unnecessarily verbose.
I propose when we have a stream in development it overrides all streams from above it, to allow for greater flexibility in configuration. Arguably the same should go for all appenders; I wonder whether we're logging twice to datadog?
That's not what I see locally in Filler on master, which is up to date on reevoo_sapience-rb. I see two streams of output for everything to STDOUT, one color and one json. There are no overrides in config/sapience.yml in Filler for development either....
Activity
mhenrixon commentedon Dec 14, 2016
It isn't additive. Any key under the environment replaces the one in the parent.
seddy commentedon Dec 14, 2016
That's not what I see locally in Filler on
master, which is up to date onreevoo_sapience-rb. I see two streams of output for everything toSTDOUT, onecolorand onejson. There are no overrides inconfig/sapience.ymlin Filler for development either....mhenrixon commentedon Dec 14, 2016
Most probably then it gets initialized oddly :) If you try
Sapience.configure(force: true)in filler does that fix your problem?seddy commentedon Dec 14, 2016
Nope :(
Specifically look a the double log line for
SELECT * FROM reviewswhen callingReview.firstseddy commentedon Dec 14, 2016
Although interestingly, the configured
appendersin that log output is actually showing acolorone toSTDOUT!!! Maybe this is something else?