mirror of
https://github.com/AmruthPillai/Reactive-Resume.git
synced 2026-10-03 10:13:47 +10:00
Santhi PrakashandAmruth Pillai
861ba8bf60
* fix(ai): make provider test timeout configurable via AI_TEST_TIMEOUT_MS - Problem: the 30s hardcoded timeout is too short for self-hosted deployments with cold-start models (e.g. Ollama). Makes it impossible to pass the provider test (issue #3374). - Fix: read AI_TEST_TIMEOUT_MS from the environment, defaulting to 30_000. Zero behaviour change when the env var is absent. - Verification: existing test asserts "30 seconds" in the timeout message; default is unchanged so the test continues to pass. (CI needs Node 22+ — not available on this host.) * fix(ai): add AI_TEST_TIMEOUT_MS to turbo globalEnv so it reaches the API process - Problem: Turborepo filters env vars not listed in globalEnv, so AI_TEST_TIMEOUT_MS would always be undefined at runtime under turbo dev/start, making the override dead code. - Fix: add AI_TEST_TIMEOUT_MS to the globalEnv array. - Verification: turbo.json validates as valid JSON. * fix(ai): validate AI_TEST_TIMEOUT_MS as a finite non-negative integer * docs(ai): add JSDoc to timeout parser and test helper * test(ai): restore AI_TEST_TIMEOUT_MS after timeout tests - Problem: loadWithTimeout() mutates process.env.AI_TEST_TIMEOUT_MS but nothing restores it, so the last value tested ("999999999999") leaked to every test that runs after this describe block in the same file. - Fix: save the pre-test value and restore it in an afterEach hook. - Verification: pnpm exec vitest run src/features/ai/service.test.ts in packages/api — 18/18 passed. * test(api): isolate AI timeout environment cases --------- Co-authored-by: Amruth Pillai <im.amruth@gmail.com>