Skip to content

troubleshoot-tidb-cluster: fix TiDB error message text - #23621

Open
yahonda wants to merge 1 commit into
masterfrom
fix-en-information-schema-error-text
Open

troubleshoot-tidb-cluster: fix TiDB error message text#23621
yahonda wants to merge 1 commit into
masterfrom
fix-en-information-schema-error-text

Conversation

@yahonda

@yahonda yahonda commented Aug 27, 2026

Copy link
Copy Markdown
Member

What is changed, added or deleted? (Required)

Found while reviewing a Japanese translation fix (CodeRabbit review on #23618): troubleshoot-tidb-cluster.md says the error message is InformationSchema is out of date (one word), but this doesn't match the actual TiDB error text.

Verified against ErrInfoSchemaExpired in pingcap/tidb:

https://github.com/pingcap/tidb/blob/1f9469913409f0c6bf4a946c51948ebdfc2d2bb8/pkg/errno/errname.go#L991

ErrInfoSchemaExpired: mysql.Message("Information schema is out of date: schema failed to update in 1 lease, please make sure TiDB can connect to TiKV", nil),

The correct text is Information schema is out of date (with a space between "Information" and "schema"), matching 7 other occurrences of this string elsewhere in this same docs corpus (faq/sql-faq.md, several releases/*.md files, tidb-troubleshooting-map.md). Only this one file had the wrong spelling.

Which TiDB version(s) do your changes apply to? (Required)

  • master

What is the related PR or file link(s)?

AI agent involvement

  • The changes in this PR were primarily made by an AI agent on behalf of the PR author.

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

The correct error text (per pkg/errno/errname.go's ErrInfoSchemaExpired
in pingcap/tidb) is "Information schema is out of date" with a space
between "Information" and "schema", not "InformationSchema" as one word.
@coderabbitai

coderabbitai Bot commented Aug 27, 2026

Copy link
Copy Markdown

Warning

Review limit reached

Next included review available in 31 minutes.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 91c02ec3-cab5-4274-b32f-eeab9c117868

📥 Commits

Reviewing files that changed from the base of the PR and between ff98075 and 14bd773.

📒 Files selected for processing (1)
  • troubleshoot-tidb-cluster.md

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 added the missing-translation-status This PR does not have translation status info. label Aug 27, 2026
@ti-chi-bot

ti-chi-bot Bot commented Aug 27, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jackysp for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found 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 the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Aug 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

missing-translation-status This PR does not have translation status info. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant