Expose all repeated measure durations in span queries - #219
Merged
jantimon merged 1 commit intoSep 6, 2026
Conversation
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Repeated named measures expose every recorded duration through
query span --format json|toon. The timing block usessampleUnit: "occurrence", since one iteration can emit several measures with the same name.Chrome and Firefox derive these durations from each measure's start and end. Firefox's sampled profile window can differ from those bounds. The profile bar keeps the occurrence with the lower-median profiled wall time; timing statistics describe the full duration series. Missing series return
null.Includes capture-order storage, documentation, and a minor changeset. This PR builds on #218 and targets its branch.
Validation: 774 unit tests, six measurement tests, the focused Chrome record-to-query test, TypeScript build, lint, formatting, and unused-code checks pass. Tests cover six occurrences across three iterations, JSON and TOON output, missing series, and Firefox measure durations that differ from sampled profile windows.