-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with error objects in meta (regression v2.3.0 -> v2.3.1) #1007
Comments
Do you think it is related to #1011 ? |
+1 |
1 similar comment
+1 |
As far as I can see, this regression was brought by the PR #977. |
gunar
added a commit
to invisible-tech/logger
that referenced
this issue
Oct 25, 2017
Affects v2.4.0 as well |
We're still getting this error on |
#1188 should fix this. A maintenance release will be made tomorrow. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
we see a problem with [email protected]. Here is the gist reproducing it: https://gist.github.com/OrKoN/9c5b212058563043a94fa144d460d1d4
When run with winston 2.3.1, it outputs:
When run with winston 2.3.0, it outputs:
The latter one is the expected behavior in my opinion. I tried to trace it down and it seems cycle.decycle removes the error object from the meta.
Any idea why this happening?
Also if we use the normal Consol transport, then the error is empty in both 2.3.0 and 2.3.1. My node version is v6.9.4.
The text was updated successfully, but these errors were encountered: