Skip to content

Commit 3a86bb7

Browse files
authored
chore: fix some words (#956)
* fix * fix * fix
1 parent 5ff7617 commit 3a86bb7

File tree

12 files changed

+31
-31
lines changed

12 files changed

+31
-31
lines changed

docs/deployment/diagnose_tool.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -110,11 +110,11 @@ NETWORK STATISTICS(alice-bob):
110110

111111
- CRD Config Check: 检查配置的 ClusterDomainRoute 是否有效,若为 FAIL,则说明 CDR 配置有误或节点本身网络不通。
112112
- NETWORK STATISTICS(alice-bob):Alice 到 Bob 的请求链路网络指标,包含:
113-
- BANDWIDTH:网络带宽指标,默认阈值为 10Mbits/sec,可通过配置 `--speed_thres \<theshold\>` 调整,当带宽检测值(DETECTED VALUE)小于10Mbits/sec 时,结果为 WARNING;
113+
- BANDWIDTH:网络带宽指标,默认阈值为 10Mbits/sec,可通过配置 `--speed_threshold` 调整,当带宽检测值(DETECTED VALUE)小于10Mbits/sec 时,结果为 WARNING;
114114
- CONNECTION:联通性,检测 Kuscia Job 的服务网络联通;
115115
- PROXY_BUFFER:网关缓冲,结果为FAIL时表示网关存在缓冲,需要联系机构网关关闭网关缓冲;
116-
- REQUEST_BODY_SIZE:网关请求包体限制,默认阈值为 1MB,可通过配置 `--size_thres \<threshold\>` 调整,当包体限制检测值(DETECTED VALUE)小于 1MB 时,结果为 WARNING;
117-
- RTT:传输延迟,默认阈值为 50ms,可通过配置 `--rtt_thres \<threshold\>`调整,当传输延迟检测值(DETECTED VALUE)大于 50ms 时,结果为 WARNING。
116+
- REQUEST_BODY_SIZE:网关请求包体限制,默认阈值为 1MB,可通过配置 `--size_threshold` 调整,当包体限制检测值(DETECTED VALUE)小于 1MB 时,结果为 WARNING;
117+
- RTT:传输延迟,默认阈值为 50ms,可通过配置 `--rtt_threshold`调整,当传输延迟检测值(DETECTED VALUE)大于 50ms 时,结果为 WARNING。
118118
- NETWORK STATISTICS(bob-alice): Bob 到 Alice 的请求链路网络指标。
119119

120120
### 其他说明

docs/locales/en/LC_MESSAGES/deployment/diagnose_tool.po

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -105,9 +105,9 @@ msgstr "NETWORK STATISTICS(alice-bob): Network metrics for the request link from
105105

106106
#: ../../deployment/diagnose_tool.md:111
107107
msgid ""
108-
"BANDWIDTH:网络带宽指标,默认阈值为 10Mbits/sec,可通过配置 `--speed_thres \\<theshold\\>` "
108+
"BANDWIDTH:网络带宽指标,默认阈值为 10Mbits/sec,可通过配置 `--speed_threshold` "
109109
"调整,当带宽检测值(DETECTED VALUE)小于10Mbits/sec 时,结果为 WARNING;"
110-
msgstr "BANDWIDTH: Network bandwidth metric. The default threshold is 10Mbits/sec. You can adjust it using the `--speed_thres <theshold>` option. If the detected value is less than 10Mbits/sec, the result will be WARNING;"
110+
msgstr "BANDWIDTH: Network bandwidth metric. The default threshold is 10Mbits/sec. You can adjust it using the `--speed_threshold` option. If the detected value is less than 10Mbits/sec, the result will be WARNING;"
111111

112112
#: ../../deployment/diagnose_tool.md:112
113113
msgid "CONNECTION:联通性,检测 Kuscia Job 的服务网络联通;"
@@ -119,15 +119,15 @@ msgstr "PROXY_BUFFER: Gateway buffer. A FAIL result indicates that the gateway b
119119

120120
#: ../../deployment/diagnose_tool.md:114
121121
msgid ""
122-
"REQUEST_BODY_SIZE:网关请求包体限制,默认阈值为 1MB,可通过配置 `--size_thres \\<threshold\\>`"
122+
"REQUEST_BODY_SIZE:网关请求包体限制,默认阈值为 1MB,可通过配置 `--size_threshold`"
123123
" 调整,当包体限制检测值(DETECTED VALUE)小于 1MB 时,结果为 WARNING;"
124-
msgstr "REQUEST_BODY_SIZE: Gateway request body size limit. The default threshold is 1MB. You can adjust it using the `--size_thres <threshold>` option. If the detected value is less than 1MB, the result will be WARNING;"
124+
msgstr "REQUEST_BODY_SIZE: Gateway request body size limit. The default threshold is 1MB. You can adjust it using the `--size_threshold` option. If the detected value is less than 1MB, the result will be WARNING;"
125125

126126
#: ../../deployment/diagnose_tool.md:115
127127
msgid ""
128-
"RTT:传输延迟,默认阈值为 50ms,可通过配置 `--rtt_thres "
129-
"\\<threshold\\>`调整,当传输延迟检测值(DETECTED VALUE)大于 50ms 时,结果为 WARNING。"
130-
msgstr "RTT: Transmission latency. The default threshold is 50ms. You can adjust it using the `--rtt_thres <threshold>` option. If the detected value exceeds 50ms, the result will be WARNING."
128+
"RTT:传输延迟,默认阈值为 50ms,可通过配置 `--rtt_threshold`"
129+
"`调整,当传输延迟检测值(DETECTED VALUE)大于 50ms 时,结果为 WARNING。"
130+
msgstr "RTT: Transmission latency. The default threshold is 50ms. You can adjust it using the `--rtt_threshold` option. If the detected value exceeds 50ms, the result will be WARNING."
131131

132132
#: ../../deployment/diagnose_tool.md:116
133133
msgid "NETWORK STATISTICS(bob-alice): Bob 到 Alice 的请求链路网络指标。"

docs/locales/en/LC_MESSAGES/reference/apis/domain_cn.po

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -563,7 +563,7 @@ msgid "state"
563563
msgstr ""
564564

565565
#: ../../reference/apis/domain_cn.md
566-
msgid "部署令牌状态 used, unsed"
566+
msgid "部署令牌状态 used, unused"
567567
msgstr "Deployment Token Status: Used, Unused."
568568

569569
#: ../../reference/apis/domain_cn.md:427

docs/locales/en/LC_MESSAGES/reference/apis/domainroute_cn.po

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -477,7 +477,7 @@ msgstr "Route List"
477477

478478
#: ../../reference/apis/domainroute_cn.md:291
479479
msgid "响应(BatchQueryDomainRouteStatusResponse)"
480-
msgstr "Response(BatchQueryDomainRouteStatusRespons)"
480+
msgstr "Response(BatchQueryDomainRouteStatusResponse)"
481481

482482
#: ../../reference/apis/domainroute_cn.md
483483
msgid "BatchQueryDomainRouteStatusResponseData"

docs/locales/en/LC_MESSAGES/troubleshoot/network/network_troubleshoot.po

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ msgid ""
6666
"通常来说,External.log 是的请求是入口流量,Internal.log里的请求是出口流量。但是存在一种特殊场景,即转发场景,Alice "
6767
"--> Bob --> Carol。在 Bob 上,如果收到一个发送给 Carol 的请求,比如请求的域名是 "
6868
"xxx.carol.svc,Alice 的请求是 ExternalPort 进去,然后转到 InternalPort,最后转发到 Carol "
69-
"的网关所以 Bob 的 External 和 Intenral.log 里会有对应该请求的 traceid 的两条日志,也可以根据请求的域名判断 "
69+
"的网关所以 Bob 的 External 和 Internal.log 里会有对应该请求的 traceid 的两条日志,也可以根据请求的域名判断 "
7070
"ServiceName 中的 NameSpace 是不是自己的节点"
7171
msgstr ""
7272
"Typically, requests in External.log are inbound traffic, while requests in Internal.log are outbound traffic. However, there is a special scenario: the forwarding scenario, Alice --> Bob --> Carol. On Bob, if a request is received for Carol, such as a request with the domain name xxx.carol.svc, Alice's request enters through the ExternalPort, then transfers to the InternalPort, and finally forwards to Carol's gateway. Therefore, Bob's External and Internal.log will have two log entries with the corresponding traceid for this request. You can also determine whether the NameSpace in the ServiceName is your own node based on the request's domain name."
@@ -88,5 +88,5 @@ msgid "发送端的internal.log"
8888
msgstr "Sender's internal.log"
8989

9090
#: ../../troubleshoot/network/network_troubleshoot.md:44
91-
msgid "接收端的exernal.log"
91+
msgid "接收端的external.log"
9292
msgstr "Receiver's external.log"

docs/reference/apis/domain_cn.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -419,7 +419,7 @@ curl -k -X POST 'https://localhost:8082/api/v1/domain/batchQuery' \
419419
| 字段 | 类型 | 描述 |
420420
|----------------------|--------|----------------------------------------------|
421421
| token | string | 部署令牌 |
422-
| state | string | 部署令牌状态 used, unsed |
422+
| state | string | 部署令牌状态 used, unused |
423423
| last_transition_time | string | 最后更新时间,RFC3339 格式(e.g. 2006-01-02T15:04:05Z) |
424424

425425
{#auth-center}

docs/troubleshoot/network/network_troubleshoot.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Envoy 的日志参考 [envoy 日志](../../deployment/logdescription.md#envoy)
2323

2424
### 怎么区分是入口流量还是出口流量呢
2525

26-
通常来说,External.log 是的请求是入口流量,Internal.log里的请求是出口流量。但是存在一种特殊场景,即转发场景,Alice --> Bob --> Carol。在 Bob 上,如果收到一个发送给 Carol 的请求,比如请求的域名是 xxx.carol.svc,Alice 的请求是 ExternalPort 进去,然后转到 InternalPort,最后转发到 Carol 的网关所以 Bob 的 External 和 Intenral.log 里会有对应该请求的 traceid 的两条日志,也可以根据请求的域名判断 ServiceName 中的 NameSpace 是不是自己的节点
26+
通常来说,External.log 是的请求是入口流量,Internal.log里的请求是出口流量。但是存在一种特殊场景,即转发场景,Alice --> Bob --> Carol。在 Bob 上,如果收到一个发送给 Carol 的请求,比如请求的域名是 xxx.carol.svc,Alice 的请求是 ExternalPort 进去,然后转到 InternalPort,最后转发到 Carol 的网关所以 Bob 的 External 和 Internal.log 里会有对应该请求的 traceid 的两条日志,也可以根据请求的域名判断 ServiceName 中的 NameSpace 是不是自己的节点
2727

2828
示例如下:
2929

@@ -41,7 +41,7 @@ Envoy 的日志参考 [envoy 日志](../../deployment/logdescription.md#envoy)
4141
1.1.1.1 - [04/Jan/2024:05:52:40 +0000] bob squu-xaskaali-node-3-0-fed.alice.svc "POST /org.interconnection.link.ReceiverService/Push HTTP/1.1" b257a3410662f1f3 b257a3410662f1f3 200 - 149 0 0 0 0 - -
4242
```
4343

44-
- 接收端的exernal.log
44+
- 接收端的external.log
4545

4646
```bash
4747
2.2.2.2 - [04/Jan/2024:05:52:40 +0000] bob squu-xaskaali-node-3-0-fed.alice.svc "POST /org.interconnection.link.ReceiverService/Push HTTP/1.1" b257a3410662f1f3 b257a3410662f1f3 200 - 149 0 - -

pkg/agent/provider/node/generic_node.go

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -211,8 +211,8 @@ func (gnp *GenericNodeProvider) refreshNodeConditions(ctx context.Context, st *v
211211
}
212212

213213
var kernelParamsChanged bool
214-
kernalParamOK, kerunalParamMsg := gnp.refreshKernelParamsCondition()
215-
if kernalParamOK {
214+
kernelParamOK, kerunalParamMsg := gnp.refreshKernelParamsCondition()
215+
if kernelParamOK {
216216
st.Conditions, kernelParamsChanged =
217217
nodeutils.AddOrUpdateNodeCondition(st.Conditions, v1.NodeCondition{
218218
Type: "Kernel-Params",

pkg/diagnose/mods/crd.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ func (m *CRDMod) ValidateClusterDomainRoute(ctx context.Context, item *CRDItem)
9797
return m.OnFailure(item, err.Error())
9898
}
9999

100-
// TODO: check certifate?
100+
// TODO: check certificate?
101101
m.OnSuccess(item)
102102
return nil
103103
}

0 commit comments

Comments
 (0)