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

Add CI workflow to guard against increases in the binary size #6527

Closed
yurishkuro opened this issue Jan 11, 2025 · 1 comment · Fixed by #6529
Closed

Add CI workflow to guard against increases in the binary size #6527

yurishkuro opened this issue Jan 11, 2025 · 1 comment · Fixed by #6529
Labels
enhancement good first issue Good for beginners help wanted Features that maintainers are willing to accept but do not have cycles to implement

Comments

@yurishkuro
Copy link
Member

Similar to jaegertracing/jaeger-ui#2581, but for the main jaeger binary.

@yurishkuro yurishkuro added good first issue Good for beginners help wanted Features that maintainers are willing to accept but do not have cycles to implement labels Jan 11, 2025
@dosubot dosubot bot added the enhancement label Jan 11, 2025
@chahatsagarmain
Copy link
Contributor

Working on this .

yurishkuro pushed a commit that referenced this issue Jan 17, 2025
## Which problem is this PR solving?
- Fix for one issue caused in #6527 

## Description of the changes
- cache_output not being set after a cache hit using restore key
- Instead check for cache-matched-key != ''" 

## How was this change tested?
- 

## Checklist
- [ ] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [ ] I have signed all commits
- [ ] I have added unit tests for the new functionality
- [ ] 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: chahatsagarmain <[email protected]>
Manik2708 pushed a commit to Manik2708/jaeger that referenced this issue Jan 21, 2025
## Which problem is this PR solving?
- Fix for one issue caused in jaegertracing#6527 

## Description of the changes
- cache_output not being set after a cache hit using restore key
- Instead check for cache-matched-key != ''" 

## How was this change tested?
- 

## Checklist
- [ ] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [ ] I have signed all commits
- [ ] I have added unit tests for the new functionality
- [ ] 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: chahatsagarmain <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement good first issue Good for beginners help wanted Features that maintainers are willing to accept but do not have cycles to implement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants