Skip to content

Conversation

jake-ciolek
Copy link
Contributor

Add a small guard that recovers and logs the panic and stack trace.

Cover both the api-server and applicationset-controller webhooks.

Add a small guard that recovers and logs the panic and stack trace.

Cover both the api-server and applicationset-controller webhooks.

Signed-off-by: Jakub Ciolek <[email protected]>
@jake-ciolek jake-ciolek requested a review from a team as a code owner October 6, 2025 10:19
Copy link

bunnyshell bot commented Oct 6, 2025

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

  • 🚀 /bns:deploy to deploy the environment

Copy link

codecov bot commented Oct 6, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.83%. Comparing base (b553cc5) to head (56dfae8).
⚠️ Report is 26 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #24862      +/-   ##
==========================================
+ Coverage   60.78%   60.83%   +0.05%     
==========================================
  Files         404      351      -53     
  Lines       66232    60439    -5793     
==========================================
- Hits        40256    36766    -3490     
+ Misses      22730    20759    -1971     
+ Partials     3246     2914     -332     

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

@rumstead
Copy link
Member

rumstead commented Oct 6, 2025

@jake-ciolek are you seeing panics? if so, what is causing the webhook handlers to panic?

@jake-ciolek
Copy link
Contributor Author

jake-ciolek commented Oct 6, 2025

@rumstead This is a follow up after those dropped last week:

GHSA-gpx4-37g2-c8pv
GHSA-f9gq-prrc-hrhc
GHSA-gpx4-37g2-c8pv

It prevents several classes of panics, shall they ever occur again (either through current or future weakness), from causing server restarts.

cc @crenshaw-dev

@rumstead
Copy link
Member

rumstead commented Oct 6, 2025

@rumstead This is a follow up after those dropped last week:

GHSA-gpx4-37g2-c8pv GHSA-f9gq-prrc-hrhc GHSA-gpx4-37g2-c8pv

It prevents several classes of panics, shall they ever occur again (either through current or future weakness), from causing server restarts.

cc @crenshaw-dev

got it, thanks!

This makes the signature more explicit.

Signed-off-by: Jakub Ciolek <[email protected]>
Copy link
Member

@crenshaw-dev crenshaw-dev left a comment

Choose a reason for hiding this comment

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

Thank you!

@crenshaw-dev crenshaw-dev added cherry-pick/3.0 Candidate for cherry picking into the 3.0 release branch cherry-pick/3.1 Candidate for cherry picking into the 3.1 release branch cherry-pick/3.2 Candidate for cherry picking into the 3.2 release branch cherry-pick/2.14 Candidate for cherry picking into the 2.14 release branch labels Oct 9, 2025
@crenshaw-dev crenshaw-dev merged commit bf0661e into argoproj:master Oct 9, 2025
37 checks passed
argo-cd-cherry-pick-bot bot pushed a commit that referenced this pull request Oct 9, 2025
argo-cd-cherry-pick-bot bot pushed a commit that referenced this pull request Oct 9, 2025
argo-cd-cherry-pick-bot bot pushed a commit that referenced this pull request Oct 9, 2025
@argo-cd-cherry-pick-bot
Copy link

🍒 Cherry-pick PR created for 3.2: #24912

@argo-cd-cherry-pick-bot
Copy link

🍒 Cherry-pick PR created for 3.0: #24913

@argo-cd-cherry-pick-bot
Copy link

🍒 Cherry-pick PR created for 3.1: #24914

@argo-cd-cherry-pick-bot
Copy link

❌ Cherry-pick failed for 2.14. Please check the workflow logs for details.

@crenshaw-dev
Copy link
Member

@jake-ciolek do you have time to manually pick 2.14?

@jake-ciolek
Copy link
Contributor Author

@crenshaw-dev Raised a pick for 2.14 here. Cheers.

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

Labels

cherry-pick/2.14 Candidate for cherry picking into the 2.14 release branch cherry-pick/3.0 Candidate for cherry picking into the 3.0 release branch cherry-pick/3.1 Candidate for cherry picking into the 3.1 release branch cherry-pick/3.2 Candidate for cherry picking into the 3.2 release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants