Skip to content

fix: harden production deploy smoke coverage#1523

Open
Sheygoodbai wants to merge 1 commit intoopenclaw:mainfrom
Sheygoodbai:codex/harden-prod-smoke-coverage
Open

fix: harden production deploy smoke coverage#1523
Sheygoodbai wants to merge 1 commit intoopenclaw:mainfrom
Sheygoodbai:codex/harden-prod-smoke-coverage

Conversation

@Sheygoodbai
Copy link
Copy Markdown

Summary

  • add prod HTTP smoke to the deploy workflow before UI smoke
  • include signed-out publish/import smoke coverage in production UI checks
  • make prod HTTP smoke retry on transient rate-limit responses and align upload gating assertions with the live redirect flow

Verification

  • CLAWHUB_E2E_SITE=https://clawhub.ai bun run test:e2e:prod-http
  • PLAYWRIGHT_BASE_URL=https://clawhub.ai bunx playwright test e2e/menu-smoke.pw.test.ts e2e/publish-entry-workflows.pw.test.ts e2e/upload-auth-smoke.pw.test.ts --reporter=list

@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Apr 4, 2026

@Sheygoodbai is attempting to deploy a commit to the 0xBuns Team on Vercel.

A member of the Team first needs to authorize it.

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Apr 4, 2026

Greptile Summary

This PR hardens the production deploy pipeline by inserting an HTTP smoke step before the UI smoke, adding 429-retry logic with header-aware back-off, memoizing the skill-detail API call across tests, and extending the Playwright suite with signed-out publish/import coverage. The /upload test assertion is also aligned with the live redirect-to-/publish-skill flow.

Confidence Score: 5/5

PR is safe to merge; all findings are minor style suggestions.

The only finding is unreachable dead code in the fetchWithRetry post-loop block — a cleanup-only concern with zero effect on correctness or reliability. All other changes are straightforward smoke-coverage improvements.

No files require special attention.

Prompt To Fix All With AI
This is a comment left during a code review.
Path: e2e/prod-http-smoke.e2e.test.ts
Line: 81-85

Comment:
**Unreachable dead code after loop**

The `if (!lastResponse)` guard and `return lastResponse` are unreachable. On the final iteration (`attempt === MAX_RATE_LIMIT_RETRIES - 1`), line 76 always `return`s the 429 response before the `for` loop can exit naturally, so execution never reaches line 81. The post-loop block can be safely removed.

How can I resolve this? If you propose a fix, please make it concise.

Reviews (1): Last reviewed commit: "fix: harden production deploy smoke cove..." | Re-trigger Greptile

Comment on lines +81 to +85
if (!lastResponse) {
throw new Error("Expected a response while retrying rate-limited request.");
}

return lastResponse;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P2 Unreachable dead code after loop

The if (!lastResponse) guard and return lastResponse are unreachable. On the final iteration (attempt === MAX_RATE_LIMIT_RETRIES - 1), line 76 always returns the 429 response before the for loop can exit naturally, so execution never reaches line 81. The post-loop block can be safely removed.

Prompt To Fix With AI
This is a comment left during a code review.
Path: e2e/prod-http-smoke.e2e.test.ts
Line: 81-85

Comment:
**Unreachable dead code after loop**

The `if (!lastResponse)` guard and `return lastResponse` are unreachable. On the final iteration (`attempt === MAX_RATE_LIMIT_RETRIES - 1`), line 76 always `return`s the 429 response before the `for` loop can exit naturally, so execution never reaches line 81. The post-loop block can be safely removed.

How can I resolve this? If you propose a fix, please make it concise.

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.

1 participant