tryCatchLog
tryCatchLog copied to clipboard
R package for better error handling incl. logging with a full (!) stack trace incl. line numbers, post-mortem analysis and support for parallel processing
In #44 you asked an open question about whether there should be a matrix configuration to supress the trace specifically by condition type. This would be great in scripts where...
#10 introduced the possibility to inject your own logging functions. There are many logging packages at CRAN now. It would be very convenient if `tryCatchLog` provides functions to activate one...
To give the user a better error (or other condition) message a feature to replace all or selected conditions (or at least condition messages) by custom conditions (messages) would be...
To show the file name and line number that has thrown a condition the [current documentation at github](https://github.com/aryoda/tryCatchLog#the-stack-trace-does-not-contain-r-file-names-and-line-number-for-my-packages-how-can-i-enable-this) says: > enable the keep.source.pkgs option before (you install the packages!) It...
R 4.0.0 has been released today and brings some changes and features that might impact `tryCatchLog`. Examine the impact of the changes... - The internal traceback object produced when an...
The current implementation seems to log local times, not UTC. This makes it difficult to correlate log entries of different services on the same and other computers to get a...
Standard R also supports post-mortem dumps + debugging, see the description here: https://cran.r-project.org/doc/manuals/R-exts.html#Debugging-R-code > ... find out more about what was happening at the time of the crash by looking...
Add the possibility to disable the logging and printing of selected warnings. **Use cases:** * An R script produces well know warnings that shall not pollute the log file. **Implementation...
Currently the options that can be used to globally configure the behaviour of `tryCatchLog` functions are documented in different functions. Add a central documentation of the options so that users...
Use cases: - Wrap technical errors to present end-user-friendly errors (e. g. in shiny apps or other UIs) Mainly important for errors and warnings... Possible signature: ` rethrow