fix: ingest hang diagnostics — timeout detection + actionable error output

[cosmicallycooked]

Bug

sonar ingest tweets and sonar ingest bookmarks spin the loading indicator indefinitely when the Sonar server accepts the TCP connection but stalls before completing the response (e.g. under high load, misrouted traffic, or a cold-start delay). The only recovery is Ctrl+C. There is no feedback about what went wrong or what to try next.

The same silent-hang issue affects sonar ingest monitor --watch, where a single stalled poll freezes the entire watch loop.

Root cause

gql() in src/lib/client.ts passes no signal to fetch(), so requests have no timeout. Node's default TCP timeout is effectively infinite for established connections.

Fix

src/lib/client.ts

• Every request is now wrapped in an AbortController with a configurable timeoutMs (default 20 s).
• AbortError is caught and rethrown as a structured message that names the elapsed timeout, attributes the likely cause, and directs the operator to check SONAR_API_URL and retry.

src/commands/ingest/tweets.tsx + bookmarks.tsx

• A component-level 15 s wall-clock deadline (via useRef / setTimeout) fires independently of the HTTP-layer timeout. This closes the gap where the gql() call times out but React hasn't surfaced the error yet.
• Timeout state is tracked separately so the UI renders a yellow warning (not a red error) with a specific note: run sonar ingest monitor — the server may have queued the job even if the response was lost.
• When the mutation returns false (job explicitly not queued), a follow-up hint directs the operator to sonar account.

src/commands/monitor.tsx

• The raw fetch() call for /indexing/status now carries its own AbortController (10 s). In --watch mode a single stalled poll no longer freezes subsequent polls.

Verification

Reproduce the hang by pointing SONAR_API_URL at a server that accepts the connection but never responds (e.g. nc -l 9999):

SONAR_API_URL=http://localhost:9999/graphql sonar ingest tweets
# Before: spins forever
# After:  yellow warning after 15 s with actionable next steps

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}