feat(ui): refactor of latency and minor fixes #42
Conversation
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
Contributor
rozzilla
commented
Mar 20, 2025
- Fixes to how we calculate the latency for aggregated data
- Unify CPU/latency components for better maintainability (and to simplify migration to TS code as we are doing here)
Member
|
I've landed the TS refactoring. |
Signed-off-by: Roberto Bianchi <roberto.bianchi@spendesk.com> update Signed-off-by: Roberto Bianchi <roberto.bianchi@spendesk.com>
517c79b to
33c8fef
Compare
Contributor
Author
Nice! Conflix fixed. I will complete the TS refactoring on a follow up PR 😉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.