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: SPI of the ThreadPoolMonitor #1518

Merged
merged 1 commit into from
Nov 24, 2023

Conversation

Dawanyezhi
Copy link
Contributor

Changes proposed in this pull request:
Fix the problem that a custom implementation class of ThreadPoolMonitor cannot be introduced through the SPI mechanism in the ReportingEventExecutor class when the project is started.

…onitor cannot be introduced through the SPI mechanism in the ReportingEventExecutor class when the project is started.
Copy link

codecov bot commented Nov 22, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (265bf6e) 34.23% compared to head (db273b0) 34.33%.
Report is 5 commits behind head on develop.

Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #1518      +/-   ##
=============================================
+ Coverage      34.23%   34.33%   +0.10%     
- Complexity       847      849       +2     
=============================================
  Files            262      262              
  Lines           5953     5953              
  Branches         560      560              
=============================================
+ Hits            2038     2044       +6     
+ Misses          3722     3717       -5     
+ Partials         193      192       -1     

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

@magestacks magestacks merged commit f49fd99 into opengoofy:develop Nov 24, 2023
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants