make failed availability check apply in the same request #56255
Merged
AndyScherzinger merged 2 commits intomasterfrom Nov 12, 2025
Merged
make failed availability check apply in the same request #56255AndyScherzinger merged 2 commits intomasterfrom
AndyScherzinger merged 2 commits intomasterfrom
Conversation
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
icewind1991
requested review from
ArtificialOwl,
CarlSchwan,
leftybournes and
yemkareems
and removed request for
a team
Member
Author
|
/backport to stable32 |
Member
Author
|
/backport to stable31 |
salmart-dev
reviewed
Nov 12, 2025
provokateurin
approved these changes
Nov 12, 2025
salmart-dev
approved these changes
Nov 12, 2025
This was referenced Nov 12, 2025
Merged
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
4 participants
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.
Currently, marking the storage as available won't be noticed by the availability wrapper until the next request.
This can lead to issues as some request can have a high number of storage calls, and repeated failures can lead to things like the instance being bruteforce protected.