refactor: remove custom utc_now in favor of chrono::Utc:now feature
#23888
Conversation
This file contains 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
fbaltor
force-pushed
the
refactor-chrono-22864
branch
from
de3b230
to
b89ee71
Compare
bartlomieju
approved these changes
May 22, 2024
There was a problem hiding this comment.
LGTM, thank you @fbaltor, really good cleanup.
@littledivy are you fine with this one? The linking tests pass so I think we're good.
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.
This PR removes the use of the custom
utc_nowfunction in favor of thechronoimplementation. It resolves #22864.