Should Console[F].printStackTrace reports stacktrace with tracing feature
See original GitHub issueCE provides a tracing functionality, given developers much more useful stack traces: https://typelevel.org/cats-effect/docs/tracing
When using Console[F].printStackTrace
however, the tracing functionality is not used.
Should we use the tracing functionality for this? Or should we provide another way to get access to those enhanced stack traces?
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
console.trace() - Web APIs - MDN Web Docs
The console.trace() method outputs a stack trace to the Web console. ... See Stack traces in the console documentation for details and examples....
Read more >JavaScript tips — Print stack traces using console.trace()
Calling console.trace() prints a stack trace to the console. This is useful for seeing the caller functions at that point in your code....
Read more >JavaScript Stack Trace: Understanding It and Using It to Debug
The stack trace helps us to know the steps that lead up to our error. And the stack trace isn't only useful for...
Read more >Analyze a stack trace - Android Developers
A stack trace generates when your app crashes because of an error or an exception. You can also print a stack trace at...
Read more >What is stacktrace and how to print in node.js ? - GeeksforGeeks
Using Error.captureStackTrace() Method: This method creates a .stack property on obj that returns a string representing the point in the code at ...
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
We are working on it. This will be available through
IO.trace
sometime soon.I actually think that, with the most recent changes @vasilmkd made, we don’t really need this anymore.
printStackTrace
is more general than printing exceptions which involve Cats Effect traces, so I think it’s better to keep it compartmentalized.