-
Notifications
You must be signed in to change notification settings - Fork 117
Fix misleading private repository message during partial fetch #301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
jagriti-aswal
wants to merge
2
commits into
GitMetricsLab:main
from
jagriti-aswal:fix-misleading-private-repo-error
+24
−9
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Inspect rejection reasons to preserve specific error handling and fix rate limiting detection.
The switch to
Promise.allSettledprevents specific error details from reaching the catch block. Critical issues:Rate limiting detection is broken: Line 61 always sets
rateLimited(false), but the catch block's 403 handling (lines 64-66) is now unreachable sincePromise.allSettlednever throws. Users hitting rate limits won't be prompted to add a PAT.Misleading error when both requests fail: When both
issueResandprResare rejected, "Some GitHub data could not be fetched completely" incorrectly implies partial success. It should indicate complete failure.Loss of specific error context: Rejected promises contain error details in their
reasonproperty (403 rate limit, 401 permission, 404 not found, validation errors), but these aren't inspected.🔧 Proposed fix to inspect rejection reasons
📝 Committable suggestion
🤖 Prompt for AI Agents