Skip to content

fix(api): read the engine timeout from DFE_ENGINE_TIMEOUT_MS - #204

Merged
catinspace-au merged 1 commit into
mainfrom
fix/h16-engine-timeout
Nov 11, 2026
Merged

catinspace-au merged 1 commit into
mainfrom
fix/h16-engine-timeout

Conversation

@catinspace-au

@catinspace-au catinspace-au commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

engine-session, org-connection and query-export each declared ENGINE_TIMEOUT_MS = 5000. They now read DFE_ENGINE_TIMEOUT_MS from dfe/config.ts.

  • The value is whole milliseconds above zero, default 5000. Anything else stops the API starting, like DFE_AUTH_MODE.
  • All changes are under dfe/. No upstream file is touched. .fork-surface is unchanged.

Done when: config.test.ts tests parsing, each of the three call sites tests the configured value on AbortSignal.timeout, and eslint and tsc pass.

The config, org-connection, engine-session and query-export suites pass on the rebased branch (154 tests).

Base automatically changed from fix/org-connection-engine-names to main November 11, 2026 06:46
engine-session, org-connection and query-export now read one config value instead of each holding ENGINE_TIMEOUT_MS = 5000.

DFE_ENGINE_TIMEOUT_MS sets the timeout in whole milliseconds above zero. The default is 5000. An invalid set value stops the API starting.

All changes are under dfe/. No upstream files change. The branch is based on fix/org-connection-engine-names because both edit org-connection.ts.
@catinspace-au
catinspace-au marked this pull request as ready for review November 11, 2026 08:22
@catinspace-au
catinspace-au merged commit 1d09f72 into main Nov 11, 2026
34 checks passed
@catinspace-au
catinspace-au deleted the fix/h16-engine-timeout branch November 11, 2026 08:22
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