RecordingStream: automatic log_tick timeline
#2072
Merged
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
teh-cmc
added
🏹 arrow
teh-cmc
commented
May 9, 2023
jprochazk
pushed a commit
that referenced
this pull request
May 11, 2023
* RecordingStream: automatic log_tick timeline (per-recording, per-process) * adjust default timeline heuristics to account for 'log_tick' * use our timeline constants everywhereg * timeless-ness shenanigans * more docs * issue
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.
Introduces a new per-recording per-process
log_ticktimeline, automatically derived on behalf of the user.Future work:
#2042