tables: fix resp is nil and change resp check

[HuSharp]

What problem does this PR solve?

Issue Number: close #52034

Problem Summary:

What changed and how does it work?

check resp is nil

Check List

Tests

• Unit test
• Integration test
• No need to test

  • I checked and no code files have been changed.

Release note

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

None

[tiprow]

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

[codecov]

Codecov Report

Merging #52035 (a5e0a29) into master (07ef009) will decrease coverage by 15.9868%.
Report is 11 commits behind head on master.
The diff coverage is 100.0000%.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #52035         +/-   ##
=================================================
- Coverage   70.6719%   54.6852%   -15.9868%     
=================================================
  Files          1481       1592        +111     
  Lines        439242     610029     +170787     
=================================================
+ Hits         310421     333596      +23175     
- Misses       109308     253250     +143942     
- Partials      19513      23183       +3670     

Flag	Coverage Δ
integration	36.7583% <100.0000%> (?)
unit	70.4680% <100.0000%> (-0.0188%)	⬇️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	51.2616% <ø> (+5.4331%)	⬆️

[JmPotato]

Could you please attach the manual test result also?

[HuSharp]

Could you please attach the manual test result also?

Test by these steps as mentioned in issue cc @mayjiang0203

step 1. down dc2 to make dr cluster change to async mode;
step 2. check table information_schema.cluster_info;

Can you add label for issue as well :)

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-03-25 02:58:28.892317528 +0000 UTC m=+1863935.914563911: ☑️ agreed by JmPotato.
• 2024-03-25 03:16:39.777501215 +0000 UTC m=+1865026.799747597: ☑️ agreed by xhebox.

[HuSharp]

/check-issue-triage-complete

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JmPotato, tangenta, xhebox

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:

• pkg/infoschema/OWNERS [tangenta]

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]

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