Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Clarify serialization behavior of Duration* and Timestamp* types #626

Merged
merged 1 commit into from
Jul 31, 2023
Merged

Clarify serialization behavior of Duration* and Timestamp* types #626

merged 1 commit into from
Jul 31, 2023

Conversation

jonasbb
Copy link
Owner

@jonasbb jonasbb commented Jul 31, 2023

Closes #625

bors r+

@bors
Copy link
Contributor

bors bot commented Jul 31, 2023

Build succeeded!

The publicly hosted instance of bors-ng is deprecated and will go away soon.

If you want to self-host your own instance, instructions are here.
For more help, visit the forum.

If you want to switch to GitHub's built-in merge queue, visit their help page.

@bors bors bot merged commit b81abda into master Jul 31, 2023
18 checks passed
@bors bors bot deleted the doc-update branch July 31, 2023 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Using TimestampMilliSeconds to serialize DateTime<Utc> differs from calling DateTime<Utc>::timestamp_millis
1 participant
@jonasbb