fix-qcloud-cos-retryable-status - #24999
Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
XuPeng-SH
left a comment
There was a problem hiding this comment.
Requesting changes for one retry-classification gap.
This PR adds COS-specific retry handling for 429 / 502 / 503 / 504, but it still leaves 500 Internal Server Error non-retryable. Since MatrixOne routes QCloud operations through DoWithRetry(..., IsRetryableError), that means transient COS 500s will still fail immediately instead of retrying.
I think http.StatusInternalServerError should be included in the retryable COS status set, and the new status-based test should cover 500 as well.
Merge Queue Status
This pull request spent 1 hour 25 minutes 30 seconds in the queue, with no time running CI. Waiting for
All conditions
ReasonThe pull request #24999 has been manually updated Failing checks:
HintIf you want to requeue this pull request, you can post a |
fcd1480 to
71ce0f7
Compare
Merge Queue Status
This pull request spent 1 hour 1 minute 35 seconds in the queue, with no time running CI. Waiting for
All conditions
ReasonThe merge conditions cannot be satisfied due to failing checks Failing checks:
HintYou may have to fix your CI before adding the pull request to the queue again. |
Merge Queue Status
This pull request spent 1 hour 3 minutes 53 seconds in the queue, including 1 hour 3 minutes 32 seconds running CI. Required conditions to merge
|
What type of PR is this?
Which issue(s) this PR fixes:
issue #24998
What this PR does / why we need it:
Fix qcloud cos retryable status