Skip to content

fix(template-manager): handle error gracefully if metadata already exists#2130

Merged
jakubno merged 9 commits intomainfrom
fix/handle-rate-limit-error
Mar 20, 2026
Merged

fix(template-manager): handle error gracefully if metadata already exists#2130
jakubno merged 9 commits intomainfrom
fix/handle-rate-limit-error

Conversation

@jakubno
Copy link
Copy Markdown
Member

@jakubno jakubno commented Mar 13, 2026

Note

Medium Risk
Changes storage write error handling to treat GCS ResourceExhausted as a special rate-limit case and skip layer-metadata writes in that scenario, which could mask unexpected storage failures if misclassified.

Overview
Improves resilience when multiple builds race to write the same content-addressed layer metadata by detecting GCS per-object mutation rate limiting (ResourceExhausted) as storage.ErrObjectRateLimited and having the layer build executor skip the metadata write (with a warning) instead of failing the build.

Written by Cursor Bugbot for commit fbbea63. This will update automatically on new commits. Configure here.

@jakubno jakubno marked this pull request as ready for review March 20, 2026 09:15
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 33dcc86c7e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@jakubno jakubno force-pushed the fix/handle-rate-limit-error branch 2 times, most recently from a17b6ff to 59a4556 Compare March 20, 2026 11:29
@jakubno jakubno force-pushed the fix/handle-rate-limit-error branch from 59a4556 to cd9b4ae Compare March 20, 2026 11:30
Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

@jakubno jakubno enabled auto-merge (squash) March 20, 2026 14:04
@jakubno jakubno merged commit 70213ce into main Mar 20, 2026
35 checks passed
@jakubno jakubno deleted the fix/handle-rate-limit-error branch March 20, 2026 14:16
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