You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by wu...@apache.org on 2022/04/18 08:05:54 UTC
[skywalking] branch master updated: Upgrade dead-link-checker to check anchors and fix CI (#8898)
This is an automated email from the ASF dual-hosted git repository.
wusheng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/skywalking.git
The following commit(s) were added to refs/heads/master by this push:
new e752b7bbe2 Upgrade dead-link-checker to check anchors and fix CI (#8898)
e752b7bbe2 is described below
commit e752b7bbe2555b4b8811a9ab80d230c1ec754c15
Author: kezhenxu94 <ke...@apache.org>
AuthorDate: Mon Apr 18 16:05:39 2022 +0800
Upgrade dead-link-checker to check anchors and fix CI (#8898)
---
.dlc.json | 3 ++-
.github/workflows/dead-link-checker.yaml | 2 +-
README.md | 2 +-
docs/en/guides/How-to-build.md | 2 +-
docs/en/guides/asf/committer.md | 4 ++--
docs/en/setup/backend/backend-alarm.md | 2 +-
docs/en/setup/backend/backend-setup.md | 2 +-
docs/en/setup/backend/grpc-security.md | 2 +-
8 files changed, 10 insertions(+), 9 deletions(-)
diff --git a/.dlc.json b/.dlc.json
index 9ee4908aa7..82e2074562 100644
--- a/.dlc.json
+++ b/.dlc.json
@@ -16,6 +16,7 @@
"fallbackRetryDelay": "1000s",
"aliveStatusCodes": [
200,
- 401
+ 401,
+ 403
]
}
diff --git a/.github/workflows/dead-link-checker.yaml b/.github/workflows/dead-link-checker.yaml
index 6090dc8df7..58f3667770 100644
--- a/.github/workflows/dead-link-checker.yaml
+++ b/.github/workflows/dead-link-checker.yaml
@@ -29,7 +29,7 @@ jobs:
timeout-minutes: 30
steps:
- uses: actions/checkout@v2
- - run: sudo npm install -g markdown-link-check@3.8.7
+ - run: sudo npm install -g markdown-link-check@3.10.0
- run: |
for file in $(find . -name "*.md"); do
markdown-link-check -c .dlc.json -q "$file"
diff --git a/README.md b/README.md
index f4e59bb827..3a236a9c8f 100644
--- a/README.md
+++ b/README.md
@@ -71,7 +71,7 @@ Please follow the [REPORTING GUIDELINES](https://www.apache.org/foundation/polic
# Contact Us
* Mail list: **dev@skywalking.apache.org**. Mail to `dev-subscribe@skywalking.apache.org`, follow the reply to subscribe the mail list.
* Send `Request to join SkyWalking slack` mail to the mail list(`dev@skywalking.apache.org`), we will invite you in.
-* Twitter, [ASFSkyWalking](https://twitter.com/ASFSkyWalking)
+* Twitter, [ASFSkyWalking](https://twitter.com/AsfSkyWalking)
* QQ Group: 901167865(Recommended), 392443393
* [bilibili B站 视频](https://space.bilibili.com/390683219)
diff --git a/docs/en/guides/How-to-build.md b/docs/en/guides/How-to-build.md
index 35c6b04729..49a7ce4716 100644
--- a/docs/en/guides/How-to-build.md
+++ b/docs/en/guides/How-to-build.md
@@ -72,7 +72,7 @@ You can build docker images of `backend` and `ui` with `Makefile` located in roo
Refer to [Build docker image](../../../docker) for more details.
## Setting up your IntelliJ IDEA
-**NOTE**: If you clone the codes from GitHub, please make sure that you have finished steps 1 to 3 in section **[Build from GitHub](#build-from-github)**. If you download the source codes from the official website of SkyWalking, please make sure that you have followed the steps in section **[Build from Apache source code release](#build-from-apache-source-code-release)**.
+**NOTE**: If you clone the codes from GitHub, please make sure that you have finished steps 1 to 3 in section **[Build from GitHub](#building-from-github)**. If you download the source codes from the official website of SkyWalking, please make sure that you have followed the steps in section **[Build from Apache source code release](#building-from-apache-source-code-release)**.
1. Import the project as a maven project.
1. Run `./mvnw compile -Dmaven.test.skip=true` to compile project and generate source codes. The reason is that we use gRPC and protobuf.
diff --git a/docs/en/guides/asf/committer.md b/docs/en/guides/asf/committer.md
index 66f6a2cdc2..55340fe2a0 100644
--- a/docs/en/guides/asf/committer.md
+++ b/docs/en/guides/asf/committer.md
@@ -105,7 +105,7 @@ The PMC member should add the new committer to the official committer list throu
### Set up the Apache ID and dev env
1. Go to [Apache Account Utility Platform](https://id.apache.org/), create your password, set up your personal mailbox (`Forwarding email address`) and GitHub account(`Your GitHub Username`). An organizational invite will be sent to you via email shortly thereafter (within 2 hours).
1. If you would like to use the `xxx@apache.org` email service, please refer to [here](https://infra.apache.org/committer-email.html). Gmail is recommended, because this forwarding mode is not easy to find in most mailbox service settings.
-1. Follow the [authorized GitHub 2FA wiki](https://help.github.com/articles/configuring-two-factor-authentication-via-a-totp-mobile-app/) to enable two-factor authorization (2FA) on [Github](http://github.com/). When you set 2FA to "off", it will be delisted by the corresponding Apache committer write permission group until you set it up again. (**NOTE: Treat your recovery codes with the same level of attention as you would your password!**)
+1. Follow the [authorized GitHub 2FA wiki](https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-totp-mobile-app) to enable two-factor authorization (2FA) on [Github](http://github.com/). When you set 2FA to "off", it will be delisted by the corresponding Apache committer write permission group until you set it up again. (**NOTE: Treat your recovery codes with [...]
1. Use [GitBox Account Linking Utility](https://gitbox.apache.org/setup/) to obtain write permission of the SkyWalking project.
1. Follow this [doc](https://github.com/apache/skywalking-website#how-to-add-a-new-committer) to update the website.
@@ -136,7 +136,7 @@ The V.P. and chair of the PMC is the secretary, who is responsible for initializ
In most cases, a new PMC member is nominated from the committer team. But it is also possible to become a PMC member directly, so long as the PMC agrees to the nomination and is confident that the candidate is ready. For instance, this can be demonstrated by the fact that he/she has been an Apache member, an Apache officer, or a PMC member of another project.
-The new PMC voting process should also follow the `[DISCUSS]`, `[VOTE]` and `[RESULT][VOTE]` procedures using a private mail list, just like the [voting process for new committers](#new-committer-nomination).
+The new PMC voting process should also follow the `[DISCUSS]`, `[VOTE]` and `[RESULT][VOTE]` procedures using a private mail list, just like the [voting process for new committers](#nominate-new-committer).
Before sending the invitation, the PMC [must also send a NOTICE mail to the Apache board](http://www.apache.org/dev/pmc.html#newpmc).
```
To: board@apache.org
diff --git a/docs/en/setup/backend/backend-alarm.md b/docs/en/setup/backend/backend-alarm.md
index c19bf94d08..2a64e2674b 100644
--- a/docs/en/setup/backend/backend-alarm.md
+++ b/docs/en/setup/backend/backend-alarm.md
@@ -3,7 +3,7 @@ Alarm core is driven by a collection of rules, which are defined in `config/alar
There are three parts in alarm rule definition.
1. [Alarm rules](#rules). They define how metrics alarm should be triggered and what conditions should be considered.
1. [Webhooks](#webhook). The list of web service endpoints, which should be called after the alarm is triggered.
-1. [gRPCHook](#gRPCHook). The host and port of the remote gRPC method, which should be called after the alarm is triggered.
+1. [gRPCHook](#grpchook). The host and port of the remote gRPC method, which should be called after the alarm is triggered.
## Entity name
Defines the relation between scope and entity name.
diff --git a/docs/en/setup/backend/backend-setup.md b/docs/en/setup/backend/backend-setup.md
index 6e1d2a35f2..3fcebdb756 100755
--- a/docs/en/setup/backend/backend-setup.md
+++ b/docs/en/setup/backend/backend-setup.md
@@ -19,7 +19,7 @@ Requirement: **JDK8 to JDK17 are tested**. Other versions are not tested and may
Before you start, you should know that the main purpose of quickstart is to help you obtain a basic configuration for previews/demo. Performance and long-term running are not our goals.
-For production/QA/tests environments, see [Backend and UI deployment documents](#deploy-backend-and-ui).
+For production/QA/tests environments, see [Backend and UI deployment documents](ui-setup.md).
You can use `bin/startup.sh` (or cmd) to start up the backend and UI with their default settings, set out as follows:
diff --git a/docs/en/setup/backend/grpc-security.md b/docs/en/setup/backend/grpc-security.md
index 5c4716e0e9..ace9488337 100644
--- a/docs/en/setup/backend/grpc-security.md
+++ b/docs/en/setup/backend/grpc-security.md
@@ -31,7 +31,7 @@ We need the following files:
By default, the communication between OAP nodes and the communication between receiver and probe share the same gRPC server. That means once you enabling SSL for receivers and probes, the OAP nodes will enable it too.
-**NOTE**: SkyWalking **does not** support to enable mTLS on `OAP server nodes communication`. That means you have to enable `receiver-sharing-server` for enabling mTLS on communication between probes ang OAP servers. More details see [Enable mTLS mode on gRPC receiver](#Enable_mTLS_mode_on_gRPC_receiver).
+**NOTE**: SkyWalking **does not** support to enable mTLS on `OAP server nodes communication`. That means you have to enable `receiver-sharing-server` for enabling mTLS on communication between probes ang OAP servers. More details see [Enable mTLS mode on gRPC receiver](#enable-mtls-mode-on-grpc-receiver).
You can enable gRPC SSL by adding the following lines to `application.yml/core/default`.