Handling uncaught exceptions
See original GitHub issueSo I am working on a project where there are many sagas and sometimes they result in errors. In development the errors get logged to the console (which is quite nice), but in production I’d like to be able to capture the exception and send it to an error monitoring service (such as honeybadger or getsentry), is there a way to do this?
The only thing I can think of is instead of passing many sagas to createSagaMiddleware
to only pass a single root saga and to manually capture the error in the root saga after forking every other saga. Is there another approach that I could use?
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
How uncaught exceptions are handled in Java - Javamex
Java actually handles uncaught exceptions according to the thread in which they occur. When an uncaught exception occurs in a particular thread, Java...
Read more >android - Need to handle uncaught exception and send log file
Handle uncaughtException in your Application subclass. · After catching an exception, start a new activity to ask the user to send a log....
Read more >20.4 — Uncaught exceptions and catch-all handlers - Learn C++
If your program uses exceptions, consider using a catch-all handler in main, to help ensure orderly behavior when an unhandled exception occurs.
Read more >Uncaught Exceptions in Java - BTech Smart Class
The uncaught exceptions are the exceptions that are not caught by the compiler but automatically caught and handled by the Java built-in exception...
Read more >Handling of Uncaught Exceptions in Haskell - Serokell
Handling of Uncaught Exceptions in Haskell ... When your Haskell application's thread throws an exception that does not get caught, the Haskell ...
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 FreeTop 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
Top GitHub Comments
@axelson For
fork
ed sagas you can use thedone
property to catch errorsyou can do the same thing with
call
ed sagas by putting the call in a try/catch then rethrow the error.@ronanwize re “we actually decided to push that down a layer so anything running in a saga will return an error object we can test for”: how did you create a lower level layer in which you can catch all sagas’ exceptions?