fix(block): classify block I/O errors into retryable and fatal - #1896
emersonbusson wants to merge 1 commit into
Conversation
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Closed in favor of PR #2085 consolidation. |
Understood. Acknowledging that this work is now obsolete and stopping work on this task. |
Summary
Classify block I/O errors into retryable and fatal categories by defining
IoErroras an enum and mappingIoError::RetryabletoNBD_ENOSPCCommits
Issue
fix(block): classify block I/O errors into retryable and fatal
Owner
ResilienceChaos100
Labels
type: fix
area: block
Validation
Passed all tests including red_test.
Rollback trigger
Client unexpected retry loops on transient failure
PR created automatically by Jules for task 4392579080887799761 started by @emersonbusson