Repository navigation
build(deps): Bump bigtable_rs to warm every channel - #733
Merged
Merged
Conversation
Co-Authored-By: Lorenzo Cian <17258265+lcian@users.noreply.github.com>
lcian
approved these changes
Oct 23, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #733 +/- ##
=======================================
Coverage 91.91% 91.91%
=======================================
Files 117 117
Lines 24141 24141
=======================================
+ Hits 22188 22189 +1
+ Misses 1953 1952 -1
☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
jan-auer
approved these changes
Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps bigtable_rs to getsentry/bigtable_rs#14. With this version, the background PingAndWarm goes to every channel in the pool on each 10s tick. Before, it went through the load balancer, so it could skip channels.
This matters now because single tenants move from 1 to 4 channels in getsentry/ops#24624. Each channel must stay warm so a retry can use it.
via @lcian.
--
View Junior Session [Sentry]