[FLINK-34401][docs-zh] Translate "Flame Graphs" page into Chinese
What is the purpose of the change
Translate Flame Graphs to Chinese
Brief change log
The page is located at "docs/content.zh/docs/ops/debugging/flame_graphs.md"
Verifying this change
Docs only change.
Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (yes / no) no
- The public API, i.e., is any changed class annotated with
@Public(Evolving): (yes / no) no - The serializers: (yes / no / don't know) no
- The runtime per-record code paths (performance sensitive): (yes / no / don't know) no
- Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know) no
- The S3 file system connector: (yes / no / don't know) bo
Documentation
- Does this pull request introduce a new feature? (yes / no) no
- If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
CI report:
- 29a741b046a99e97ce4d853726a7d5fce3746bcd Azure: SUCCESS
Bot commands
The @flinkbot bot supports the following commands:@flinkbot run azurere-run the last Azure build
@flinkbot run azure
@flinkbot run azure
Hi @JingGe , thank you for your advice, it is my first time participating in the Flink project. i have added 2 commits with your suggestion, Please review it when you have free time, thank you.
@flinkbot run azure
@flinkbot run azure
@flinkbot run azure
@flinkbot run azure
@flinkbot run azure
Could you rebase your branch?
hi @JingGe , I have done with it, is that OK for you to merge this PR? thanks a lot.
hi @JingGe , I have done with it, is that OK for you to merge this PR? thanks a lot.
sure, let's wait until the CI passed
@Zakelly 谢谢建议,还有这个pr没合入之前,每次master变更都要merge,然后merge又要过CI,CI耗时又很长,很是麻烦,我想问问CI在跑的过程中能合入吗
@Zakelly 谢谢建议,还有这个pr没合入之前,每次master变更都要merge,然后merge又要过CI,CI耗时又很长,很是麻烦,我想问问CI在跑的过程中能合入吗
如果是文档类的更改,确认不对CI造成影响的可以,committer可以合。master变更的话不用merge回你的更改分支哈,如果有更改可以继续提交commit即可。如果因为有冲突合不进去那需要进行rebase。
@Zakelly 谢谢建议,还有这个pr没合入之前,每次master变更都要merge,然后merge又要过CI,CI耗时又很长,很是麻烦,我想问问CI在跑的过程中能合入吗
如果是文档类的更改,确认不对CI造成影响的可以,committer可以合。master变更的话不用merge回你的更改分支哈,如果有更改可以继续提交commit即可。如果因为有冲突合不进去那需要进行rebase。
好的,非常感谢
@flinkbot run azure
@JingGe could you please merge this PR, thanks
@lxliyou001 sure, would you like to squash your commits?
@JingGe sure,could you help me do the "Squash and merge" action? thanks.