fix: chunk support issue message stats query to avoid SQL parameter limit#3634
Open
fix: chunk support issue message stats query to avoid SQL parameter limit#3634
Conversation
davidleomay
reviewed
Apr 28, 2026
Member
davidleomay
left a comment
There was a problem hiding this comment.
Could we use Util.doInBatches?
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
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
GET /v1/support/issue/listfailed withThe incoming request has too many parameters. The server supports a maximum of 2100 parameterswhen more than ~2100 issues matched the filter.getMessageStatspassed all issue IDs into a singleIN (:...ids)clause; TypeORM emits one parameter per ID and SQL Server rejects the query above 2100.Test plan
npx prettier --checkon the changed filenpx eslinton the changed filenpm test(927 passed, 0 failed)/v1/support/issue/listsucceeds on a dataset with >2100 matching issues