You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the other hand using only UTC drives me crazy when I try to understand logs and my timezone is different (eg. searching and filtering requires time zone calculations).
I suggest to add another column named "timezone.UTC" to build.log.entry() to let the user see both time zones (local + UTC).
And the time zone of the logging framework output should be left untouched in tryCatchLog since it is a configuration (or default setting) of the logging framework.
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 holistic picture of log events.
The internal implementations uses
tryCatchLog/R/tryCatchLog.R
Line 239 in f3fdebd
which returns an absolute date-time value of class
POSIXct
but when a log entry is created the local time zone may be applied...The text was updated successfully, but these errors were encountered: