forked from molecule-ai/molecule-core
edcac16b81
Second related E2E bug, surfaced after #2066's instance_status fix let the harness reach the TLS readiness step: Error: tenant TLS: timed out after 180s The CP provisioner writes staging tenant DNS as <slug>.staging.moleculesai.app (with the staging. subdomain prefix — visible in the EC2 provisioner DNS log line). The harness was building https://<slug>.moleculesai.app (prod-zone shape), so DNS literally didn't resolve, fetch threw NXDOMAIN inside the silent catch, and waitFor saw null on every 5s poll until 180s elapsed. Fix: parameterize as STAGING_TENANT_DOMAIN env var, default staging.moleculesai.app. Doc-comment example updated to match. Override hatch is there only for ops running this harness against a non-default zone. Verified manually: a freshly-provisioned tenant (e2e-canvas-20260425-sav9fe) was unreachable at the prod-shaped URL (NXDOMAIN) but reached CF at the staging-shaped URL. teardown.ts only hits CP, not the tenant URL — no fix needed there. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| e2e | ||
| public | ||
| src | ||
| .env.example | ||
| .gitignore | ||
| components.json | ||
| Dockerfile | ||
| next.config.ts | ||
| package-lock.json | ||
| package.json | ||
| playwright.config.ts | ||
| playwright.staging.config.ts | ||
| postcss.config.js | ||
| tailwind.config.ts | ||
| tsconfig.json | ||
| vitest.config.ts | ||