external: improve S3 error message

[lance6716]

What problem does this PR solve?

Issue Number: close #59326

Problem Summary:

What changed and how does it work?

simply use %s instead of %v when printf

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 @lance6716. 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

Attention: Patch coverage is 46.66667% with 8 lines in your changes missing coverage. Please review.

Project coverage is 74.9962%. Comparing base (4734c9c) to head (a1f6cb8).
Report is 323 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #59327        +/-   ##
================================================
+ Coverage   73.0474%   74.9962%   +1.9487%     
================================================
  Files          1689       1736        +47     
  Lines        467010     475785      +8775     
================================================
+ Hits         341139     356821     +15682     
+ Misses       104891      96584      -8307     
- Partials      20980      22380      +1400     

Flag	Coverage Δ
integration	48.7570% <0.0000%> (?)
unit	72.5935% <46.6666%> (+0.0561%)	⬆️

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

Components	Coverage Δ
dumpling	44.7619% <ø> (∅)
parser	∅ <ø> (∅)
br	62.2414% <46.6666%> (+15.4051%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[zimulala]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, zimulala

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:

• br/pkg/storage/OWNERS [D3Hunter]

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:

• 2025-02-08 02:33:15.059846882 +0000 UTC m=+64637.456068940: ☑️ agreed by D3Hunter.
• 2025-02-08 02:50:19.124197223 +0000 UTC m=+65661.520419285: ☑️ agreed by zimulala.

[ti-chi-bot]

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

[ti-chi-bot]

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

[GMHDBJD]

/cherry-pick release-8.1

[GMHDBJD]

/cherry-pick release-8.5

[ti-chi-bot]

@GMHDBJD: new pull request created to branch release-8.1: #62062.

In response to this:

/cherry-pick release-8.1

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 ti-community-infra/tichi repository.

[ti-chi-bot]

@GMHDBJD: new pull request could not be created: failed to create pull request against pingcap/tidb#release-8.5 from head ti-chi-bot:cherry-pick-59327-to-release-8.5: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between pingcap:release-8.5 and ti-chi-bot:cherry-pick-59327-to-release-8.5"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to this:

/cherry-pick release-8.5

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 ti-community-infra/tichi repository.

[GMHDBJD]

/cherry-pick release-8.1

[ti-chi-bot]

@GMHDBJD: new pull request could not be created: failed to create pull request against pingcap/tidb#release-8.1 from head ti-chi-bot:cherry-pick-59327-to-release-8.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-59327-to-release-8.1."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to this:

/cherry-pick release-8.1

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 ti-community-infra/tichi repository.