From c10761ec9a8983de1b373a70051f56369da8f636 Mon Sep 17 00:00:00 2001 From: Duansg Date: Fri, 6 Feb 2026 20:50:59 +0800 Subject: [PATCH] [improve] improved version validation documentation content (#4013) --- home/blog/2023-05-11-greptimedb-store.md | 10 +++++----- .../community/code-style-and-quality-guide.md | 15 +++++++-------- home/docs/community/how-to-verify.md | 8 ++++---- home/docs/help/consul_sd.md | 2 +- .../2023-05-11-greptimedb-store.md | 10 +++++----- .../community/code-style-and-quality-guide.md | 5 ++--- .../current/community/how-to-verify.md | 12 ++++++------ .../current/help/consul_sd.md | 2 +- .../community/code-style-and-quality-guide.md | 5 ++--- .../community/code-style-and-quality-guide.md | 5 ++--- .../version-1.7.x/help/consul_sd.md | 2 +- .../community/code-style-and-quality-guide.md | 15 +++++++-------- .../community/code-style-and-quality-guide.md | 15 +++++++-------- .../version-1.7.x/help/consul_sd.md | 2 +- script/ci/link_check.json | 3 ++- 15 files changed, 53 insertions(+), 58 deletions(-) diff --git a/home/blog/2023-05-11-greptimedb-store.md b/home/blog/2023-05-11-greptimedb-store.md index 43bef637e8..bab74edca4 100644 --- a/home/blog/2023-05-11-greptimedb-store.md +++ b/home/blog/2023-05-11-greptimedb-store.md @@ -1,8 +1,8 @@ --- -title: GreptimeDB & HertzBeat, using the open source temporal database GreptimeDB to store metrics for the open source real-time monitoring HertzBeat -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: GreptimeDB & HertzBeat, using the open source temporal database GreptimeDB to store metrics for the open source real-time monitoring HertzBeat +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [open source monitoring system, open source temporal database, HertzBeat, GreptimeDB] --- @@ -18,7 +18,7 @@ keywords: [open source monitoring system, open source temporal database, HertzBe - Efficient storage and computation, with object storage and high data compression rate to achieve ultra-low storage costs. Built-in data analytics solution to avoid replicating data to external data warehouses. - Distributed, Highly Reliable & Highly Available, easily scale each module independently with decoupled cloud-native architecture. Ensure data reliability and availability with configurable replicas and automated failover mechanisms. -Cloud: **[GreptimePlay](https://greptime.com/playground)** +Cloud: **[GreptimePlay](https://greptime.com/product/cloud)** ### What is HertzBeat? diff --git a/home/docs/community/code-style-and-quality-guide.md b/home/docs/community/code-style-and-quality-guide.md index f1a489a92f..c9fa91e1c0 100644 --- a/home/docs/community/code-style-and-quality-guide.md +++ b/home/docs/community/code-style-and-quality-guide.md @@ -27,7 +27,7 @@ limitations under the License. - After creating a new `PR`, you need to associate the existing corresponding `ISSUE` at the Github Development button on the `PR` page (if there is no corresponding ISSUE, it is recommended to create a new corresponding ISSUE). - - Title naming format + - Title naming format `[feature/bugfix/doc/improve/refactor/bug/cleanup] title` 2. Description @@ -35,7 +35,7 @@ limitations under the License. - Please fill in the `PR` template to describe the contribution. So that the reviewer can understand the problem and solution from the description, rather than just from the code. - Check the CheckList 3. It's recommended that `PR` should be arranged changes such as `cleanup`, `Refactor`, `improve`, and `feature` into separated `PRs`/`Commits`. -4. Commit message(English, lowercase, no special characters) +4. Commit message(English, lowercase, no special characters) The commit of messages should follow a pattern similar to the `[feature/bugfix/doc/improve/refactor/bug/cleanup] title` ## 2 Code Checkstyle @@ -133,8 +133,8 @@ Error code description: ``` 2. Pinyin abbreviations are prohibited for variables (excluding nouns such as place names), such as chengdu. -3. It is recommended to end variable names with a `type`. - For variables of type `Collection/List`, take `xxxx` (plural representing multiple elements) or end with `xxxList` (specific type). +3. It is recommended to end variable names with a `type`. + For variables of type `Collection/List`, take `xxxx` (plural representing multiple elements) or end with `xxxList` (specific type). For variables of type `map`, describe the `key` and `value` clearly: ```java @@ -142,7 +142,7 @@ Error code description: Map userIdNameMap; ``` -4. That can intuitively know the type and meaning of the variable through its name. +4. That can intuitively know the type and meaning of the variable through its name. Method names should start with a verb first as follows: ```java @@ -320,7 +320,7 @@ to reduce code line depth and improve readability like follows: ...... } } - + ``` - Positive demo: @@ -630,7 +630,7 @@ public void process(String input) { // ignored declaration lines. List`` userList = getUsersByBatch(1000); if (LOG.isDebugEnabled()) { - LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); + LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); } ``` @@ -644,6 +644,5 @@ public void process(String input) { - [https://site.mockito.org/](https://site.mockito.org/) - [https://alibaba.github.io/p3c/](https://alibaba.github.io/p3c/) -- [https://rules.sonarsource.com/java/](https://rules.sonarsource.com/java/) - [https://junit.org/junit5/](https://junit.org/junit5/) - [https://streampark.apache.org/](https://streampark.apache.org/) diff --git a/home/docs/community/how-to-verify.md b/home/docs/community/how-to-verify.md index 91aa60cdb7..4bd9c90a08 100644 --- a/home/docs/community/how-to-verify.md +++ b/home/docs/community/how-to-verify.md @@ -91,10 +91,10 @@ check result > If something like the following appears, it means the signature is correct. Keyword: **`Good signature`** ```shell -apache-hertzbeat-xxx-src.tar.gz +apache-hertzbeat-${release_version}-src.tar.gz gpg: Signature made XXXX gpg: using RSA key XXXXX -gpg: Good signature from "xxx @apache.org>" +gpg: Good signature from "XXX " ``` #### 2.3 Check sha512 hash @@ -125,10 +125,10 @@ check as follows: > If the binary/web-binary package is uploaded, check the binary package. -Unzip `apache-hertzbeat-`release_version`-src.tar.gz` +Unzip `apache-hertzbeat-${release_version}-src.tar.gz` ```shell -cd apache-hertzbeat-`release_version`-src +cd apache-hertzbeat-${release_version}-src ``` compile the source code: [Build HertzBeat Binary Package](https://hertzbeat.apache.org/docs/community/development/#build-hertzbeat-binary-package) diff --git a/home/docs/help/consul_sd.md b/home/docs/help/consul_sd.md index 0b499eecb1..248e24a486 100644 --- a/home/docs/help/consul_sd.md +++ b/home/docs/help/consul_sd.md @@ -15,7 +15,7 @@ Consul Service Discovery allows HertzBeat to connect to your Consul server and a #### Deploy Consul Server -1. Deploy Consul server according to [Consul official documentation](https://www.consul.io/docs/install). +1. Deploy Consul server according to [Consul official documentation](https://developer.hashicorp.com/consul/docs/fundamentals/install). 2. Ensure Consul server is accessible from HertzBeat. 3. Verify that you can access Consul UI at `http://your-consul-server:8500/ui/` 4. Ensure the Consul HTTP API is accessible (default port: 8500) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-05-11-greptimedb-store.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-05-11-greptimedb-store.md index d0a2f85989..b99a535f1a 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-05-11-greptimedb-store.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-05-11-greptimedb-store.md @@ -1,8 +1,8 @@ --- -title: GreptimeDB & HertzBeat, 使用开源时序数据库 GreptimeDB 存储开源实时监控 HertzBeat 的度量数据 -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: GreptimeDB & HertzBeat, 使用开源时序数据库 GreptimeDB 存储开源实时监控 HertzBeat 的度量数据 +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [开源监控系统, 开源时序数据库, HertzBeat, GreptimeDB] --- @@ -18,7 +18,7 @@ keywords: [开源监控系统, 开源时序数据库, HertzBeat, GreptimeDB] - 高效存储与计算,通过对象存储和高数据压缩率实现超低的存储成本。内置数据分析解决方案,避免将数据复制到外部数据仓库。 - 分布式、高可靠与高可用,通过解耦的云原生架构,轻松独立地扩展每个模块。通过可配置的副本和自动的故障转移机制,确保数据的可靠性和可用性。 -Cloud: **[GreptimePlay](https://greptime.com/playground)** +Cloud: **[GreptimePlay](https://greptime.com/product/cloud)** ### 什么是 HertzBeat diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/code-style-and-quality-guide.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/code-style-and-quality-guide.md index 1c67ee891f..2550e0e822 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/code-style-and-quality-guide.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/code-style-and-quality-guide.md @@ -35,7 +35,7 @@ limitations under the License. - 新建 `PR` 时请仔细描述此贡献,描述文档和代码同样重要。审阅者可以从描述中,而不仅仅是从代码中,了解问题和解决方案。 - 勾选是否完成了对应的 Checklist。 3. 建议一次 `PR` 只包含一个功能/一种修复/一类改进/一种重构/一次清理/一类文档等 -4. 提交消息(英文,小写,无特殊字符) +4. 提交消息(英文,小写,无特殊字符) 消息的提交应遵循与 `PR` 类似的模式:`[feature/bugfix/doc/improve/refactor/bug/cleanup] title` ## 2 代码检查样式 @@ -631,7 +631,7 @@ public void process(String input) { // 忽略声明行。 List`` userList = getUsersByBatch(1000); if (LOG.isDebugEnabled()) { - LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); + LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); } ``` @@ -645,6 +645,5 @@ public void process(String input) { - [https://site.mockito.org/](https://site.mockito.org/) - [https://alibaba.github.io/p3c/](https://alibaba.github.io/p3c/) -- [https://rules.sonarsource.com/java/](https://rules.sonarsource.com/java/) - [https://junit.org/junit5/](https://junit.org/junit5/) - [https://streampark.apache.org/](https://streampark.apache.org/) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/how-to-verify.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/how-to-verify.md index ca56885448..f1f82bafb0 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/how-to-verify.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/how-to-verify.md @@ -86,10 +86,10 @@ for i in *.tar.gz; do echo $i; gpg --verify $i.asc $i ; done > 出现类似以下内容则说明签名正确,关键字:**`Good signature`** ```shell -apache-hertzbeat-xxx-incubating-src.tar.gz +apache-hertzbeat-${release_version}-src.tar.gz gpg: Signature made XXXX gpg: using RSA key XXXXX -gpg: Good signature from "xxx @apache.org>" +gpg: Good signature from "XXX " ``` #### 2.3 检查sha512哈希 @@ -102,10 +102,10 @@ for i in *.tar.gz; do echo $i; sha512sum --check $i.sha512; done #### 2.4 检查二进制包 -解压缩 `apache-hertzbeat-${release.version}-incubating-bin.tar.gz` +解压缩 `apache-hertzbeat-${release_version}-bin.tar.gz` ```shell -tar -xzvf apache-hertzbeat-${release.version}-incubating-bin.tar.gz +tar -xzvf apache-hertzbeat-${release_version}-bin.tar.gz ``` 进行如下检查: @@ -123,10 +123,10 @@ tar -xzvf apache-hertzbeat-${release.version}-incubating-bin.tar.gz #### 2.5. 源码编译验证 -解压缩 `apache-hertzbeat-`release_version`-incubating-src.tar.gz` +解压缩 `apache-hertzbeat-${release_version}-src.tar.gz` ```shell -cd apache-hertzbeat-`release_version`-incubating-src +cd apache-hertzbeat-${release_version}-src ``` 编译源码: [https://hertzbeat.apache.org/docs/community/development/#build-hertzbeat-binary-package](https://hertzbeat.apache.org/docs/community/development/#build-hertzbeat-binary-package) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/consul_sd.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/consul_sd.md index 737ef71d21..dc4d3a3ce9 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/consul_sd.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/consul_sd.md @@ -15,7 +15,7 @@ Consul 服务发现允许 HertzBeat 连接到您的 Consul 服务器并自动发 #### 部署 Consul 服务器 -1. 根据 [Consul 官方文档](https://www.consul.io/docs/install)部署 Consul 服务器。 +1. 根据 [Consul 官方文档](https://developer.hashicorp.com/consul/docs/fundamentals/install)部署 Consul 服务器。 2. 确保 Consul 服务器可从 HertzBeat 访问。 3. 验证您可以访问 Consul UI:`http://your-consul-server:8500/ui/` 4. 确保 Consul HTTP API 可访问(默认端口:8500) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/community/code-style-and-quality-guide.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/community/code-style-and-quality-guide.md index dcd4abf6fe..d3d0d28ffd 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/community/code-style-and-quality-guide.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/community/code-style-and-quality-guide.md @@ -35,7 +35,7 @@ limitations under the License. - 新建 `PR` 时请仔细描述此贡献,描述文档和代码同样重要。审阅者可以从描述中,而不仅仅是从代码中,了解问题和解决方案。 - 勾选是否完成了对应的 Checklist。 3. 建议一次 `PR` 只包含一个功能/一种修复/一类改进/一种重构/一次清理/一类文档等 -4. 提交消息(英文,小写,无特殊字符) +4. 提交消息(英文,小写,无特殊字符) 消息的提交应遵循与 `PR` 类似的模式:`[feature/bugfix/doc/improve/refactor/bug/cleanup] title` ## 2 代码检查样式 @@ -631,7 +631,7 @@ public void process(String input) { // 忽略声明行。 List`` userList = getUsersByBatch(1000); if (LOG.isDebugEnabled()) { - LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); + LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); } ``` @@ -645,6 +645,5 @@ public void process(String input) { - [https://site.mockito.org/](https://site.mockito.org/) - [https://alibaba.github.io/p3c/](https://alibaba.github.io/p3c/) -- [https://rules.sonarsource.com/java/](https://rules.sonarsource.com/java/) - [https://junit.org/junit5/](https://junit.org/junit5/) - [https://streampark.apache.org/](https://streampark.apache.org/) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/community/code-style-and-quality-guide.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/community/code-style-and-quality-guide.md index 1c67ee891f..2550e0e822 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/community/code-style-and-quality-guide.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/community/code-style-and-quality-guide.md @@ -35,7 +35,7 @@ limitations under the License. - 新建 `PR` 时请仔细描述此贡献,描述文档和代码同样重要。审阅者可以从描述中,而不仅仅是从代码中,了解问题和解决方案。 - 勾选是否完成了对应的 Checklist。 3. 建议一次 `PR` 只包含一个功能/一种修复/一类改进/一种重构/一次清理/一类文档等 -4. 提交消息(英文,小写,无特殊字符) +4. 提交消息(英文,小写,无特殊字符) 消息的提交应遵循与 `PR` 类似的模式:`[feature/bugfix/doc/improve/refactor/bug/cleanup] title` ## 2 代码检查样式 @@ -631,7 +631,7 @@ public void process(String input) { // 忽略声明行。 List`` userList = getUsersByBatch(1000); if (LOG.isDebugEnabled()) { - LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); + LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); } ``` @@ -645,6 +645,5 @@ public void process(String input) { - [https://site.mockito.org/](https://site.mockito.org/) - [https://alibaba.github.io/p3c/](https://alibaba.github.io/p3c/) -- [https://rules.sonarsource.com/java/](https://rules.sonarsource.com/java/) - [https://junit.org/junit5/](https://junit.org/junit5/) - [https://streampark.apache.org/](https://streampark.apache.org/) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/help/consul_sd.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/help/consul_sd.md index 737ef71d21..dc4d3a3ce9 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/help/consul_sd.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/help/consul_sd.md @@ -15,7 +15,7 @@ Consul 服务发现允许 HertzBeat 连接到您的 Consul 服务器并自动发 #### 部署 Consul 服务器 -1. 根据 [Consul 官方文档](https://www.consul.io/docs/install)部署 Consul 服务器。 +1. 根据 [Consul 官方文档](https://developer.hashicorp.com/consul/docs/fundamentals/install)部署 Consul 服务器。 2. 确保 Consul 服务器可从 HertzBeat 访问。 3. 验证您可以访问 Consul UI:`http://your-consul-server:8500/ui/` 4. 确保 Consul HTTP API 可访问(默认端口:8500) diff --git a/home/versioned_docs/version-1.6.x/community/code-style-and-quality-guide.md b/home/versioned_docs/version-1.6.x/community/code-style-and-quality-guide.md index 14e99295f8..8d701b64b3 100644 --- a/home/versioned_docs/version-1.6.x/community/code-style-and-quality-guide.md +++ b/home/versioned_docs/version-1.6.x/community/code-style-and-quality-guide.md @@ -27,7 +27,7 @@ limitations under the License. - After creating a new `PR`, you need to associate the existing corresponding `ISSUE` at the Github Development button on the `PR` page (if there is no corresponding ISSUE, it is recommended to create a new corresponding ISSUE). - - Title naming format + - Title naming format `[feature/bugfix/doc/improve/refactor/bug/cleanup] title` 2. Description @@ -35,7 +35,7 @@ limitations under the License. - Please fill in the `PR` template to describe the contribution. So that the reviewer can understand the problem and solution from the description, rather than just from the code. - Check the CheckList 3. It's recommended that `PR` should be arranged changes such as `cleanup`, `Refactor`, `improve`, and `feature` into separated `PRs`/`Commits`. -4. Commit message(English, lowercase, no special characters) +4. Commit message(English, lowercase, no special characters) The commit of messages should follow a pattern similar to the `[feature/bugfix/doc/improve/refactor/bug/cleanup] title` ## 2 Code Checkstyle @@ -133,8 +133,8 @@ Error code description: ``` 2. Pinyin abbreviations are prohibited for variables (excluding nouns such as place names), such as chengdu. -3. It is recommended to end variable names with a `type`. - For variables of type `Collection/List`, take `xxxx` (plural representing multiple elements) or end with `xxxList` (specific type). +3. It is recommended to end variable names with a `type`. + For variables of type `Collection/List`, take `xxxx` (plural representing multiple elements) or end with `xxxList` (specific type). For variables of type `map`, describe the `key` and `value` clearly: ```java @@ -142,7 +142,7 @@ Error code description: Map userIdNameMap; ``` -4. That can intuitively know the type and meaning of the variable through its name. +4. That can intuitively know the type and meaning of the variable through its name. Method names should start with a verb first as follows: ```java @@ -320,7 +320,7 @@ to reduce code line depth and improve readability like follows: ...... } } - + ``` - Positive demo: @@ -630,7 +630,7 @@ public void process(String input) { // ignored declaration lines. List`` userList = getUsersByBatch(1000); if (LOG.isDebugEnabled()) { - LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); + LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); } ``` @@ -644,6 +644,5 @@ public void process(String input) { - [https://site.mockito.org/](https://site.mockito.org/) - [https://alibaba.github.io/p3c/](https://alibaba.github.io/p3c/) -- [https://rules.sonarsource.com/java/](https://rules.sonarsource.com/java/) - [https://junit.org/junit5/](https://junit.org/junit5/) - [https://streampark.apache.org/](https://streampark.apache.org/) diff --git a/home/versioned_docs/version-1.7.x/community/code-style-and-quality-guide.md b/home/versioned_docs/version-1.7.x/community/code-style-and-quality-guide.md index f1a489a92f..c9fa91e1c0 100644 --- a/home/versioned_docs/version-1.7.x/community/code-style-and-quality-guide.md +++ b/home/versioned_docs/version-1.7.x/community/code-style-and-quality-guide.md @@ -27,7 +27,7 @@ limitations under the License. - After creating a new `PR`, you need to associate the existing corresponding `ISSUE` at the Github Development button on the `PR` page (if there is no corresponding ISSUE, it is recommended to create a new corresponding ISSUE). - - Title naming format + - Title naming format `[feature/bugfix/doc/improve/refactor/bug/cleanup] title` 2. Description @@ -35,7 +35,7 @@ limitations under the License. - Please fill in the `PR` template to describe the contribution. So that the reviewer can understand the problem and solution from the description, rather than just from the code. - Check the CheckList 3. It's recommended that `PR` should be arranged changes such as `cleanup`, `Refactor`, `improve`, and `feature` into separated `PRs`/`Commits`. -4. Commit message(English, lowercase, no special characters) +4. Commit message(English, lowercase, no special characters) The commit of messages should follow a pattern similar to the `[feature/bugfix/doc/improve/refactor/bug/cleanup] title` ## 2 Code Checkstyle @@ -133,8 +133,8 @@ Error code description: ``` 2. Pinyin abbreviations are prohibited for variables (excluding nouns such as place names), such as chengdu. -3. It is recommended to end variable names with a `type`. - For variables of type `Collection/List`, take `xxxx` (plural representing multiple elements) or end with `xxxList` (specific type). +3. It is recommended to end variable names with a `type`. + For variables of type `Collection/List`, take `xxxx` (plural representing multiple elements) or end with `xxxList` (specific type). For variables of type `map`, describe the `key` and `value` clearly: ```java @@ -142,7 +142,7 @@ Error code description: Map userIdNameMap; ``` -4. That can intuitively know the type and meaning of the variable through its name. +4. That can intuitively know the type and meaning of the variable through its name. Method names should start with a verb first as follows: ```java @@ -320,7 +320,7 @@ to reduce code line depth and improve readability like follows: ...... } } - + ``` - Positive demo: @@ -630,7 +630,7 @@ public void process(String input) { // ignored declaration lines. List`` userList = getUsersByBatch(1000); if (LOG.isDebugEnabled()) { - LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); + LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); } ``` @@ -644,6 +644,5 @@ public void process(String input) { - [https://site.mockito.org/](https://site.mockito.org/) - [https://alibaba.github.io/p3c/](https://alibaba.github.io/p3c/) -- [https://rules.sonarsource.com/java/](https://rules.sonarsource.com/java/) - [https://junit.org/junit5/](https://junit.org/junit5/) - [https://streampark.apache.org/](https://streampark.apache.org/) diff --git a/home/versioned_docs/version-1.7.x/help/consul_sd.md b/home/versioned_docs/version-1.7.x/help/consul_sd.md index 0b499eecb1..248e24a486 100644 --- a/home/versioned_docs/version-1.7.x/help/consul_sd.md +++ b/home/versioned_docs/version-1.7.x/help/consul_sd.md @@ -15,7 +15,7 @@ Consul Service Discovery allows HertzBeat to connect to your Consul server and a #### Deploy Consul Server -1. Deploy Consul server according to [Consul official documentation](https://www.consul.io/docs/install). +1. Deploy Consul server according to [Consul official documentation](https://developer.hashicorp.com/consul/docs/fundamentals/install). 2. Ensure Consul server is accessible from HertzBeat. 3. Verify that you can access Consul UI at `http://your-consul-server:8500/ui/` 4. Ensure the Consul HTTP API is accessible (default port: 8500) diff --git a/script/ci/link_check.json b/script/ci/link_check.json index 5dce366d4d..deae2430c1 100644 --- a/script/ci/link_check.json +++ b/script/ci/link_check.json @@ -19,6 +19,7 @@ 200, 400, 401, - 403 + 403, + 429 ] }