Missing AbortController / timeout on all server-side fetch() calls

[rishab11250]

Description

Multiple server-side fetch() calls lack timeout handling via AbortController. If the LeetCode API wrapper or GitHub API hangs, the request stalls indefinitely with no timeout, no fallback, no recovery path.

Affected Locations

File	Line	Request	Risk
scripts/fetch-user-info.js	25	fetch(rawUrl) — GitHub raw data	Hangs entire user profile request
scripts/fetch-user-info.js	53	fetch(liveApiUrl) — LeetCode API wrapper	Hangs entire user profile request
server.js	204	fetchUserInfo(username) — no timeout passed down	Cascading timeout failure

Steps to Reproduce

1. Start the server.
2. Trigger /api/user/:username for any user.
3. If the LeetCode wrapper API becomes unresponsive, livePromise (line 53) never resolves/rejects.
4. The entire request hangs forever. No timeout mechanism exists.
5. Subsequent requests accumulate, consuming server connections.

Expected Behavior

Every outbound fetch() should have an AbortController with a 15-second timeout that cleanly aborts and triggers the existing error/fallback paths.

Actual Behavior

Zero timeout configuration. If a remote API hangs, the server hangs with it.

Suggested Fix

Create a reusable helper in fetch-user-info.js:

async function fetchWithTimeout(url, timeoutMs = 15000) {
  const controller = new AbortController();
  const timeoutId = setTimeout(() => controller.abort(), timeoutMs);
  try {
    const res = await fetch(url, { signal: controller.signal });
    return res;
  } finally {
    clearTimeout(timeoutId);
  }
}

Replace both fetch(rawUrl) and fetch(liveApiUrl) calls with fetchWithTimeout(...).

Affected Files

• scripts/fetch-user-info.js (lines 25, 53)
• server.js (line 204 — ensure timeout is respected)

[github-actions]

Thank you for opening an issue.

Please review our CONTRIBUTING.md guidelines before getting started.

A maintainer will review this issue shortly. If you would like to work on the issue yourself, please leave a comment requesting assignment.

Issue Assignment Policy

• The issue creator is given the first priority to work on their issue.
• If the creator declines or does not request assignment, the issue will be assigned to others in the order of requests received.
• Please do not submit PRs or begin work until you are officially assigned.

Note: This project is currently maintained by a solo maintainer, so reviews, assignments, and responses may sometimes take a little time. Thanks for your patience.

[rishab11250]

I want to work on this