-
Notifications
You must be signed in to change notification settings - Fork 373
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Simpler, sturdier stateful time tracking in both SDKs (#2506)
(Probably easier to review commit by commit) Follow up to my discussion with @abey79 regarding his poor experience with time tracking, which was summarized in #2501 (comment): > - When implementing the `step` timeline of the scalar example, I first searched for `set_time_sequence` (used in Python API) in the Rust docs, which I found in `RecordingStream`. Turns out it's not in 0.7 and bugged on `main` (or rather ignored by `MsgSender`). Again, it compiled and displayed no error, but no timeline was created. This PR makes it so that `RecordingStream` is always in charge of injecting its internal clock into outgoing rows (unless the caller ask it not to, e.g. because the data is meant to be timeless). This is pretty similar to what was already in place for `log_tick`, except it now applies to every timelines, whether they are builtin or user defined. - Within the Python SDK, this gets rid of all the existing manual time injection stuff. - On the Rust SDK's side, this fixes the issue that `MsgSender` used to ignore the internal clock altogether (i.e. the stateful time APIs were not supported at all for Rust users). - And finally this cleans up the Rust examples a bunch since we now have access to stateful time. --- <!-- This line will get updated when the PR build summary job finishes. --> PR Build Summary: https://build.rerun.io/pr/2506 <!-- pr-link-docs:start --> Docs preview: https://rerun.io/preview/178edf5/docs Examples preview: https://rerun.io/preview/178edf5/examples <!-- pr-link-docs:end -->
- Loading branch information
Showing
9 changed files
with
120 additions
and
185 deletions.
There are no files selected for viewing
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
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
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
Oops, something went wrong.