Bug: stack trace error
See original GitHub issueDescribe the bug After updating to 2.6.1 I got error in bluebird
/node_modules/bluebird/js/release/debuggability.js:768 var lastStackLines = (lastLineError.stack || "").split("\n");
seems like tslog converts error.stack into array
To Reproduce
const { Logger } = require("tslog");
const promise = require("bluebird");
const logger = new Logger();
async function run() {
try {
await promise.any([Promise.resolve()]);
} catch (err) {
logger.error(err);
}
}
run();
Additional context Node.JS 12.18.0 tslog ^2.6.1
Seems related #33
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Stack Trace: How to Debug Your Application With a Stack Trace
A stack trace is a valuable piece of information that can be used for debugging purposes. Whenever you encounter an error in your...
Read more >Fix bugs in Bash scripts by printing a stack trace
Automatically printing a stack trace on unhandled errors in your scripts can make finding and fixing bugs in your code much easier.
Read more >Analyze a stack trace - Android Developers
Debugging an app often requires working with stack traces. A stack trace generates when your app crashes because of an error or an...
Read more >java - What is a stack trace, and how can I use it to debug my ...
In simple terms, a stack trace is a list of the method calls that the application was in the middle of when an...
Read more >Making stack traces more useful with symbolication - Bugsnag
When debugging errors, symbolicated stack traces are essential because they provide visibility into where the errors originated in the code.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@terehov Works fine now. Thank you.
Should be fixed in
2.6.2
.