fix: max_node_limit_exceeded error when fetching associatedPRs
#912
Conversation
This file contains 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
travi
approved these changes
Sep 3, 2024
|
🎉 This issue has been resolved in version 10.3.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The PR addressed the issue where we our graphql query that fetches associatedPRs hits a case where it requests for 1million plus nodes exceeding the GitHub Node Limits size. It does this by simply reducing the number of
labelsrequested per associatedPRs reducing the maximum possible requests to410,000just right below500,000which is GitHub's maximum Node Limit size.Changes Made:
firstvalue in thebaseFieldconstant from100to40for all graphql request that consumes it 😁Related Issues
Fixes #911