Skip to content

Releases: aryoda/tryCatchLog

CRAN release v1.3.1 (Oct 24, 2021)

25 Oct 07:17
Compare
Choose a tag to compare

See https://cran.r-project.org/package=tryCatchLog

Version 1.3.1 (Oct 24, 2021) for CRAN

Version 1.3.0 (Sept 30, 2021)

  • Fix critical bug #68: Bad condition logging performance with bug data sizes
    (#68)
  • Limit the maximum number of source code rows printed in the full call stack per call to 10
    (was unlimited before which cause bug #68 if large data in arguments was printed too)
  • Add option tryCatchLog.max.lines.per.call to change the maximum number of source code rows
    printed in the full call stack per call

Version 1.2.5 (Sept 06, 2021)

  • Implement feature request #62: Optional logging of conditions via the new logged.conditions argument
    (#62). Conditions are now no longer logged by default
    to avoid flooding the log output.

    Many thanks to Valerian Wrobel for this contribution!

CRAN release v1.2.4 (May 21, 2021)

21 May 07:19
Compare
Choose a tag to compare

See NEWS file for the changes:

Version 1.2.4 (May 21, 2021) for CRAN

Version 1.2.3 (May 16, 2021) - submitted at CRAN but rejected

  • Fix bug #64: Unit tests fail on R-devel (test_build_log_entry.R and test_build_log_output).
    Many thanks to Brodie Gaslam to find and help fixing this bug!
  • Extend the maximum value of the `maxwidth argument of limitedLabels() from 1000 to 2000.
    This was required for a decent fix of bug #64.

Version 1.2.2 (Jan. 8, 2021)

  • Fix bug #63: Severity level is contained twice in the log message output line

CRAN release v1.2.1 (Nov 25, 2020)

25 Nov 07:10
Compare
Choose a tag to compare

Change log (compared to v1.1.6_CRAN):

Version 1.2.1 (Nov. 24, 2020) for CRAN

Version 1.2.0 (Nov 23, 2020) for CRAN

  • CRAN release version
  • Fix r-devel finding "Found the following (possibly) invalid URLs" caused by http to https redirection
  • Fix bug #60: sprintf warnings in R-devel (CRAN check)

Version 1.1.8 (April 20, 2020)

  • Implemented feature requests #14 and #45: Support logging of all conditions (incl. user-defined conditions).
    • Interrupt conditions are logged with the message "User-requested interrupt"
      even though R does not deliver a message. (incl. user-defined and interrupt)
    • #14
    • #45
  • Fixed bug #55: Duplicated error dump files in nested tryCatchLog calls

Version 1.1.7 (April 6, 2020)

  • Implemented feature request #52: Add runtime context information to conditions
    (#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 (#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).

Feature release v1.1.7 (April 6, 2020)

20 Apr 20:14
Compare
Choose a tag to compare
Pre-release
  • Implemented feature request #52: Add runtime context information to conditions

    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 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).

CRAN release v1.1.6 (Nov 6, 2019)

06 Nov 19:54
Compare
Choose a tag to compare
  • Fixes #50 (tryCatchLog was removed from CRAN in Oct. 2019).
  • Publishes the newly implemented features at CRAN

Feature release v1.1.5 (Oct. 1, 2019)

30 Sep 22:07
Compare
Choose a tag to compare

Implemented feature request #44: Support configurable suppression of compact and full stack trace
(#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.

CRAN release v1.1.4 (March 26, 2019)

26 Mar 06:01
Compare
Choose a tag to compare

This is a version officially published at the CRAN repository.

See: https://cran.r-project.org/package=tryCatchLog

Please note that this "hotfix" version for previous CRAN version of last week
solving an issue if tryCatchLogis not used via library (see #41).

CRAN release v1.1.2 (March 20, 2019)

20 Mar 16:59
Compare
Choose a tag to compare

This is the second version officially published at the CRAN repository.

See: https://cran.r-project.org/package=tryCatchLog

Please note that this version has a major issue if not used via library (see #41).

CRAN version 1.0.2 (May 18, 2018)

18 May 17:37
Compare
Choose a tag to compare

This is the first version officially published at the CRAN repository.

See: https://cran.r-project.org/package=tryCatchLog