Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump @pyroscope/flamegraph to 0.18.4 #977

Conversation

pavelpashkovsky
Copy link
Contributor

@pavelpashkovsky pavelpashkovsky commented Aug 11, 2022

Signed-off-by: pavelpashkovsky pavelpashkovsky@gmail.com

Which problem is this PR solving?

  • Bumping @pyroscope/flamegraph to 0.18.4

Short description of the changes

Signed-off-by: pavelpashkovsky <pavelpashkovsky@gmail.com>
@codecov
Copy link

codecov bot commented Aug 11, 2022

Codecov Report

Merging #977 (7739d75) into main (f67399f) will increase coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #977      +/-   ##
==========================================
+ Coverage   95.29%   95.42%   +0.13%     
==========================================
  Files         243      243              
  Lines        7560     7560              
  Branches     1892     1892              
==========================================
+ Hits         7204     7214      +10     
+ Misses        349      339      -10     
  Partials        7        7              
Impacted Files Coverage Δ
...mponents/TracePage/TraceStatistics/tableValues.tsx 96.55% <0.00%> (+2.75%) ⬆️
...nents/TracePage/TraceTimelineViewer/SpanBarRow.tsx 100.00% <0.00%> (+5.55%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@@ -42,7 +42,7 @@
},
"dependencies": {
"@jaegertracing/plexus": "0.2.0",
"@pyroscope/flamegraph": "0.18.4-1379-557f0b4.0",
"@pyroscope/flamegraph": "0.18.4",
Copy link
Member

Choose a reason for hiding this comment

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

while I have you, I wanted to ask - in the last merge I am seeing that the numbers in the flame graph & table are in "units", which is pretty confusing. It sounds like a technical reason (library may not know the units of numbers), but couldn't we pass some parameter to it to make it more obvious? Also, I'm just curious under what conditions the numbers in the flamegraph are not time units - if they are always time than it seems like the graph could always display them with proper time units like s, ms, etc.

Copy link

@Rperry2174 Rperry2174 Aug 11, 2022

Choose a reason for hiding this comment

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

The flamegraph component can be used for visualizing other arbitrary data that does have other units.

Makes sense though that for traces it will always be time so made a Pr to fix this:
grafana/pyroscope#1387

It's released now in flamegraph v0.18.5

@yurishkuro yurishkuro merged commit e2ae62a into jaegertracing:main Aug 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants