-
Notifications
You must be signed in to change notification settings - Fork 373
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
Simpler, sturdier stateful time tracking in both SDKs #2506
Merged
+120
−185
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
05134de
make RecordingStream inject its internal clock when recording a row
teh-cmc 73d5b7a
record_path_op using the internal clock like everything else
teh-cmc 0c6fa05
get rid of manual time injection in python SDK
teh-cmc eeb1c21
get rid of manual time injection in rust SDK
teh-cmc 143fed3
update rust examples to get rid of manual time injection
teh-cmc 69be85d
MsgSender: dont advertise with_time*, it gets messy
teh-cmc 9a6827b
RecordingStream: friendler set_time_* funcs
teh-cmc 178edf5
update guide
teh-cmc 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
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.
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.
it looks like right now we're no longer using this timepoint anywhere as we're always seem to use the ones set on the recording (plus the ones the recording generates on adding a row)
I find it still very useful to have this here additionally (also makes logically a lot of sense), but feels like we're missing something in the (code) docs and examples about this 🤔 :
MsgSender::timepoint
doc string doesn't talk about this and we don't seem to have an example now that useswith_timestamp
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.
We're still using that timestamp the same way we did before, it gets added directly into the
DataRow
s thatMsgSender
generates (MsgSender::into_rows
).The only somewhat weird part is that these timestamps get potentially overridden by
RecordingStream
if the internal clock already has values for the same timelines.The reason this is weird is because
MsgSender
shouldn't exist anymore to begin with, it's just annoying and serves no real purpose anymore... it'll go away with codegen, in the meantime I'll markwith_timestamp
& friends as#[doc(hidden)
and update the starting guide.