Skip to content

go.mod: update PD client for pd#10997#69837

Merged
ti-chi-bot[bot] merged 1 commit into
pingcap:release-nextgen-202603from
lhy1024:update-pd-client-nextgen-2603
Jul 14, 2026
Merged

go.mod: update PD client for pd#10997#69837
ti-chi-bot[bot] merged 1 commit into
pingcap:release-nextgen-202603from
lhy1024:update-pd-client-nextgen-2603

Conversation

@lhy1024

@lhy1024 lhy1024 commented Jul 14, 2026

Copy link
Copy Markdown
Member

What problem does this PR solve?

Issue Number: ref tikv/pd#10997

Problem Summary:

Successful Resource Control token waits can produce excessive TiDB warning logs.

What changed and how does it work?

Check List

Tests

  • Unit test
    • go test ./pkg/domain/affinity -tags=intest,deadlock,nextgen -count=1
  • Manual test (add detailed scripts or steps below)
    • make bazel_prepare
    • go mod verify
    • bazel build --remote_cache=https://cache.hawkingrei.com/bazelcache --noremote_upload_local_results //pkg/domain/affinity:affinity was attempted, but the new PD client and kvproto archives have not reached the configured TiDB mirrors yet (404/502).
  • Integration test
  • No need to test
    • I checked and no code files have been changed.

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility

Documentation

  • Affects user behaviors
  • Contains syntax changes
  • Contains variable changes
  • Contains experimental features
  • Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

Reduce excessive TiDB warning logs for successful Resource Control token waits.

Summary by CodeRabbit

  • Chores
    • Updated internal dependency versions for improved compatibility and access to the latest upstream changes.
    • Synchronized dependency metadata and integrity checks with the updated versions.

@ti-chi-bot ti-chi-bot Bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jul 14, 2026
@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown

Caution

Review failed

An error occurred during the review process. Please try again later.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@ti-chi-bot

ti-chi-bot Bot commented Jul 14, 2026

Copy link
Copy Markdown

@bufferflies: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

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 the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Jul 14, 2026
@dillon-zheng

Copy link
Copy Markdown
Contributor

/retest

@lhy1024

lhy1024 commented Jul 14, 2026

Copy link
Copy Markdown
Member Author

/retest

@lhy1024

lhy1024 commented Jul 14, 2026

Copy link
Copy Markdown
Member Author

@cfzjywxk PTAL

@ti-chi-bot

ti-chi-bot Bot commented Jul 14, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bufferflies, cfzjywxk, JmPotato

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

The pull request process is described here

Details 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 approved lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Jul 14, 2026
@ti-chi-bot

ti-chi-bot Bot commented Jul 14, 2026

Copy link
Copy Markdown

[LGTM Timeline notifier]

Timeline:

  • 2026-07-14 06:09:42.15739795 +0000 UTC m=+693968.193492996: ☑️ agreed by JmPotato.
  • 2026-07-14 07:35:01.87832451 +0000 UTC m=+699087.914419576: ☑️ agreed by cfzjywxk.

@codecov

codecov Bot commented Jul 14, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (release-nextgen-202603@c89f0c7). Learn more about missing BASE report.

Additional details and impacted files
@@                     Coverage Diff                     @@
##             release-nextgen-202603     #69837   +/-   ##
===========================================================
  Coverage                          ?   76.1578%           
===========================================================
  Files                             ?       1936           
  Lines                             ?     540873           
  Branches                          ?          0           
===========================================================
  Hits                              ?     411917           
  Misses                            ?     128956           
  Partials                          ?          0           
Flag Coverage Δ
unit 76.1578% <ø> (?)

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

Components Coverage Δ
dumpling 61.5065% <0.0000%> (?)
parser ∅ <0.0000%> (?)
br 48.7600% <0.0000%> (?)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ti-chi-bot ti-chi-bot Bot merged commit 8c0a0f0 into pingcap:release-nextgen-202603 Jul 14, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved lgtm release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants