MAX_NODE_LIMIT_EXCEEDED #911
Comments
|
We are already paginating and in fact we split requests into chunks, the issue here is that we've got a query that possibly break the GitHub GraphQL API Node Limit... this one's my bad 🫣 But, Examine our Query and Calculatequery getAssociatedPRs {
repository([name], [owner]) {
commit1: object(oid: [sha]) {
...Fields
}
// ....other commits minimized
commit100: object(oid: [sha]) {
...Fields
}
}
}
fragment Fields on Commit {
oid
associatedPullRequests(first: 100) {
pageInfo {
endCursor
hasNextPage
}
nodes {
//...otherBaseFields minimized
labels(first: 100) {
nodes {
id
url
name
color
}
}
mergeable
canBeRebased
changedFiles
mergedAt
isDraft
mergedBy {
login
avatarUrl
url
}
commits {
totalCount
}
}
}
}100 = 100 Commits Nodes = 1,010,000 Total Possible Nodes Explainer
Proposed FixWe currently split the In order to accommodate the 😉 |
|
🎉 This issue has been resolved in version 10.3.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
i just hit this error when releasing a package that hasnt had activity in quite some time other than renovate dependency update PRs. the last release of this package was in 2021, so i imagine there are lots of dependency update commits and associated PRs since then. i imagine this is another scenario where pagination could be necessary.
error output:
The text was updated successfully, but these errors were encountered: