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

Fix initilization potential deadlock #637

Merged
merged 2 commits into from
Mar 10, 2024

Conversation

Dohbedoh
Copy link

@Dohbedoh Dohbedoh commented Mar 8, 2024

Fixes #635. It should at least guarantee that loading the extension (that would call the constructor) does register the collector.

Changes proposed

  • Initialize PrometheusMetrics after jobs are loaded using @Initializer

Checklist

  • Includes tests covering the new functionality?
  • Ready for review
  • Follows CONTRIBUTING rules

Notify

@Waschndolos

@Waschndolos Waschndolos merged commit d79999a into jenkinsci:master Mar 10, 2024
25 checks passed
@Waschndolos
Copy link

Thank you for the PR. I'll test it in our Companies Test Instance tomorrow and perform a Release the upcoming days

@Waschndolos
Copy link

Appears to work as before (as expected :))

Waschndolos added a commit that referenced this pull request Mar 28, 2024
Waschndolos added a commit that referenced this pull request Mar 29, 2024
…ances (#650)

* Revert "Fixes #635: Changing creation of service classes away from explicit guice usage to avoid duplicate instantiation of DefaultPrometheusMetrics class. (#644)"

This reverts commit 9401c6e.

* Revert "Fix initilization potential deadlock (#637)"

This reverts commit d79999a.
@Dohbedoh Dohbedoh deleted the bugfix/initialization branch May 30, 2024 06:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Possible deadlock on startup
2 participants