Skip to content
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

[release-20.0] bugfix: treat EXPLAIN like SELECT (#17054) #17057

Merged
merged 1 commit into from
Oct 25, 2024

Conversation

vitess-bot[bot]
Copy link
Contributor

@vitess-bot vitess-bot bot commented Oct 23, 2024

Description

This is a backport of #17054

@vitess-bot vitess-bot bot added Backport This is a backport Component: Query Serving Merge Conflict Skip CI Skip CI actions from running Type: Bug labels Oct 23, 2024
Copy link
Contributor Author

vitess-bot bot commented Oct 23, 2024

Hello @systay, there are conflicts in this backport.

Please address them in order to merge this Pull Request. You can execute the snippet below to reset your branch and resolve the conflict manually.

Make sure you replace origin by the name of the vitessio/vitess remote

git fetch --all
gh pr checkout 17057 -R vitessio/vitess
git reset --hard origin/release-20.0
git cherry-pick -m 1 11a655ca06a7add5b9184a9830bc5dea1f987cb7

Copy link
Contributor Author

vitess-bot bot commented Oct 23, 2024

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

  • Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

  • Apply the release notes (needs details) label if users need to know about this change.
  • New features should be documented.
  • There should be some code comments as to why things are implemented the way they are.
  • There should be a comment at the top of each new or modified test to explain what the test does.

New flags

  • Is this flag really necessary?
  • Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
  • vtctl command output order should be stable and awk-able.

@github-actions github-actions bot added this to the v20.0.3 milestone Oct 23, 2024
@systay systay removed Skip CI Skip CI actions from running Merge Conflict labels Oct 25, 2024
@systay systay marked this pull request as ready for review October 25, 2024 11:02
@systay systay force-pushed the backport-17054-to-release-20.0 branch from bc43b48 to 679b17e Compare October 25, 2024 11:05
Copy link

codecov bot commented Oct 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.40%. Comparing base (d374ace) to head (679b17e).
Report is 3 commits behind head on release-20.0.

Additional details and impacted files
@@               Coverage Diff                @@
##           release-20.0   #17057      +/-   ##
================================================
- Coverage         66.40%   66.40%   -0.01%     
================================================
  Files              1541     1541              
  Lines            243942   243973      +31     
================================================
+ Hits             161991   162003      +12     
- Misses            81951    81970      +19     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@harshit-gangal harshit-gangal merged commit 2043068 into release-20.0 Oct 25, 2024
185 checks passed
@harshit-gangal harshit-gangal deleted the backport-17054-to-release-20.0 branch October 25, 2024 12:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants