8000 chore(dashboard): update TiDB Dashboard to v6.5.13-89eba508 [release-6.5] by baurine · Pull Request #9277 · tikv/pd · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore(dashboard): update TiDB Dashboard to v6.5.13-89eba508 [release-6.5] #9277

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 2 commits into
base: release-6.5
Choose a base branch
from
Open

chore(dashboard): update TiDB Dashboard to v6.5.13-89eba508 [release-6.5] #9277

wants to merge 2 commits into from
+7 −7

Conversation

baurine
Copy link
Contributor
@baurine baurine commented Apr 28, 2025 •
edited
Loading

What problem does this PR solve?

Issue Number: close #9278, ref #4257

Update TiDB Dashboard to v6.5.13-89eba508.

This PR includes 3 major tidb-dashboard changes:

  1. truncate too long sql text for sql statement & slow query list to improve performance
  2. add 1 year, custom, no expiration options for share code to login, required by client
  3. add read-only mode for diagnose/manual profiling/debug data features, required by client

related tidb-dashboard PRs:

Release note

None

@baurine
chore(dashboard): update TiDB Dashboard to v6.5.13-4c27fa6d
9e68e92 
Signed-off-by: baurine <2008.hbl@gmail.com>
@ti-chi-bot ti-chi-bot bot added do-not-merge/cherry-pick-not-approved release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has signed the dco. labels Apr 28, 2025
@ti-chi-bot ti-chi-bot
Copy link
Contributor
ti-chi-bot bot commented Apr 28, 2025

This cherry pick PR is for a release branch and has not yet been approved by triage owners.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick:

  1. It must be approved by the approvers firstly.
  2. AFTER it has been approved by approvers, please wait for the cherry-pick merging approval from triage owners.

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 kubernetes-sigs/prow repository.

@ti-chi-bot ti-chi-bot
Copy link
Contributor
ti-chi-bot bot commented Apr 28, 2025

Hi @baurine. Thanks for your PR.

I'm waiting for a tikv member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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 kubernetes-sigs/prow repository.

@ti-chi-bot ti-chi-bot bot added needs-ok-to-test Indicates a PR created by contributors and need ORG member send '/ok-to-test' to start testing. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Apr 28, 2025
@ti-chi-bot ti-chi-bot bot added approved needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Apr 28, 2025
@rleungx
Copy link
Member
rleungx commented Apr 28, 2025

/ok-to-test

@ti-chi-bot ti-chi-bot bot added ok-to-test Indicates a PR is ready to be tested. dco-signoff: no Indicates the PR's author has not signed dco. and removed needs-ok-to-test Indicates a PR created by contributors and need ORG member send '/ok-to-test' to start testing. dco-signoff: yes Indicates the PR's author has signed the dco. labels Apr 28, 2025
@baurine
chore(dashboard): update TiDB Dashboard to v6.5.13-89eba508
658f7ee 
Signed-off-by: baurine <2008.hbl@gmail.com>
@baurine baurine force-pushed the update-tidb-dashboard/release-6.5-v6.5.13-4c27fa6d-1745825763 branch from b6f98c7 to 658f7ee Compare April 29, 2025 06:41
@ti-chi-bot ti-chi-bot bot added dco-signoff: yes Indicates the PR's author has signed the dco. and removed dco-signoff: no Indicates the PR's author has not signed dco. labels Apr 29, 2025
@baurine baurine changed the title chore(dashboard): update TiDB Dashboard to v6.5.13-4c27fa6d [release-6.5] chore(dashboard): update TiDB Dashboard to v6.5.13-89eba508 [release-6.5] Apr 29, 2025
@ti-chi-bot ti-chi-bot
Copy link
Contributor
ti-chi-bot bot commented Apr 29, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JmPotato, rleungx

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

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Apr 29, 2025
@ti-chi-bot ti-chi-bot
Copy link
Contributor
ti-chi-bot bot commented Apr 29, 2025

[LGTM Timeline notifier]

Timeline:

  • 2025-04-28 08:12:17.205430463 +0000 UTC m=+861681.017220839: ☑️ agreed by rleungx.
  • 2025-04-29 06:59:00.943202976 +0000 UTC m=+943684.754993356: ☑️ agreed by JmPotato.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@JmPotato JmPotato JmPotato approved these changes

@rleungx rleungx rleungx approved these changes

Assignees
No one assigned
Labels
approved dco-signoff: yes Indicates the PR's author has signed the dco. do-not-merge/cherry-pick-not-approved lgtm ok-to-test Indicates a PR is ready to be tested. release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@baurine @rleungx @JmPotato
0