lgr logging package.
Thanks to github user "duccioa" for the pull request (https://github.com/aryoda/tryCatchLog/pull/73)!set.logging.package() as preparation of feature request #42
(add convenience functions to activate other major logging packages).
Currently only futile.logger, lgr and tryCatchLog are supported as logging package.tryCatchLog.preferred.logging.package to configure which logging package
shall be used when the tryCatchLog package is loadedlogger.package.name to set.logging.functions() to allow
internal status printing of the active logging package (or custom functions)inst/doc/tryCatchLog-intro.html reported by win-builder on R-devel:
Found the following (possibly) invalid URLs:
URL: http://www.biostat.jhsph.edu/~rpeng/docs/R-debug-tools.pdf
(moved to https://www.biostat.jhsph.edu/~rpeng/docs/R-debug-tools.pdf)tryCatchLog.max.lines.per.call to change the maximum number of source code rows
printed in the full call stack per callImplement feature request #62: Optional logging of conditions via the new logged.conditions argument
(https://github.com/aryoda/tryCatchLog/issues/62). Conditions are now no longer logged by default
to avoid flooding the log output.
Many thanks to Valerian Wrobel for this contribution!
Implemented feature request #52: Add runtime context information to conditions (https://github.com/aryoda/tryCatchLog/issues/52)
Added the argument execution.context.msg to the tryCatchLog and try functions
to support an text identifier (eg. the PID or a variable value) that will be added to msg.text
for catched conditions. This makes it easier to identify the runtime state that caused
a condition esp. in parallel execution scenarios.
Idea and core implementation contributed by user '1beb' via pull request #53 (https://github.com/aryoda/tryCatchLog/pull/53). THX!
Note: In tryLog the new argument was added at the end to keep the function signature
compatible to existing code. In tryCatchLog the new argument was added as 3rd
argument to make it more visible. The signature is still compatible since it follows
the ... argument which requires all subsequent arguments to be named in calls.
Fixed bug: last.tryCatchLog.result() has sometimes not been reset in case of an internal error
so that the result of the previous tryCatchLog or tryLog call was returned (no issue number).
Thanks, we see:
Found the following (possibly) invalid file URIs: URI: LICENSE From: inst/doc/tryCatchLog-intro.html URI: cond From: NEWS.md
Please include the files in the correct directories or link to documents via fully specified URLs.
Implemented feature request #44: Support configurable suppression of compact and full stack trace (https://github.com/aryoda/tryCatchLog/issues/44).
tryCatchLog and tryCatch now have two additional arguments named
include.full.call.stack and include.compact.call.stack which can also be configured globally
via options.
Also closes (rejects) #5 (suppress empty compact stack trace) and implements #25 (add option for include.full.call.stack).
API breaking change: The function build.log.output has a new argument include.compact.call.stack
at the 3rd position which breaks the old interface
(only if the caller has passed subsequent arguments by position instead of using using the names).
tryCatchLog package was not attached first using library or depends (https://github.com/aryoda/tryCatchLog/issues/41)testthat with devtools has a known limitation required
by some tests: "Can't detach package in tests"
(https://github.com/r-lib/devtools/issues/1797)DESCRIPTION file to keep it ASCII-only
(required due to a new note produced by the winbuilder service)tryCatchLog package was not attached first using library or dependsdump_2019-03-13_at_15-39-33.086_PID_15270.rdaAdded parameter and options to write dump files into a specific folder:
See new write.error.dump.folder parameter and new tryCatchLog.write.error.dump.folder option.
Contributed by Charles Epaillard.
Closes https://github.com/aryoda/tryCatchLog/issues/37
API breaking change: tryLog has a changed API due to the newly inserted parameter write.error.dump.folder
at position 3.
Adjust your source code if you call tryLog and pass arguments by position using more than 2 arguments).
Added new function get.pretty.tryCatchLog.options for a convenient way of printing and logging
the current values of all options supported by the tryCatchLog package
set.logging.functions().
For details see: https://github.com/aryoda/tryCatchLog/issues/10futile.logger (in Imports section of DESCRIPTION file)
by implementing a package internal basic logging function log2console used as default
if the package futile.logger is not installedfutile.logger is now only Suggests in the DESCRIPTION file,
no longer ImportslimitedLabelsCompact does ignore maxwidth argument (logged call stack is too long)rmarkdown::html_vignette as output to minimize the HTML file sizerevealjs from "recommended" section in DESCRIPTION filetryCatchLog packageR CMD check warning (Undocumented code objects: ‘build.log.output’)tryLog and tryCatchLog not working for bubbled-up warningstryCatchLog callsbuild.log.output)last.tryCatch.resultbuild.log.output)build.log.output to create a single string suited as logging output from last.tryCatchLog.resultbuild.log.output extended to support not only one but many log entry rows at oncelast.tryCatch.result returns now a data.frame with separated logging items in columnstryCatchLog to be as close to tryCatch as possibletryCatchLog removedtryCatchLog(log("a"))last.tryCatchLog.log to last.tryCatchLog.result (clearer und avoid R CMD CHECK problem)last.tryCatchLog.log to retrieve the log output of the call of tryLog or tryCatchLog[[3L]](cond) : unused argument (cond)silent.messages to tryCatchLog and tryLogsilent.warnings to tryCatchLog and tryLogtryLog functiontryCatchLog function as "working horse"