Thejesh Reddy 9cad956cc9 fix(portals): add a 15s request timeout to every board fetch (#197) ...

None of the board CLIs set a fetch timeout, and the retry loops react only to HTTP status codes, not to a connection that is accepted then never responds (black-holed TCP, hung TLS, stalled proxy) - so await fetch(...) never settles and the command hangs with no output and no exit. freehire's helper even documented a fast-degrade contract its try/catch didn't deliver on a mid-flight stall. Adds signal: AbortSignal.timeout(15000) to every fetch across all six CLIs, with network-free tests asserting the signal is present on each request wrapper.

By @thejesh23. Verified: 8 timeout tests pass locally with fetch stubbed (no network), and would fail on the pre-fix code.

Closes #196

2026-07-20 20:19:27 +02:00

..

cli-flag-validation.test.ts

Add freehire-search: country-agnostic freehire.dev aggregator skill (#85)

2026-07-09 06:04:35 +02:00

commands.test.ts

Add freehire-search: country-agnostic freehire.dev aggregator skill (#85)

2026-07-09 06:04:35 +02:00

helpers.ts

Add freehire-search: country-agnostic freehire.dev aggregator skill (#85)

2026-07-09 06:04:35 +02:00

parsing.test.ts

Add freehire-search: country-agnostic freehire.dev aggregator skill (#85)

2026-07-09 06:04:35 +02:00

request-timeout.test.ts

fix(portals): add a 15s request timeout to every board fetch (#197)

2026-07-20 20:19:27 +02:00