en,zh: add pause deployment docs of tidb cluster #906

BinChenn · 2020-12-07T11:41:14Z

First-time contributors' checklist

I've signed Contributor License Agreement that's required for repo owners to accept my contribution.

What is changed, added, or deleted? (Required)

Fix #79

Add docs of pause-deployment-of-tidbcluster in en and zh.

Change TOC.md, insert Pause Deloyment of TiDB Cluster in catalog Operator / 运维

Which TiDB Operator version(s) do your changes apply to? (Required)

master (the latest development version)
v1.1 (TiDB Operator 1.1 versions)
v1.0 (TiDB Operator 1.0 versions)

What is the related PR or file link(s)?

This PR is translated from:
#2013
Other reference link(s):

Do your changes match any of the following descriptions?

NONE

BinChenn · 2020-12-08T02:30:13Z

/cc @ran-huang

BinChenn · 2020-12-08T02:33:15Z

/needs-cherry-pick-1.1

dragonly

文档中的“部署”不太符合实际场景，建议改为“同步”，英文可以对应为“sync”。

部署一般只第一次安装运行，而 TidbCluster.Spec.Paused 设置好之后，实际行为是暂停同步 Spec 与 Status。

en/pause-deployment-of-tidbcluster.md

en/TOC.md

zh/pause-deployment-of-tidbcluster.md

zh/pause-sync-of-tidbcluster.md

en/TOC.md

en/pause-sync-of-tidb-cluster.md

ran-huang

Rest LGTM

en/pause-sync-of-tidb-cluster.md

BinChenn

gfd

ti-srebot · 2020-12-13T11:42:47Z

@BinChenn, please update your pull request.

ran-huang · 2020-12-14T02:36:52Z

@dragonly PTAL. Thanks

ti-srebot · 2020-12-20T04:26:29Z

@BinChenn, please update your pull request.

DanielZhangQD · 2020-12-24T06:26:51Z

zh/pause-sync-of-tidb-cluster.md

+    {{< copyable "shell-regular" >}}
+
+    ```shell
+    kubectl edit tc/`${cluster_name}` -n ${namespace}


Suggested change

kubectl edit tc/`${cluster_name}` -n ${namespace}

kubectl edit tc ${cluster_name} -n ${namespace}

To keep consistent with the other docs.

DanielZhangQD · 2020-12-24T06:36:31Z

zh/pause-sync-of-tidb-cluster.md

+        ...
+    ```
+
+3. TiDB 集群同步暂停后，可以使用以下命令查看 Controller Pod 日志确认 TiDB 集群同步状态。其中 `${pod_name}` 表示 Controller Pod 的名称，`${namespace}` 表示 TiDB Operator 所在的 namespace。


Suggested change

3. TiDB 集群同步暂停后，可以使用以下命令查看 Controller Pod 日志确认 TiDB 集群同步状态。其中 `${pod_name}` 表示 Controller Pod 的名称，`${namespace}` 表示 TiDB Operator 所在的 namespace。

3. TiDB 集群同步暂停后，可以使用以下命令查看 tidb-controller-manager Pod 日志确认 TiDB 集群同步状态。其中 `${pod_name}` 表示 tidb-controller-manager Pod 的名称，`${namespace}` 表示 TiDB Operator 所在的 namespace。

DanielZhangQD · 2020-12-24T06:37:27Z

zh/pause-sync-of-tidb-cluster.md

+    {{< copyable "shell-regular" >}}
+
+    ```shell
+    kubectl edit tc/${cluster_name} -n ${namespace}


Suggested change

kubectl edit tc/${cluster_name} -n ${namespace}

kubectl edit tc ${cluster_name} -n ${namespace}

DanielZhangQD · 2020-12-24T06:37:58Z

zh/pause-sync-of-tidb-cluster.md

+        ...
+    ```
+
+3. 恢复 TiDB 集群同步后，可以使用以下命令查看 Controller Pod 日志确认 TiDB 集群同步状态。其中 `${pod_name}` 表示 Controller Pod 的名称，`${namespace}` 表示 TiDB Operator 所在的 namespace。


Suggested change

3. 恢复 TiDB 集群同步后，可以使用以下命令查看 Controller Pod 日志确认 TiDB 集群同步状态。其中 `${pod_name}` 表示 Controller Pod 的名称，`${namespace}` 表示 TiDB Operator 所在的 namespace。

3. 恢复 TiDB 集群同步后，可以使用以下命令查看 tidb-controller-manager Pod 日志确认 TiDB 集群同步状态。其中 `${pod_name}` 表示 tidb-controller-manager Pod 的名称，`${namespace}` 表示 TiDB Operator 所在的 namespace。

…ator into improveImportDoc

DanielZhangQD · 2020-12-24T07:12:00Z

en/pause-sync-of-tidb-cluster.md

+    kubectl logs ${pod_name} -n ${namespace} | grep "Finished syncing TidbCluster"
+    ```
+
+    The expected output is as follows. The `finished syncing` timestamp is later than the `pausing` timestamp, which indicates that sync of the TiDB cluster has been resumed.


Suggested change

The expected output is as follows. The `finished syncing` timestamp is later than the `pausing` timestamp, which indicates that sync of the TiDB cluster has been resumed.

The expected output is as follows. The `finished syncing` timestamp is later than the `paused` timestamp, which indicates that sync of the TiDB cluster has been resumed.

ran-huang · 2020-12-24T07:22:07Z

en/pause-sync-of-tidb-cluster.md

+
+# Pause Sync of a TiDB Cluster in Kubernetes
+
+This document introduce how to pause sync of a TiDB cluster in Kubernetes with configuration.


Suggested change

This document introduce how to pause sync of a TiDB cluster in Kubernetes with configuration.

This document introduces how to pause sync of a TiDB cluster in Kubernetes using configuration.

with has multiple meanings. Let's use a more accurate way of expression.

en/pause-sync-of-tidb-cluster.md

ran-huang · 2020-12-24T07:46:19Z

en/pause-sync-of-tidb-cluster.md

+
+- Avoiding unexpected rolling update
+
+    In order to prevent the compatibility of the new version TiDB Operator from affecting the TiDB clusters, you can pause sync of TiDB clusters before updating the TiDB Operator. After updating TiDB Operator, resume sync of TiDB clusters one by one or resume sync of TiDB clusters at a specified time, so as to observe the impact of TiDB Operator rolling update on the cluster.


Suggested change

In order to prevent the compatibility of the new version TiDB Operator from affecting the TiDB clusters, you can pause sync of TiDB clusters before updating the TiDB Operator. After updating TiDB Operator, resume sync of TiDB clusters one by one or resume sync of TiDB clusters at a specified time, so as to observe the impact of TiDB Operator rolling update on the cluster.

To prevent new versions of TiDB Operator from introducing compatibility issues into the clusters, before updating TiDB Operator, you can pause sync of TiDB clusters. After updating TiDB Operator, you can resume syncing clusters one by one, or specify a time for resume. In this way, you can observe how the rolling update of TiDB Operator would affect the cluster.

ran-huang · 2020-12-24T08:00:34Z

en/pause-sync-of-tidb-cluster.md

+
+- Avoid multiple rolling restarts
+
+    In some cases, the configuration of a TiDB cluster may be modified several times over a period of time, but you do not want to restart the TiDB cluster many times. In order to avoid multiple rolling restarts, you can pause sync of a TiDB cluster first. During this period, any modification to configuration of the TiDB cluster will not take effect. After the cluster configuration modification is completed, resuming sync of TiDB Cluster. At this time, multiple configuration changes during the sync pausing can be applied in one time rolling restart.


Suggested change

In some cases, the configuration of a TiDB cluster may be modified several times over a period of time, but you do not want to restart the TiDB cluster many times. In order to avoid multiple rolling restarts, you can pause sync of a TiDB cluster first. During this period, any modification to configuration of the TiDB cluster will not take effect. After the cluster configuration modification is completed, resuming sync of TiDB Cluster. At this time, multiple configuration changes during the sync pausing can be applied in one time rolling restart.

In some cases, you might need to continuously modify the cluster over a period of time, but do not want to restart the TiDB cluster many times. To avoid multiple rolling restarts, you can pause sync of the cluster. During the sync pausing, any change of the configuration does not take effect on the cluster. After you finish the modification, resume sync of the TiDB cluster. All changes can be applied in a single rolling restart.

ran-huang · 2020-12-24T08:05:12Z

en/pause-sync-of-tidb-cluster.md

+
+- Maintenance window
+
+    In some situations, you can update or restart TiDB cluster only during a maintenance window. When outside the maintenance window, you can pause sync of the TiDB cluster, so that any modification to spec does not take effect. When inside the maintenance window, you can resume sync of the TiDB cluster to allow TiDB cluster rolling update or restart.


Suggested change

In some situations, you can update or restart TiDB cluster only during a maintenance window. When outside the maintenance window, you can pause sync of the TiDB cluster, so that any modification to spec does not take effect. When inside the maintenance window, you can resume sync of the TiDB cluster to allow TiDB cluster rolling update or restart.

In some situations, you can update or restart the TiDB cluster only during a maintenance window. When outside the maintenance window, you can pause sync of the TiDB cluster, so that any modification to the specs does not take effect. When inside the maintenance window, you can resume sync of the TiDB cluster to allow TiDB cluster to rolling update or restart.

ran-huang · 2020-12-24T08:20:02Z

en/pause-sync-of-tidb-cluster.md

+        ...
+    ```
+
+3. Execute the following command to confirm the sync status of a TiDB cluster. `${pod_name}` is the name of tidb-controller-manager Pod, and `${namespace}` is the namespace of TiDB Operator.


