Skip to content

Conversation

@k-fish
Copy link
Member

@k-fish k-fish commented Jun 4, 2024

Summary

This uses the quantization from the backend when provided (trace breakdowns), but still uses time for the spans since they don't have quantization.

Screenshot 2024-06-04 at 2 47 54 PM

This uses the quantization from the backend when provided (trace breakdowns), but still uses time for the spans since they don't have quantization.
@k-fish k-fish self-assigned this Jun 4, 2024
@k-fish k-fish requested a review from a team June 4, 2024 18:48
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jun 4, 2024
@k-fish k-fish enabled auto-merge (squash) June 4, 2024 18:49
@codecov
Copy link

codecov bot commented Jun 4, 2024

Bundle Report

Changes will decrease total bundle size by 59.14kB ⬇️

Bundle name Size Change
app-webpack-bundle-array-push 27.89MB 59.14kB ⬇️

@k-fish k-fish merged commit 1ef63d4 into master Jun 4, 2024
@k-fish k-fish deleted the feat/traces/use-slices-not-percent branch June 4, 2024 19:01
Copy link
Member

@mjq mjq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh looks like this already got merged, flagging a weird conditional just in case still

const sliceDuration = sliceEnd - sliceStart;

if (sliceDuration <= 0) {
if (sliceNumberWidth === 0 && sliceNumberWidth === undefined && sliceDuration <= 0) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sliceNumberWidth === 0 && sliceNumberWidth === undefined

Isn't that always false?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, this should be sliceNumberWidth === 0 || (sliceNumberWidth === undefined && sliceDuration <= 0), I must have accidentally undone this.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should just be entirely removed anyway actually, we have checks on the backend now, don't need this defensive code anymore.

@github-actions github-actions bot locked and limited conversation to collaborators Jun 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants