*: bump client-go to fix correctness issue of membuffer snapshot read

[you06]

What problem does this PR solve?

Issue Number: close #54929

Problem Summary:

What changed and how does it work?

Fix the issue that mem buffer don't bypass the staging data when doing snapshot read and add a regression test.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• 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.

Fix a bug that mem buffer's snapshot can read staging data.

[tiprow]

Hi @you06. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.7982%. Comparing base (3464dae) to head (6b3baec).
Report is 476 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #55547        +/-   ##
================================================
+ Coverage   74.8392%   75.7982%   +0.9590%     
================================================
  Files          1576       1582         +6     
  Lines        365764     454500     +88736     
================================================
+ Hits         273735     344503     +70768     
- Misses        72274      89890     +17616     
- Partials      19755      20107       +352     

Flag	Coverage Δ
integration	50.4143% <ø> (?)
unit	72.9551% <ø> (-0.8560%)	⬇️

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

Components	Coverage Δ
dumpling	52.9567% <ø> (-2.2327%)	⬇️
parser	∅ <ø> (∅)
br	52.5810% <ø> (+4.8213%)	⬆️

[you06]

/retest

[tiprow]

@you06: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cfzjywxk, zyguan

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:

• OWNERS [cfzjywxk,zyguan]

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]

[LGTM Timeline notifier]

Timeline:

• 2024-08-23 06:09:31.695724786 +0000 UTC m=+504966.830174901: ☑️ agreed by cfzjywxk.
• 2024-08-23 06:24:47.064133903 +0000 UTC m=+505882.198584024: ☑️ agreed by zyguan.

[you06]

/retest

[tiprow]

@you06: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[you06]

/ok-to-test

[you06]

/test fast_test_tiprow

[ti-chi-bot]

@you06: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test build
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test pull-br-integration-test
• /test pull-integration-ddl-test
• /test pull-lightning-integration-test
• /test pull-mysql-client-test
• /test unit-test

The following commands are available to trigger optional jobs:

• /test canary-notify-when-compatibility-sections-changed
• /test pingcap/tidb/canary_ghpr_unit_test
• /test pull-common-test
• /test pull-e2e-test
• /test pull-integration-common-test
• /test pull-integration-copr-test
• /test pull-integration-jdbc-test
• /test pull-integration-mysql-test
• /test pull-integration-nodejs-test
• /test pull-sqllogic-test
• /test pull-tiflash-test

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/ghpr_build
• pingcap/tidb/ghpr_check
• pingcap/tidb/ghpr_check2
• pingcap/tidb/ghpr_mysql_test
• pingcap/tidb/ghpr_unit_test
• pingcap/tidb/pull_integration_ddl_test
• pingcap/tidb/pull_mysql_client_test

In response to this:

/test fast_test_tiprow

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/test-infra repository.

[you06]

/retest

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #55626.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #56280.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #56906.