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

Make changes to allow for /api/quality-metrics to work #2641

Merged
merged 10 commits into from
Feb 15, 2025

Conversation

ADI-ROXX
Copy link
Contributor

@ADI-ROXX ADI-ROXX commented Jan 28, 2025

Which problem is this PR solving?

Description of the changes

How was this change tested?

  • manually

Checklist

Signed-off-by: cs-308-2023 <[email protected]>
@ADI-ROXX ADI-ROXX requested a review from a team as a code owner January 28, 2025 15:56
@ADI-ROXX ADI-ROXX requested review from jkowall and removed request for a team January 28, 2025 15:56
@ADI-ROXX
Copy link
Contributor Author

@yurishkuro Some tests are failing. I have to make changes in the .test.js files

@yurishkuro
Copy link
Member

lgtm. Is it correct that this is a breaking change (different data shape is expected)? Please document it in the description.

@yurishkuro
Copy link
Member

can you get the CI to green? Both linter and unit tests are failing.

@ADI-ROXX
Copy link
Contributor Author

ADI-ROXX commented Feb 3, 2025

Is it correct that this is a breaking change (different data shape is expected)?

I didn't understand. Can you elaborate it a bit? What data shape is actually expected?

@yurishkuro
Copy link
Member

You are now parsing data in a different shape than before (the "data" sub-structure in json)

@ADI-ROXX
Copy link
Contributor Author

ADI-ROXX commented Feb 3, 2025

You are now parsing data in a different shape than before (the "data" sub-structure in json)

Are you referring to this:
image

@yurishkuro
Copy link
Member

yes

Signed-off-by: cs-308-2023 <[email protected]>
Signed-off-by: cs-308-2023 <[email protected]>
Signed-off-by: cs-308-2023 <[email protected]>
Copy link

codecov bot commented Feb 12, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.62%. Comparing base (625a57a) to head (c2a896d).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2641   +/-   ##
=======================================
  Coverage   96.62%   96.62%           
=======================================
  Files         256      256           
  Lines        7732     7733    +1     
  Branches     2018     2018           
=======================================
+ Hits         7471     7472    +1     
  Misses        261      261           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Signed-off-by: cs-308-2023 <[email protected]>
Signed-off-by: cs-308-2023 <[email protected]>
@ADI-ROXX
Copy link
Contributor Author

Please document it in the description.

Added in the description of the PR

yurishkuro pushed a commit to jaegertracing/jaeger that referenced this pull request Feb 12, 2025
## Which problem is this PR solving?
- Resolves #6607 
- Related to jaegertracing/jaeger-ui#2640
- Related to the PR:
jaegertracing/jaeger-ui#2641

## Description of the changes
- 

## How was this change tested?
- 

## Checklist
- [x] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [x] I have signed all commits
- [x] I have added unit tests for the new functionality
- [x] I have run lint and test steps successfully
  - for `jaeger`: `make lint test`
  - for `jaeger-ui`: `npm run lint` and `npm run test`

---------

Signed-off-by: cs-308-2023 <[email protected]>
@@ -92,9 +92,10 @@ export class UnconnectedQualityMetrics extends React.PureComponent<TProps, TStat
this.setState({ loading: true });

JaegerAPI.fetchQualityMetrics(service, lookback)
.then((qualityMetrics: TQualityMetrics) => {
this.setState({ qualityMetrics, loading: false });
.then((qualityMetrics: { data: TQualityMetrics }) => {
Copy link
Member

Choose a reason for hiding this comment

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

I don't understand why we need to be making a breaking change to the data format? The current code does not expect data: element. The backend code does not require it either.

yurishkuro and others added 3 commits February 15, 2025 09:10
@yurishkuro yurishkuro added the changelog:bugfix-or-minor-feature 🐞 Bug fixes, Minor Improvements label Feb 15, 2025
Signed-off-by: Yuri Shkuro <[email protected]>
@yurishkuro yurishkuro enabled auto-merge February 15, 2025 13:33
@yurishkuro yurishkuro added this pull request to the merge queue Feb 15, 2025
Merged via the queue into jaegertracing:main with commit 655f2b7 Feb 15, 2025
9 checks passed
github-merge-queue bot pushed a commit to jaegertracing/jaeger that referenced this pull request Feb 15, 2025
## Which problem is this PR solving?
- Follow up to #6608
- Resolves #6607

## Description of the changes
- Remove intermediate `data:` element from the response
- Match response to what the UI expects
- Fix unit test that wasn't testing the output

## How was this change tested?
- unit tests
- manual test with jaegertracing/jaeger-ui#2641

---------

Signed-off-by: Yuri Shkuro <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog:bugfix-or-minor-feature 🐞 Bug fixes, Minor Improvements
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature]: Make changes to allow for /api/quality-metrics to work
2 participants