Skip to content

[release-21.0] fix: Fix GenerateShardRanges returning shard names that don't cover the full range (#18641)#18653

Merged
arthurschreiber merged 2 commits intorelease-21.0from
backport-18641-to-release-21.0
Sep 15, 2025
Merged

[release-21.0] fix: Fix GenerateShardRanges returning shard names that don't cover the full range (#18641)#18653
arthurschreiber merged 2 commits intorelease-21.0from
backport-18641-to-release-21.0

Conversation

@vitess-bot
Copy link
Contributor

@vitess-bot vitess-bot bot commented Sep 15, 2025

Description

This is a backport of #18641

… the full range (#18641)

Signed-off-by: Arthur Schreiber <arthur@planetscale.com>
@vitess-bot
Copy link
Contributor Author

vitess-bot bot commented Sep 15, 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.

@github-actions github-actions bot added this to the v21.0.6 milestone Sep 15, 2025
…o backport-18641-to-release-21.0

Signed-off-by: Arthur Schreiber <arthur@planetscale.com>
@codecov
Copy link

codecov bot commented Sep 15, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 67.56%. Comparing base (c896dd9) to head (0a79c3c).
⚠️ Report is 4 commits behind head on release-21.0.

Additional details and impacted files
@@               Coverage Diff                @@
##           release-21.0   #18653      +/-   ##
================================================
+ Coverage         67.54%   67.56%   +0.02%     
================================================
  Files              1572     1572              
  Lines            252478   252474       -4     
================================================
+ Hits             170532   170580      +48     
+ Misses            81946    81894      -52     

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

@arthurschreiber arthurschreiber enabled auto-merge (squash) September 15, 2025 17:23
@arthurschreiber arthurschreiber merged commit 602fbde into release-21.0 Sep 15, 2025
195 of 197 checks passed
@arthurschreiber arthurschreiber deleted the backport-18641-to-release-21.0 branch September 15, 2025 17:23
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.

1 participant