Fix timezone logging #40
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hugomendix
requested changes
Feb 10, 2023
dahfjkg
force-pushed
the
dat/timezone-logging
branch
from
49d3b67 to
08c5ec9
Compare
dahfjkg
force-pushed
the
dat/timezone-logging
branch
from
08c5ec9 to
ef2fb1e
Compare
hugomendix
approved these changes
Feb 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
LogSessionTimeZoneDateNotationnow actually affects logging. its default value is now falseWe now display correct time zone ID in the log
ServerTimeZone value is changed to
UTC. That should not affect logging becauseUTCwas hard-coded before.