Skip to content

[release-20.0] make sure to give MEMBER OF the correct precedence (#18237)#18243

Merged
systay merged 1 commit intorelease-20.0from
backport-18237-to-release-20.0
May 8, 2025
Merged

[release-20.0] make sure to give MEMBER OF the correct precedence (#18237)#18243
systay merged 1 commit intorelease-20.0from
backport-18237-to-release-20.0

Conversation

@vitess-bot
Copy link
Copy Markdown
Contributor

@vitess-bot vitess-bot bot commented May 7, 2025

Description

This is a backport of #18237

@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 May 7, 2025
@vitess-bot
Copy link
Copy Markdown
Contributor Author

vitess-bot bot commented May 7, 2025

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 18243 -R vitessio/vitess
git reset --hard origin/release-20.0
git cherry-pick -m 1 d0176be34a0cc2b24c84f7454a04d013aa9fbe55

@vitess-bot
Copy link
Copy Markdown
Contributor Author

vitess-bot bot commented May 7, 2025

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.

@vitess-bot vitess-bot bot requested a review from systay May 7, 2025 06:33
@github-actions github-actions bot added this to the v20.0.8 milestone May 7, 2025
@systay systay removed Skip CI Skip CI actions from running Merge Conflict labels May 7, 2025
@systay systay marked this pull request as ready for review May 7, 2025 06:37
Signed-off-by: Andres Taylor <andres@planetscale.com>
@systay systay force-pushed the backport-18237-to-release-20.0 branch from 376a048 to a89be0a Compare May 7, 2025 06:53
@codecov
Copy link
Copy Markdown

codecov bot commented May 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.41%. Comparing base (20c989e) to head (a89be0a).
Report is 4 commits behind head on release-20.0.

Additional details and impacted files
@@               Coverage Diff                @@
##           release-20.0   #18243      +/-   ##
================================================
+ Coverage         66.38%   66.41%   +0.03%     
================================================
  Files              1543     1543              
  Lines            244886   244884       -2     
================================================
+ Hits             162572   162646      +74     
+ Misses            82314    82238      -76     

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

🚀 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.

@systay systay merged commit 4bd42e8 into release-20.0 May 8, 2025
185 of 186 checks passed
@systay systay deleted the backport-18237-to-release-20.0 branch May 8, 2025 05:09
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.

2 participants