Skip to content

[Format error in 2.0.0] \n is not added to msg printed in crash.log via call error_logger:error_report(Any) while everything seems ok in error.log #164

define-null opened this Issue Aug 8, 2013 · 1 comment

3 participants


We have some code which uses error_logger:error_report(Any) calls. After switching to lager we found out that this messages are formatted without \n at the end of the string which causes crash.log to be not very easy to read. Something like^

2013-08-07 21:14:21 =ERROR REPORT====
[{<<"Ping failed">>,{error,req_timedout}}]2013-08-07 21:15:14 =ERROR REPORT====
[{<<"Indicators failed">>,{error,req_timedout}}]2013-08-07 21:15:23 =ERROR REPORT====
Vagabond commented Feb 7, 2014

Confirmed, testing a fix.

@mrallen1 mrallen1 closed this Jun 24, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.