Skip to content

Extend retries to 5xx and 408#5364

Merged
denik merged 4 commits into
mainfrom
denik/retries-more
Jun 1, 2026
Merged

Extend retries to 5xx and 408#5364
denik merged 4 commits into
mainfrom
denik/retries-more

Conversation

@denik
Copy link
Copy Markdown
Contributor

@denik denik commented May 28, 2026

Follow up to #5349

Analysis shows 500 and 408 errors show up as well (although what we saw is those errors happen during file upload, but no reason it cannot happen on other endpoints).

@denik denik marked this pull request as ready for review May 28, 2026 11:23
@denik denik temporarily deployed to test-trigger-is May 28, 2026 11:23 — with GitHub Actions Inactive
@denik denik temporarily deployed to test-trigger-is May 28, 2026 11:23 — with GitHub Actions Inactive
@denik denik temporarily deployed to test-trigger-is May 28, 2026 11:25 — with GitHub Actions Inactive
@denik denik temporarily deployed to test-trigger-is May 28, 2026 11:25 — with GitHub Actions Inactive
@eng-dev-ecosystem-bot
Copy link
Copy Markdown
Collaborator

eng-dev-ecosystem-bot commented May 28, 2026

Commit: 18476af

Run: 26756445355

denik added 3 commits June 1, 2026 10:26
…both retried

The condition `StatusCode >= 500 && StatusCode == 408` is logically
impossible (no code can satisfy both). Using `||` lets both 5xx errors
and 408 Request Timeout trigger the retry path, which is the intended
behaviour from the parent commit.

Co-authored-by: Isaac
@denik denik force-pushed the denik/retries-more branch from d044d1e to cbe3ea7 Compare June 1, 2026 08:28
@denik denik temporarily deployed to test-trigger-is June 1, 2026 08:29 — with GitHub Actions Inactive
@denik denik temporarily deployed to test-trigger-is June 1, 2026 08:29 — with GitHub Actions Inactive
@denik denik enabled auto-merge June 1, 2026 09:00
@denik denik added this pull request to the merge queue Jun 1, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to a conflict with the base branch Jun 1, 2026
@denik denik temporarily deployed to test-trigger-is June 1, 2026 13:00 — with GitHub Actions Inactive
@denik denik temporarily deployed to test-trigger-is June 1, 2026 13:00 — with GitHub Actions Inactive
@denik denik merged commit cf28cd2 into main Jun 1, 2026
22 of 23 checks passed
@denik denik deleted the denik/retries-more branch June 1, 2026 13:57
@eng-dev-ecosystem-bot
Copy link
Copy Markdown
Collaborator

Commit: cf28cd2

Run: 26759551706

deco-sdk-tagging Bot added a commit that referenced this pull request Jun 4, 2026
## Release v1.2.0

### CLI
* `experimental open` now opens every DABs resource type that has a workspace URL, picking up `catalogs`, `schemas`, `volumes`, `database_instances`, `database_catalogs`, `synced_database_tables`, `postgres_catalogs`, `postgres_synced_tables`, `quality_monitors`, `vector_search_endpoints`, and `vector_search_indexes` ([#5346](#5346)).

### Bundles
* Retry transient HTTP 5xx and 408 errors in direct deployment engine ([#5349](#5349), [#5364](#5364)).
* Preserve `.designer.ipynb` suffix when translating notebook task paths so Lakeflow Designer files referenced from a `notebook_task` resolve correctly in the workspace ([#5370](#5370)).
* Fix script output dropping last line without trailing newline ([#4995](#4995)).
* engine/direct: Add `--select` flag to `bundle plan` and `bundle deploy` to plan/deploy a subset of resources (e.g. `--select my_job` or `--select jobs.my_job`); resources referenced by the selection are included transitively ([#5413](#5413)).
* Support `purge_on_delete: true` on `postgres_projects` so bundles can hard-delete a Lakebase project on destroy (skipping the soft-delete retention window) ([#5414](#5414)).
* Support terraform references in direct engine ([#5392](#5392))
* Support lifecycle.started for SQL warehouses ([#5348](#5348))

### Dependency updates
* Bump Go toolchain to 1.26.4 ([#5420](#5420)).
* Bump `github.com/databricks/databricks-sdk-go` from v0.136.0 to v0.141.0 ([#5361](#5361))
* Bump Terraform provider from v1.115.0 to v1.117.0 ([#5421](#5421))
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.

3 participants