-
Notifications
You must be signed in to change notification settings - Fork 295
feat: Add datetime.datetime support in pydict_to_metadata() for metadata forwarding #1329
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.
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
Merged
haixuanTao
merged 25 commits into
dora-rs:main
from
gaumrab:fix/datetime-metadata-support
Feb 9, 2026
Merged
Changes from 9 commits
Commits
Show all changes
25 commits
Select commit
Hold shift + click to select a range
773f582
Add Timestamp variant to Parameter enum in metadata (#1326)
9d48561
Enhance metadata handling by adding datetime conversion in pydict_to_…
2ae3a08
Add chrono dependency for enhanced datetime handling in metadata
65168b7
Add get_timestamp and set_timestamp methods to Metadata for handling …
8284cc2
Add chrono dependency with serde feature for enhanced datetime serial…
f83af86
Implement serialization for Timestamp variant in log_to_terminal func…
8d3ba13
Refactor datetime handling in pydict_to_metadata and metadata_to_pydi…
4b9cf39
Refactor Timestamp serialization in log_to_terminal function for impr…
b56b308
Add chrono dependency to Cargo.lock for enhanced datetime handling
bc1bbe1
Refactor timestamp handling in pydict_to_metadata for improved clarit…
dc97fbb
Refactor timestamp handling in pydict_to_metadata for improved effici…
a26314f
Enhance C++ build configuration by adding C++20 standard and suppress…
39860d7
Refactor timestamp handling in Metadata to use nanoseconds for improv…
33b2c44
Update CMake template to use C++20 standard for improved compatibility
c864b9e
Update C++ node build configuration to use C++20 standard for enhance…
629967a
Update C++ node build configuration to use C++20 standard for consist…
c2c9cbf
Update CMake configuration to set C++ standard to 20 for improved com…
f4a4612
Update C++ node build configuration to use C++20 standard for improve…
94ac2dd
Enhance C++ node README with C++20 timestamp support details
4b00bb6
Refactor timestamp conversion in Metadata to improve code clarity
d27f834
Refactor timestamp serialization in echo command for improved clarity
8a71991
Refactor timestamp serialization in Metadata for improved error handling
67af07a
Refactor timestamp serialization in Metadata for improved readability
c269db6
Refactor timestamp serialization in echo command for improved consist…
47eba11
Simplify C++ timestamp API docs and handle Timestamp in example
haixuanTao File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we can use C++20, how about using
std::chrono::time_point<sd::chrono::utc_clock>?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the suggestion! I noticed -std=c++17 in our example build files, but I haven’t confirmed which C++ standard the API bindings actually use. If C++20 is acceptable for the project, I’d be happy to use std::chrono::time_pointstd::chrono::utc_clock.
@phil-opp any thoughts on this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@haixuanTao @heyong4725 Any thoughts on this? Is requiring c++20 ok or do we want to stick to c++17?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's go ahead and switch to C++20 and the time_point type, and see if there are any issues. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok