Improvement: Distinguish Between "API Error" and "User Not Found"

[Yashaswini-K-P]

Description

Currently, analyze-inactivity.js treats all fetchData failures as "unreachable." This is problematic because it fails to distinguish between a temporary network/server issue (500 Error) and a permanent issue where the user account no longer exists (404 Error).

Proposed Solution

Modify fetchData to return the HTTP status code. The inactivity analysis should categorize these failures:

1. 500/503/429 (Temporary): Keep the user in the list to be checked again.
2. 404 (Permanent): Flag the user as "invalid" and add them to a separate report for cleanup or manual verification.

Implementation Details

• Update fetchData to return an object containing { data, status } rather than just null.
• Update the logic in the main loop to handle status === 404 separately.
• Create an invalid-users.json or update the final output object to include an invalidUsers array.

Benefits

• System Maintenance: Automatically identifies broken accounts that need to be removed or updated.
• Resource Efficiency: Avoids repeatedly polling for usernames that will never return a successful response.

[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.