Skip to content

[release-20.0] Throttler: keep watching topo even on error (#18223)#18320

Merged
GuptaManan100 merged 1 commit intorelease-20.0from
backport-18223-to-release-20.0
Jun 18, 2025
Merged

[release-20.0] Throttler: keep watching topo even on error (#18223)#18320
GuptaManan100 merged 1 commit intorelease-20.0from
backport-18223-to-release-20.0

Conversation

@vitess-bot
Copy link
Copy Markdown
Contributor

@vitess-bot vitess-bot bot commented Jun 4, 2025

Description

This is a backport of #18223

Signed-off-by: Shlomi Noach <2607934+shlomi-noach@users.noreply.github.com>
@vitess-bot
Copy link
Copy Markdown
Contributor Author

vitess-bot bot commented Jun 4, 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 v20.0.8 milestone Jun 4, 2025
@codecov
Copy link
Copy Markdown

codecov bot commented Jun 4, 2025

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 66.41%. Comparing base (fbebdf7) to head (8dbae18).
Report is 1 commits behind head on release-20.0.

Files with missing lines Patch % Lines
go/vt/vttablet/tabletserver/throttle/throttler.go 0.00% 1 Missing ⚠️
Additional details and impacted files
@@               Coverage Diff                @@
##           release-20.0   #18320      +/-   ##
================================================
- Coverage         66.41%   66.41%   -0.01%     
================================================
  Files              1543     1543              
  Lines            244938   244938              
================================================
- Hits             162687   162680       -7     
- Misses            82251    82258       +7     

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

@GuptaManan100 GuptaManan100 mentioned this pull request Jun 18, 2025
30 tasks
@GuptaManan100 GuptaManan100 merged commit 83e05b5 into release-20.0 Jun 18, 2025
193 of 194 checks passed
@GuptaManan100 GuptaManan100 deleted the backport-18223-to-release-20.0 branch June 18, 2025 05:37
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