Suggested change

3. Execute the following command to confirm the sync status of a TiDB cluster. `${pod_name}` is the name of tidb-controller-manager Pod, and `${namespace}` is the namespace of TiDB Operator.

3. To confirm the sync status of a TiDB cluster, execute the following command. `${pod_name}` is the name of tidb-controller-manager Pod, and `${namespace}` is the namespace of TiDB Operator.

ran-huang · 2020-12-24T08:21:06Z

en/pause-sync-of-tidb-cluster.md

+
+## Resume sync
+
+If you want to resume the sync of the TiDB cluster, configure the TidbCluster CR with `spec.paused: false`.


Suggested change

If you want to resume the sync of the TiDB cluster, configure the TidbCluster CR with `spec.paused: false`.

To resume the sync of the TiDB cluster, configure `spec.paused: false` in the TidbCluster CR.

ran-huang · 2020-12-24T08:23:15Z

en/pause-sync-of-tidb-cluster.md

+
+If you want to resume the sync of the TiDB cluster, configure the TidbCluster CR with `spec.paused: false`.
+
+1. Execute the following command to edit configuration of TiDB cluster. `${cluster_name}` represents the name of TiDB cluster, and `${namespace}` refers to the TiDB cluster namespace.


Suggested change

1. Execute the following command to edit configuration of TiDB cluster. `${cluster_name}` represents the name of TiDB cluster, and `${namespace}` refers to the TiDB cluster namespace.

1. Execute the following command to edit the TiDB cluster configuration. `${cluster_name}` represents the name of the TiDB cluster, and `${namespace}` refers to the TiDB cluster namespace.

ran-huang · 2020-12-24T08:24:33Z

en/pause-sync-of-tidb-cluster.md

+    kubectl edit tc ${cluster_name} -n ${namespace}
+    ```
+
+2. Configure the TidbCluster CR with `spec.paused: false` as following, save changes and exit editor, sync of TiDB cluster's components (PD, TiKV, TiDB, TiFlash, TiCDC,Pump) will be resumed. 


Suggested change

2. Configure the TidbCluster CR with `spec.paused: false` as following, save changes and exit editor, sync of TiDB cluster's components (PD, TiKV, TiDB, TiFlash, TiCDC,Pump) will be resumed.

2. Configure `spec.paused: false` as follows, and save changes. The sync of TiDB cluster components (PD, TiKV, TiDB, TiFlash, TiCDC, Pump) is then resumed.

ran-huang · 2020-12-24T08:25:51Z

en/pause-sync-of-tidb-cluster.md

+        ...
+    ```
+
+3. After resuming sync of the TiDB cluster, execute the following command to confirm sync status of the TiDB cluster. `${pod_name}` represents the name of tidb-controller-manager Pod, `${namespace}` represents the namespace of TiDB Operator.


