dashboard: Update TiDB Dashboard to v2021.06.15.1 (#3785)

[shhdgit]

What problem does this PR solve?

This is an cherry-pick of #3785

Signed-off-by: Suhaha [email protected]

What is changed and how it works?

Check List

Update to TiDB Dashboard v2021.06.15.1

Tests

• Manual test (add detailed scripts or steps below)

Related changes

• Need to cherry-pick to the release branch

Release note

Update TiDB Dashboard to v2021.06.15.1

[codecov]

Codecov Report

Merging #3798 (76c6f5a) into release-5.0 (65ddb56) will decrease coverage by 0.22%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           release-5.0    #3798      +/-   ##
===============================================
- Coverage        74.75%   74.52%   -0.23%     
===============================================
  Files              245      245              
  Lines            24188    24188              
===============================================
- Hits             18081    18027      -54     
- Misses            4495     4537      +42     
- Partials          1612     1624      +12     

Flag	Coverage Δ
unittests	74.52% <ø> (-0.23%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
pkg/tempurl/tempurl.go	45.00% <0.00%> (-25.00%)	⬇️
server/region_syncer/server.go	83.33% <0.00%> (-6.07%)	⬇️
server/election/leadership.go	83.52% <0.00%> (-5.89%)	⬇️
server/tso/allocator_manager.go	74.41% <0.00%> (-5.32%)	⬇️
server/member/member.go	69.56% <0.00%> (-3.27%)	⬇️
server/schedulers/utils.go	93.10% <0.00%> (-1.38%)	⬇️
client/base_client.go	82.47% <0.00%> (-0.52%)	⬇️
server/cluster/cluster.go	82.95% <0.00%> (-0.37%)	⬇️
server/grpc_service.go	46.83% <0.00%> (-0.34%)	⬇️
server/schedule/operator/step.go	67.44% <0.00%> (-0.34%)	⬇️
... and 4 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 65ddb56...76c6f5a. Read the comment docs.

[shhdgit]

/label needs-cherry-pick-release-5.0

[ti-chi-bot]

@shhdgit: The label(s) type/cherry-pick-for-release-5.1 cannot be applied. These labels are supported: Hacktoberfest, challenge-program, ci-unstable, compatibility-breaker, high-performance, hptc, needs-cherry-pick-release-1.0, needs-cherry-pick-release-2.0, needs-cherry-pick-release-2.1, needs-cherry-pick-release-3.0, needs-cherry-pick-release-3.1, needs-cherry-pick-release-4.0, needs-cherry-pick-release-5.0, needs-cherry-pick-release-5.1, release-note, require-LGT1, wontfix.

In response to this:

/label type/cherry-pick-for-release-5.1

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

@shhdgit: The label(s) cherry-pick-for-release-5.1 cannot be applied. These labels are supported: Hacktoberfest, challenge-program, ci-unstable, compatibility-breaker, high-performance, hptc, needs-cherry-pick-release-1.0, needs-cherry-pick-release-2.0, needs-cherry-pick-release-2.1, needs-cherry-pick-release-3.0, needs-cherry-pick-release-3.1, needs-cherry-pick-release-4.0, needs-cherry-pick-release-5.0, needs-cherry-pick-release-5.1, release-note, require-LGT1, wontfix.

In response to this:

/label cherry-pick-for-release-5.1

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[rleungx]

Hi, seems it is duplicated with #3794.

[shhdgit]

Yes, how do I resolve the conflict in #3794, instead of opening a new pr?

[breezewish]

@nolouch Please take a look about this PR, and please help close these two, thanks!

#3794
#3793

[HunDunDM]

Yes, how do I resolve the conflict in #3794, instead of opening a new pr?

Due to some security issues, we are temporarily unable to do so, I will close the bot PR.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• HunDunDM

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[shhdgit]

Thank you so much.

[nolouch]

/merge

[ti-chi-bot]

@nolouch: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 9cd7f9f

[purelind]

/run-integration-tests

[nolouch]

/merge

[ti-chi-bot]

@nolouch: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.