Skip to content
This repository was archived by the owner on Oct 6, 2025. It is now read-only.

Conversation

sivchari
Copy link
Member

No description provided.

Copy link

codecov bot commented Mar 11, 2025

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 47.91%. Comparing base (8849c3f) to head (7e520a1).
Report is 40 commits behind head on master.

Files with missing lines Patch % Lines
pkg/utils/json/json.go 0.00% 2 Missing ⚠️
Additional details and impacted files
@@ Coverage Diff @@ ## master #698 +/- ## ========================================== - Coverage 54.26% 47.91% -6.35%  ========================================== Files 64 64 Lines 6164 6461 +297 ========================================== - Hits 3345 3096 -249  - Misses 2549 3111 +562  + Partials 270 254 -16 

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
Signed-off-by: sivchari <shibuuuu5@gmail.com>
Signed-off-by: sivchari <shibuuuu5@gmail.com>
@sivchari sivchari force-pushed the fix-vulnerability branch from 85819e6 to ed31e85 Compare March 23, 2025 04:26
@sivchari
Copy link
Member Author

@crenshaw-dev
codecov is failed, but it doesn't affect some quality. PTAL.

Signed-off-by: sivchari <shibuuuu5@gmail.com>
@sivchari sivchari force-pushed the fix-vulnerability branch from 3ba59b8 to 7e520a1 Compare April 13, 2025 02:18
@sivchari
Copy link
Member Author

https://pkg.go.dev/vuln/GO-2025-3547 is occurred, but this issue hasn't been resolved yet.
So vulncheck must be failed. Let's keep it until it's resolved.

@crenshaw-dev
Copy link
Member

@sivchari can you rebase

@ppapapetrou76
Copy link
Contributor

The gitops-engine repository is migrating to https://github.com/argoproj/argo-cd.

Can you please update the PR by resolving the conflicts / If it's not relevant anymore, feel free to close it
You can always re-open it when the migration is over

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

3 participants