Suggested change

3. After resuming sync of the TiDB cluster, execute the following command to confirm sync status of the TiDB cluster. `${pod_name}` represents the name of tidb-controller-manager Pod, `${namespace}` represents the namespace of TiDB Operator.

3. To confirm the sync status of a TiDB cluster, execute the following command. `${pod_name}` represents the name of the tidb-controller-manager Pod, and `${namespace}` represents the namespace of TiDB Operator.

ti-srebot · 2020-12-26T06:52:08Z

@BinChenn, please update your pull request.

ti-srebot · 2020-12-28T06:52:09Z

@BinChenn, please update your pull request.

DanielZhangQD

LGTM with the Chinese doc.

ran-huang

LGTM

ran-huang · 2020-12-29T02:54:19Z

/merge

ti-srebot · 2020-12-29T02:56:42Z

/run-all-tests

Signed-off-by: ti-srebot <ti-srebot@pingcap.com>

ti-srebot · 2020-12-29T02:59:15Z

cherry pick to release-1.1 in PR #958

Signed-off-by: ti-srebot <ti-srebot@pingcap.com> Co-authored-by: BinChen <binchinsmail@gmail.com>

BinChenn force-pushed the improveImportDoc branch from f48f8f1 to b9d451f Compare December 7, 2020 11:44

ti-srebot requested a review from ran-huang December 8, 2020 02:30

ran-huang added needs-cherry-pick-1.1 translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR. labels Dec 8, 2020

ran-huang requested a review from DanielZhangQD December 8, 2020 06:20

dragonly requested changes Dec 8, 2020

View reviewed changes

en/pause-deployment-of-tidbcluster.md Outdated Show resolved Hide resolved

ran-huang reviewed Dec 8, 2020

View reviewed changes

BinChenn force-pushed the improveImportDoc branch 2 times, most recently from 3524b1a to 50f4e1a Compare December 9, 2020 02:10

dragonly reviewed Dec 9, 2020

View reviewed changes

zh/pause-sync-of-tidbcluster.md Outdated Show resolved Hide resolved

BinChenn force-pushed the improveImportDoc branch from 50f4e1a to dbfba8c Compare December 9, 2020 09:04

ran-huang reviewed Dec 9, 2020

View reviewed changes

ran-huang added the status/require-change Needs the author to address comments. label Dec 9, 2020

BinChenn force-pushed the improveImportDoc branch from dbfba8c to 5b26ba2 Compare December 9, 2020 11:30

en,zh: add pause deployment docs of tidb cluster

9e31a8f

BinChenn force-pushed the improveImportDoc branch from eb66179 to 9e31a8f Compare December 9, 2020 11:32

ran-huang reviewed Dec 10, 2020

View reviewed changes

BinChenn force-pushed the improveImportDoc branch from 6081cec to b9a5de0 Compare December 10, 2020 10:07

ran-huang removed the status/require-change Needs the author to address comments. label Dec 11, 2020

ran-huang reviewed Dec 11, 2020

View reviewed changes

BinChenn commented Dec 11, 2020

View reviewed changes

fix syntax error

9762a4d

BinChenn force-pushed the improveImportDoc branch from 31aa5fc to 9762a4d Compare December 11, 2020 11:24

Merge branch 'master' into improveImportDoc

d8834a4

Merge branch 'master' into improveImportDoc

874e34f

BinChenn requested a review from dragonly December 15, 2020 02:32

update shell var

f5b3289

BinChenn force-pushed the improveImportDoc branch from 23d84e8 to f5b3289 Compare December 21, 2020 02:01

BinChenn and others added 2 commits December 21, 2020 10:03

fix command

f0ed135

Merge branch 'master' into improveImportDoc

faa197a

BinChenn requested a review from DanielZhangQD December 23, 2020 02:21

Merge branch 'master' into improveImportDoc

e60f49a

DanielZhangQD reviewed Dec 24, 2020

View reviewed changes

BinChenn added 2 commits December 24, 2020 14:49

fix typo and command

c67637d

Merge branch 'improveImportDoc' of github.com:BinChenn/docs-tidb-oper…

6347845

…ator into improveImportDoc

