Skip unsearchable users during live refresh#25
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary\n- treat GitHub Search 422 responses for unsearchable/deleted/inaccessible users as per-user activity misses\n- log a warning and continue refreshing instead of failing the whole weekly run\n- keep other search/API errors fatal so real outages are still visible\n\n## Why\nThe weekly refresh can discover users through GraphQL user search that later fail REST search with:\n\n
\nThe listed users cannot be searched either because the users do not exist or you do not have permission to view the users.\n\n\nThat should not abort the full data collection.\n\n## Verification\n- pnpm run check\n- pnpm run test