Skip to content

FIX 1338: Error object is not parsed or printed#1527

Closed
crowleym wants to merge 2 commits into
winstonjs:masterfrom
crowleym:bug/1338
Closed

FIX 1338: Error object is not parsed or printed#1527
crowleym wants to merge 2 commits into
winstonjs:masterfrom
crowleym:bug/1338

Conversation

@crowleym
Copy link
Copy Markdown

@crowleym crowleym commented Nov 7, 2018

Simple fix for Error objects being lost when passed as meta

logger.error("blah", new Error("oops"));

@crowleym
Copy link
Copy Markdown
Author

crowleym commented Nov 7, 2018

Previous build have failed with same issue.
Something to do with log tailing as opposed to this fix. Not sure how to rerun tests

@crowleym crowleym closed this Nov 7, 2018
@crowleym crowleym reopened this Nov 7, 2018
@crowleym
Copy link
Copy Markdown
Author

crowleym commented Nov 7, 2018

Rerun tests.

@crowleym crowleym closed this Nov 9, 2018
@crowleym
Copy link
Copy Markdown
Author

crowleym commented Nov 9, 2018

Need to understand these test failures.

@crowleym
Copy link
Copy Markdown
Author

This covers all options. However some tests fail. The failures are expected given the fix, but I don't believe I am in a position to make the call to amend/delete the tests.

Failing build is here https://travis-ci.org/winstonjs/winston/jobs/453012141 and its obvious why the tests now fail when you read the test code:

assume(info).instanceOf(Error);

Thoughts?

@crowleym crowleym reopened this Nov 14, 2018
@indexzero
Copy link
Copy Markdown
Member

Closing in favor of #1562. Thank you for your contribution none the less!

@indexzero indexzero closed this Jan 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants