Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a default for retry after #371

Merged
merged 2 commits into from
Mar 14, 2024
Merged

Add a default for retry after #371

merged 2 commits into from
Mar 14, 2024

Conversation

benc-db
Copy link
Collaborator

@benc-db benc-db commented Mar 14, 2024

If we get a 503 without a Retry-After, it can indicate that nginx was responding while app was starting up / shutting down, and may not have a Retry-After set. This causes the connector to bail, which is problematic for dependent projects such as dbt-databricks. Apologies for the autoformat, the only real change is on lines 366-367.

Signed-off-by: Ben Cassell <ben.cassell@databricks.com>
Signed-off-by: Ben Cassell <ben.cassell@databricks.com>
@benc-db benc-db merged commit f85e903 into main Mar 14, 2024
13 checks passed
benc-db added a commit that referenced this pull request Mar 19, 2024
* Add a default for retry after
Signed-off-by: Ben Cassell <ben.cassell@databricks.com>

* Applied black formatter
Signed-off-by: Ben Cassell <ben.cassell@databricks.com>
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.

2 participants