[zjncs]

Problem

Experience.tsx:54 treats active === 0 as a fetch failure:

if (res.status === 200 && res?.data?.prediction?.active) {
  setPredict(toFixed(res.data.prediction.active * 100, 1));
} else {
  setErrorMsg(t('academe:failed_to_fetch_data'));
}

The live endpoint POST /api/beta/predict returns {"prediction":{"active":0.8265}} — a 0-1 probability. When the model returns exactly 0 (dead/archived repo), the truthy guard fails and a successful request renders the "failed to fetch data" error instead of a 0% progress bar.

Secondary falsy-zero: {predict && ...} hides the result section when predict is 0.

Fix

• typeof res?.data?.prediction?.active === 'number' (0 is a valid number result)
• {predict !== null && ...} (0 must display)

Verification

New Experience.test.tsx: mock getData resolving {status:200, data:{prediction:{active:0}}}, assert the error message does NOT appear. RED before (truthy guard fails on 0, error shows), GREEN after.

Risk

None — 0 is now correctly rendered as a 0% bar instead of an error message.

[vercel]

@zjncs is attempting to deploy a commit to the codersett's projects Team on Vercel.

A member of the Team first needs to authorize it.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.