We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why is the severity level (here: "error") contained twice?
> library(tryCatchLog) Using futile.logger for logging... > tryCatchLog(stop("msg")) ERROR [2021-01-08 18:58:30] [ERROR] msg Compact call stack: 1 tryCatchLog(stop("msg")) ...
This could be caused by futile logger...
The text was updated successfully, but these errors were encountered:
Analysis results:
The reason seems to be that
tryCatchLog
build.log.output
futile.logger
flog
> flog.warn("msg") WARN [2021-01-08 20:14:07] msg > tryCatchLog:::log2console("WARN", "msg") WARN [2021-01-08 20:19:06] msg
tryCatchLog should not include the severity level in the msg text itself but leave this to the logger function that corresponds to the severity level.
The bug was probably already introduced in commit 7c8e245 (Dec 3, 2017)!
Sorry, something went wrong.
5c4fdd4
Increase version number and extend NEWS for bug fix #63
0dc4e8e
No branches or pull requests
Why is the severity level (here: "error") contained twice?
This could be caused by futile logger...
The text was updated successfully, but these errors were encountered: