Fix up first column unit on trace detail #5133
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
|
cc @danmoseley |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
3 tasks
adamint
approved these changes
Aug 1, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The first column always has a value of zero. Originally it displayed the smallest unit:
0μs. That looked odd.A later update removed the unit so it just displayed zero:
0. Better but not perfect.This PR uses the unit from the next column. So, if the next unit is
msthen the first column is0ms. If the next unit issthen the first column is0s.Microsoft Reviewers: Open in CodeFlow