pkg/util: fix panic caused by logging grpc err

[guo-shaoge]

What problem does this PR solve?

Issue Number: close #51301

Problem Summary:

What changed and how does it work?

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.

None

[tiprow]

Hi @guo-shaoge. 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 #52179 (d47a9d6) into master (ce2cf92) will decrease coverage by 17.3994%.
The diff coverage is 0.0000%.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #52179         +/-   ##
=================================================
- Coverage   69.2479%   51.8485%   -17.3994%     
=================================================
  Files          1490       1601        +111     
  Lines        420134     606090     +185956     
=================================================
+ Hits         290934     314249      +23315     
- Misses       109680     268792     +159112     
- Partials      19520      23049       +3529     

Flag	Coverage Δ
integration	20.4834% <0.0000%> (?)

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

Components	Coverage Δ
dumpling	56.2971% <ø> (ø)
parser	∅ <ø> (∅)
br	47.8341% <ø> (+1.4626%)	⬆️

[windtalker]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-03-28 06:40:57.33646173 +0000 UTC m=+2136484.358708112: ☑️ agreed by windtalker.
• 2024-03-28 07:04:32.679779423 +0000 UTC m=+2137899.702025810: ☑️ agreed by mornyx.

[mornyx]

/lgtm

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mornyx, windtalker

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 [windtalker]

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-6.5: #52185.

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

In response to a cherrypick label: new pull request could not be created: failed to create pull request against pingcap/tidb#release-7.1 from head ti-chi-bot:cherry-pick-52179-to-release-7.1: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for ti-chi-bot:cherry-pick-52179-to-release-7.1."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"}

[ti-chi-bot]

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

[ti-chi-bot]

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