Skip to content

Conversation

@tdewanNvidia
Copy link
Contributor

@tdewanNvidia tdewanNvidia commented Jan 8, 2026

Description

Connection test to service should retry on 429 and 503
Issue - None

Checklist

  • I am familiar with the Contributing Guidelines.
  • New or existing tests cover these changes.
  • The documentation is up to date with these changes.

@tdewanNvidia tdewanNvidia requested a review from a team January 8, 2026 00:03
url_config.url,
status_code,
)
return None
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How is the behavior different between this and failure_status_codes since they both return None. How do we differentiate between the two to retry with this one but not with the one below?

retriable_status_codes: List[int] = pydantic.Field(
default=[429, 503], description='Status codes that should trigger retry')
failure_status_codes: List[int] = pydantic.Field(
default=[500, 501, 502, 504, 505, 506, 507, 508, 510, 511],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems kind of odd that by default this is full of 500 status codes, but down below we have

 if status_code in url_config.failure_status_codes or status_code >= 500:

This might as well default to an empty list if we always check all 500 status codes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants