feat: liveness signal for wedged provider streams (5min chunk timeout hides stalls)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- observability-sre
Research direction
Start in provider.ts at wrapSSE and inspect how DEFAULT_CHUNK_TIMEOUT currently detects missing chunks. Compare the separate no-first-byte/liveness signal and the still-waiting indicator proposed in the issue, then identify which behavior should be specified before implementation. Done means a wedged stream becomes visible sooner without regressing intentionally slow provider streams.
Written by the indexing model from the issue text.
Description
Found during the v0.8.8 release review (Chaos Gremlin / on-call SRE, P2 deferred).
#844 raised DEFAULT_CHUNK_TIMEOUT from 2min to 5min. The watchdog (wrapSSE in provider.ts) only fires when a chunk fails to arrive within the window, so a genuinely wedged provider stream (connection alive, no data) now hangs a user for ~5 minutes before the timeout aborts — up from ~2. Errors are surfaced, not silent, but the user-visible stall doubled.
This was an intentional tradeoff (slow warehouse/LLM streams were tripping the 2min watchdog), so it is deferred. Possible follow-up: a separate, shorter "no first byte" / liveness signal distinct from the steady-state chunk timeout, or surfacing a "still waiting…" indicator past N seconds so a wedged stream is visible before the hard timeout.
- Dominant language
- TypeScript
- Stars
- 813
- Forks
- 134
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 65
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AltimateAI/altimate-code
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
AltimateAI/altimate-code#1359 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
AltimateAI/altimate-code#1323 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
AltimateAI/altimate-code#1288 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
AltimateAI/altimate-code#1285 ·
-
privacy: Altimate Base consent dialog no longer discloses persistent per-installation identifier Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
AltimateAI/altimate-code#1284 ·
All issues in AltimateAI/altimate-code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
bcgov/bc-wallet-mobile#4761 · 1 comment ·
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
refactor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100