Repository navigation
release: v1.0.0-alpha.26 - #64
Merged
Merged
Conversation
…migrations) - App and worker container env vars all set (checked by name only) - Public runtime config reached client (NUXT_PUBLIC_SUPABASE_URL in HTML) - Storage buckets contracts and analysis-pdfs both exist, both private - All 22 repo migrations recorded in production _migrations table, 0 pending
- Task 2: Carlos confirmed QA account provisioned, logged into connected Chrome profile; declined to create the credentials file, so AUTH_MODE=browser (the plan's own anticipated fallback) is used - Task 3 step 1: public SUPABASE_URL/SUPABASE_ANON_KEY extracted from the production homepage (no login needed) and written to ~/.config/clarify-qa/phase13-ids (mode 600, values not echoed) - Task 3 steps 2-8 blocked: AUTH_MODE=browser requires driving the existing authenticated Chrome tab via mcp__claude-in-chrome__* tools, which are not part of this gsd-executor subagent's tool set (confirmed via the claude-in-chrome skill this session) — no job submitted, no file uploaded, no credits spent; continuation needed from a context with browser tool access
release: v1.0.0-alpha.25
…iling Two consecutive Forensic-tier analyses failed in production with "Request timed out" — but both took ~15 minutes to surface the error, not the configured 10-minute timeout. The OpenAI SDK defaults to 2 automatic retries on failure (including timeout), and each retry re-waits the full configured timeout, turning a single 10-minute ceiling into an unbounded multiplier for a request that's already the most expensive one this app makes (120k input / 30k output tokens, gpt-6-astra). Sets maxRetries: 0 so the configured timeout is a real wall-clock ceiling, and raises the forensic timeout to 12 minutes (queue/worker job timeouts raised to 13 minutes to stay above it) — a request this large may legitimately need more headroom than 10 minutes even on a single clean attempt, and retries provide little value for a non-idempotent, expensive generation call anyway. Verified locally: image builds successfully with the change.
fix(worker): disable OpenAI retry, raise forensic timeout
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixed
Deploy notes
Sixth same-day-adjacent hotfix, following v1.0.0-alpha.20 through v1.0.0-alpha.25.