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

[ISSUE #12946] Improve Clarity and Log Level of Shutdown Message in HttpClientBeanHolder #12950

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

SoilChang
Copy link

Please do not create a Pull Request without creating an issue first.

What is the purpose of the change

This change improves the clarity and professionalism of logging messages across various components. Specifically, it updates log messages related to resource destruction processes to ensure consistent grammar, clarity, and message intent.

Brief changelog

Updated log messages in ConfigHttpClientManager to clarify resource destruction stages.
Updated log messages in NamingHttpClientManager for better grammar and meaning.
Refined log messages in ThreadPoolManager to ensure clarity about the shutdown process.
Improved log messages in HttpClientBeanHolder to clearly describe the start and completion of HTTP client destruction.
Enhanced logging in NotifyCenter to make resource cleanup messages more professional and meaningful.
Updated HttpClientManager in the config and naming modules to use consistent and clear log messages during the destruction of HTTP clients.

Verifying this change

visual verifying

Follow this checklist to help us incorporate your contribution quickly and easily:

  • Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
  • Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
  • Run mvn -B clean package apache-rat:check findbugs:findbugs -Dmaven.test.skip=true to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link

Thanks for your this PR. 🙏
Please check again for your PR changes whether contains any usage/api/configuration change such as Add new API , Add new configuration, Change default value of configuration.
If so, please add or update documents(markdown type) in docs/next/ for repository nacos-group/nacos-group.github.io


感谢您提交的PR。 🙏
请再次查看您的PR内容,确认是否包含任何使用方式/API/配置参数的变更,如:新增API新增配置参数修改默认配置等操作。
如果是,请确保在提交之前,在仓库nacos-group/nacos-group.github.io中的docs/next/目录下添加或更新文档(markdown格式)。

@codecov-commenter
Copy link

Codecov Report

Attention: Patch coverage is 92.85714% with 1 line in your changes missing coverage. Please review.

Project coverage is 72.43%. Comparing base (08fac16) to head (2abb6f0).
Report is 1 commits behind head on develop.

Files with missing lines Patch % Lines
...m/alibaba/nacos/naming/misc/HttpClientManager.java 50.00% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@              Coverage Diff              @@
##             develop   #12950      +/-   ##
=============================================
+ Coverage      72.32%   72.43%   +0.11%     
- Complexity      9959     9962       +3     
=============================================
  Files           1308     1307       -1     
  Lines          41830    41783      -47     
  Branches        4403     4389      -14     
=============================================
+ Hits           30254    30266      +12     
+ Misses          9462     9402      -60     
- Partials        2114     2115       +1     
Files with missing lines Coverage Δ
...os/client/config/impl/ConfigHttpClientManager.java 54.54% <100.00%> (ø)
...nt/naming/remote/http/NamingHttpClientManager.java 95.23% <100.00%> (ø)
...ibaba/nacos/common/executor/ThreadPoolManager.java 100.00% <100.00%> (ø)
...libaba/nacos/common/http/HttpClientBeanHolder.java 79.31% <100.00%> (ø)
.../com/alibaba/nacos/common/notify/NotifyCenter.java 90.15% <100.00%> (ø)
...onfig/server/service/notify/HttpClientManager.java 81.48% <100.00%> (ø)
...m/alibaba/nacos/naming/misc/HttpClientManager.java 50.00% <50.00%> (ø)

... and 13 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 08fac16...2abb6f0. Read the comment docs.

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.

4 participants