-
Notifications
You must be signed in to change notification settings - Fork 701
hardware-and-software-requirements: Add note about supported filesystems (#21379) #21392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hardware-and-software-requirements: Add note about supported filesystems (#21379) #21392
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @ti-chi-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request primarily enhances the TiDB documentation by adding critical information regarding supported file systems for production deployments. It also refines the terminology used for storage requirements, improving the clarity and accuracy of the hardware and software specifications.
Highlights
- Documentation Update: Added a specific note to the
hardware-and-software-requirements.md
file, clarifying that TiDB officially supports XFS and Ext4 file systems, and advises against using others for production environments. - Terminology Refinement: Updated all instances of "Disk space requirements" to "Storage requirements" within the
hardware-and-software-requirements.md
document, including table headers and section titles, for improved clarity and consistency. - Linter Configuration: Added a new URL to the
.lycheeignore
file, likely to prevent link checker warnings for a newly referenced external resource.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request updates the documentation to include a note about supported file systems and changes 'Disk space requirements' to 'Storage requirements' for better consistency. The file system note has been updated to improve clarity and adhere to the style guide, and terminology consistency has been checked.
@@ -288,6 +288,8 @@ As an open-source distributed SQL database, TiDB requires the following network | |||
</tbody> | |||
</table> | |||
|
|||
TiDB supports the XFS and Ext4 file systems. Other file systems are not recommended for production environments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The note about supported file systems can be improved for clarity and adherence to the style guide1. Specifically, file system names should be enclosed in backticks, and the recommendation should directly state why other file systems are not advised.
Style Guide References
TiDB supports the XFS and Ext4 file systems. Other file systems are not recommended for production environments. | |
TiDB supports the `XFS` and `Ext4` file systems. Using other file systems in production environments is not recommended because they may impact stability and performance. |
Footnotes
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qiancai 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:
Approvers can indicate their approval by writing |
This is an automated cherry-pick of #21379
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?