-
Notifications
You must be signed in to change notification settings - Fork 702
v6.0.0 release notes: update the description of "setting incorrect values for system variables" (#20768) #20774
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
v6.0.0 release notes: update the description of "setting incorrect values for system variables" (#20768) #20774
Conversation
…lues for system variables"
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.
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!
Summary of Changes
This pull request updates the release notes for TiDB v6.0.0-dmr.md. Specifically, it clarifies the behavior of TiDB regarding incorrect values for system variables across different versions. The change modifies the description to indicate that TiDB allowed incorrect values for some noop system variables in v5.4 and earlier, but disallows this behavior starting from v6.0.0.
Highlights
- Release Notes Update: The release notes for v6.0.0 are updated to clarify the behavior change regarding incorrect system variable values.
- System Variable Validation: TiDB now enforces correct values for system variables starting from v6.0.0, while earlier versions (v5.4 and prior) permitted incorrect values for some noop system variables.
Changelog
- releases/release-6.0.0-dmr.md
- Modified the description of the system variable validation behavior to include versions prior to v5.4.
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.
A version's tale,
Variables now prevail,
Six point oh's rule,
No more values cruel,
Correctness will not fail.
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
The pull request updates the description of "setting incorrect values for system variables" in the release notes for TiDB v6.0.0. The change clarifies the versions affected by this behavior. The pull request includes changes to the releases/release-6.0.0-dmr.md
file.
Merge Readiness
The pull request consists of a small documentation update. The change is straightforward and seems correct. The pull request is ready to be merged.
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Oreoxmt 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 #20768
…lues for system variables"
First-time contributors' checklist
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?