DanielZhangQD reviewed Dec 24, 2020

View reviewed changes

ran-huang reviewed Dec 24, 2020

View reviewed changes

DanielZhangQD approved these changes Dec 28, 2020

View reviewed changes

ti-srebot added the status/LGT1 Indicates that a PR has LGTM 1. label Dec 28, 2020

fix syntax errors

2910931

ran-huang approved these changes Dec 29, 2020

View reviewed changes

ti-srebot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Dec 29, 2020

ti-srebot approved these changes Dec 29, 2020

View reviewed changes

ti-srebot added the status/can-merge Indicates a PR has been approved by a committer. label Dec 29, 2020

Merge branch 'master' into improveImportDoc

ca420f5

ti-srebot merged commit e0bcbcc into pingcap:master Dec 29, 2020

ti-srebot pushed a commit to ti-srebot/docs-tidb-operator that referenced this pull request Dec 29, 2020

cherry pick pingcap#906 to release-1.1

18398ff

Signed-off-by: ti-srebot <ti-srebot@pingcap.com>

ti-srebot mentioned this pull request Dec 29, 2020

en,zh: add pause deployment docs of tidb cluster (#906) #958

Merged

4 tasks

ran-huang pushed a commit that referenced this pull request Dec 29, 2020

cherry pick #906 to release-1.1 (#958)

d06030a

Signed-off-by: ti-srebot <ti-srebot@pingcap.com> Co-authored-by: BinChen <binchinsmail@gmail.com>

	kubectl edit tc/`${cluster_name}` -n ${namespace}
	kubectl edit tc ${cluster_name} -n ${namespace}

	3. TiDB 集群同步暂停后，可以使用以下命令查看 Controller Pod 日志确认 TiDB 集群同步状态。其中 `${pod_name}` 表示 Controller Pod 的名称，`${namespace}` 表示 TiDB Operator 所在的 namespace。
	3. TiDB 集群同步暂停后，可以使用以下命令查看 tidb-controller-manager Pod 日志确认 TiDB 集群同步状态。其中 `${pod_name}` 表示 tidb-controller-manager Pod 的名称，`${namespace}` 表示 TiDB Operator 所在的 namespace。

	kubectl edit tc/${cluster_name} -n ${namespace}
	kubectl edit tc ${cluster_name} -n ${namespace}

	3. 恢复 TiDB 集群同步后，可以使用以下命令查看 Controller Pod 日志确认 TiDB 集群同步状态。其中 `${pod_name}` 表示 Controller Pod 的名称，`${namespace}` 表示 TiDB Operator 所在的 namespace。
	3. 恢复 TiDB 集群同步后，可以使用以下命令查看 tidb-controller-manager Pod 日志确认 TiDB 集群同步状态。其中 `${pod_name}` 表示 tidb-controller-manager Pod 的名称，`${namespace}` 表示 TiDB Operator 所在的 namespace。

	The expected output is as follows. The `finished syncing` timestamp is later than the `pausing` timestamp, which indicates that sync of the TiDB cluster has been resumed.
	The expected output is as follows. The `finished syncing` timestamp is later than the `paused` timestamp, which indicates that sync of the TiDB cluster has been resumed.


		# Pause Sync of a TiDB Cluster in Kubernetes

		This document introduce how to pause sync of a TiDB cluster in Kubernetes with configuration.

	This document introduce how to pause sync of a TiDB cluster in Kubernetes with configuration.
	This document introduces how to pause sync of a TiDB cluster in Kubernetes using configuration.


		- Avoiding unexpected rolling update

		In order to prevent the compatibility of the new version TiDB Operator from affecting the TiDB clusters, you can pause sync of TiDB clusters before updating the TiDB Operator. After updating TiDB Operator, resume sync of TiDB clusters one by one or resume sync of TiDB clusters at a specified time, so as to observe the impact of TiDB Operator rolling update on the cluster.

	In order to prevent the compatibility of the new version TiDB Operator from affecting the TiDB clusters, you can pause sync of TiDB clusters before updating the TiDB Operator. After updating TiDB Operator, resume sync of TiDB clusters one by one or resume sync of TiDB clusters at a specified time, so as to observe the impact of TiDB Operator rolling update on the cluster.
	To prevent new versions of TiDB Operator from introducing compatibility issues into the clusters, before updating TiDB Operator, you can pause sync of TiDB clusters. After updating TiDB Operator, you can resume syncing clusters one by one, or specify a time for resume. In this way, you can observe how the rolling update of TiDB Operator would affect the cluster.


		- Avoid multiple rolling restarts

		In some cases, the configuration of a TiDB cluster may be modified several times over a period of time, but you do not want to restart the TiDB cluster many times. In order to avoid multiple rolling restarts, you can pause sync of a TiDB cluster first. During this period, any modification to configuration of the TiDB cluster will not take effect. After the cluster configuration modification is completed, resuming sync of TiDB Cluster. At this time, multiple configuration changes during the sync pausing can be applied in one time rolling restart.


		- Maintenance window

		In some situations, you can update or restart TiDB cluster only during a maintenance window. When outside the maintenance window, you can pause sync of the TiDB cluster, so that any modification to spec does not take effect. When inside the maintenance window, you can resume sync of the TiDB cluster to allow TiDB cluster rolling update or restart.

	3. Execute the following command to confirm the sync status of a TiDB cluster. `${pod_name}` is the name of tidb-controller-manager Pod, and `${namespace}` is the namespace of TiDB Operator.
	3. To confirm the sync status of a TiDB cluster, execute the following command. `${pod_name}` is the name of tidb-controller-manager Pod, and `${namespace}` is the namespace of TiDB Operator.


		## Resume sync

		If you want to resume the sync of the TiDB cluster, configure the TidbCluster CR with `spec.paused: false`.

	If you want to resume the sync of the TiDB cluster, configure the TidbCluster CR with `spec.paused: false`.
	To resume the sync of the TiDB cluster, configure `spec.paused: false` in the TidbCluster CR.


		If you want to resume the sync of the TiDB cluster, configure the TidbCluster CR with `spec.paused: false`.

		1. Execute the following command to edit configuration of TiDB cluster. `${cluster_name}` represents the name of TiDB cluster, and `${namespace}` refers to the TiDB cluster namespace.

	2. Configure the TidbCluster CR with `spec.paused: false` as following, save changes and exit editor, sync of TiDB cluster's components (PD, TiKV, TiDB, TiFlash, TiCDC,Pump) will be resumed.
	2. Configure `spec.paused: false` as follows, and save changes. The sync of TiDB cluster components (PD, TiKV, TiDB, TiFlash, TiCDC, Pump) is then resumed.

	3. After resuming sync of the TiDB cluster, execute the following command to confirm sync status of the TiDB cluster. `${pod_name}` represents the name of tidb-controller-manager Pod, `${namespace}` represents the namespace of TiDB Operator.
	3. To confirm the sync status of a TiDB cluster, execute the following command. `${pod_name}` represents the name of the tidb-controller-manager Pod, and `${namespace}` represents the namespace of TiDB Operator.

en,zh: add pause deployment docs of tidb cluster #906

en,zh: add pause deployment docs of tidb cluster #906

Conversation

BinChenn commented Dec 7, 2020 • edited by ran-huang Loading

First-time contributors' checklist

What is changed, added, or deleted? (Required)

Which TiDB Operator version(s) do your changes apply to? (Required)

What is the related PR or file link(s)?

Do your changes match any of the following descriptions?

BinChenn commented Dec 8, 2020

BinChenn commented Dec 8, 2020

dragonly left a comment

Choose a reason for hiding this comment

ran-huang left a comment

Choose a reason for hiding this comment

BinChenn left a comment

Choose a reason for hiding this comment

ti-srebot commented Dec 13, 2020

ran-huang commented Dec 14, 2020

ti-srebot commented Dec 20, 2020

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ti-srebot commented Dec 26, 2020

ti-srebot commented Dec 28, 2020

DanielZhangQD left a comment

Choose a reason for hiding this comment

ran-huang left a comment

Choose a reason for hiding this comment

ran-huang commented Dec 29, 2020

ti-srebot commented Dec 29, 2020

ti-srebot commented Dec 29, 2020

BinChenn commented Dec 7, 2020 •

edited by ran-huang

Loading