aryoda
aryoda
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
While Rs `traceback` shows the function call that caused an error top-most in the call stack output `tryCatchLog` shows it at the bottom (as many other programming languages do). This...
**Problem description:** If I log an error with eg. `tryCatchLog()` the stack trace lines are cut at a column width of 80 or similar which makes it difficult sometimes to...
E. g. - how to signal a condition (`signalCondition`?) - how to clean-up resources (`finally` or `on.exit`) - restart types provided by R (`invokeRestart("abort")` to "rethrow a caught interrupt condition"...
**See the excellent eRum 2018 presentation:** > Reducing bewilderment by improving errors | Lionel Henry > > Among the many unusual features of the R language, the condition system is...
Continuous deployment of package documentation with pkgdown and Travis CI: https://www.r-bloggers.com/continuous-deployment-of-package-documentation-with-pkgdown-and-travis-ci/