mirror of
https://github.com/go-gitea/gitea.git
synced 2026-05-22 13:55:07 -05:00
The incoming request has too many parameters. This server supports a maximum of 2100 parameters. #11414
Closed
opened 2025-11-02 09:36:56 -06:00 by GiteaMirror
·
15 comments
No Branch/Tag Specified
main
release/v1.25
release/v1.24
release/v1.23
release/v1.22
release/v1.21
release/v1.20
release/v1.19
release/v1.18
release/v1.17
release/v1.16
release/v1.15
release/v1.14
release/v1.13
release/v1.12
release/v1.11
release/v1.10
release/v1.9
release/v1.8
v1.25.3
v1.25.2
v1.25.1
v1.25.0
v1.24.7
v1.25.0-rc0
v1.26.0-dev
v1.24.6
v1.24.5
v1.24.4
v1.24.3
v1.24.2
v1.24.1
v1.24.0
v1.23.8
v1.24.0-rc0
v1.25.0-dev
v1.23.7
v1.23.6
v1.23.5
v1.23.4
v1.23.3
v1.23.2
v1.23.1
v1.23.0
v1.23.0-rc0
v1.24.0-dev
v1.22.6
v1.22.5
v1.22.4
v1.22.3
v1.22.2
v1.22.1
v1.22.0
v1.23.0-dev
v1.22.0-rc1
v1.21.11
v1.22.0-rc0
v1.21.10
v1.21.9
v1.21.8
v1.21.7
v1.21.6
v1.21.5
v1.21.4
v1.21.3
v1.21.2
v1.20.6
v1.21.1
v1.21.0
v1.21.0-rc2
v1.21.0-rc1
v1.20.5
v1.22.0-dev
v1.21.0-rc0
v1.20.4
v1.20.3
v1.20.2
v1.20.1
v1.20.0
v1.19.4
v1.21.0-dev
v1.20.0-rc2
v1.20.0-rc1
v1.20.0-rc0
v1.19.3
v1.19.2
v1.19.1
v1.19.0
v1.19.0-rc1
v1.20.0-dev
v1.19.0-rc0
v1.18.5
v1.18.4
v1.18.3
v1.18.2
v1.18.1
v1.18.0
v1.17.4
v1.18.0-rc1
v1.19.0-dev
v1.18.0-rc0
v1.17.3
v1.17.2
v1.17.1
v1.17.0
v1.17.0-rc2
v1.16.9
v1.17.0-rc1
v1.18.0-dev
v1.16.8
v1.16.7
v1.16.6
v1.16.5
v1.16.4
v1.16.3
v1.16.2
v1.16.1
v1.16.0
v1.15.11
v1.17.0-dev
v1.16.0-rc1
v1.15.10
v1.15.9
v1.15.8
v1.15.7
v1.15.6
v1.15.5
v1.15.4
v1.15.3
v1.15.2
v1.15.1
v1.14.7
v1.15.0
v1.15.0-rc3
v1.14.6
v1.15.0-rc2
v1.14.5
v1.16.0-dev
v1.15.0-rc1
v1.14.4
v1.14.3
v1.14.2
v1.14.1
v1.14.0
v1.13.7
v1.14.0-rc2
v1.13.6
v1.13.5
v1.14.0-rc1
v1.15.0-dev
v1.13.4
v1.13.3
v1.13.2
v1.13.1
v1.13.0
v1.12.6
v1.13.0-rc2
v1.14.0-dev
v1.13.0-rc1
v1.12.5
v1.12.4
v1.12.3
v1.12.2
v1.12.1
v1.11.8
v1.12.0
v1.11.7
v1.12.0-rc2
v1.11.6
v1.12.0-rc1
v1.13.0-dev
v1.11.5
v1.11.4
v1.11.3
v1.10.6
v1.12.0-dev
v1.11.2
v1.10.5
v1.11.1
v1.10.4
v1.11.0
v1.11.0-rc2
v1.10.3
v1.11.0-rc1
v1.10.2
v1.10.1
v1.10.0
v1.9.6
v1.9.5
v1.10.0-rc2
v1.11.0-dev
v1.10.0-rc1
v1.9.4
v1.9.3
v1.9.2
v1.9.1
v1.9.0
v1.9.0-rc2
v1.10.0-dev
v1.9.0-rc1
v1.8.3
v1.8.2
v1.8.1
v1.8.0
v1.8.0-rc3
v1.7.6
v1.8.0-rc2
v1.7.5
v1.8.0-rc1
v1.9.0-dev
v1.7.4
v1.7.3
v1.7.2
v1.7.1
v1.7.0
v1.7.0-rc3
v1.6.4
v1.7.0-rc2
v1.6.3
v1.7.0-rc1
v1.7.0-dev
v1.6.2
v1.6.1
v1.6.0
v1.6.0-rc2
v1.5.3
v1.6.0-rc1
v1.6.0-dev
v1.5.2
v1.5.1
v1.5.0
v1.5.0-rc2
v1.5.0-rc1
v1.5.0-dev
v1.4.3
v1.4.2
v1.4.1
v1.4.0
v1.4.0-rc3
v1.4.0-rc2
v1.3.3
v1.4.0-rc1
v1.3.2
v1.3.1
v1.3.0
v1.3.0-rc2
v1.3.0-rc1
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.2.0-rc3
v1.2.0-rc2
v1.1.4
v1.2.0-rc1
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.2
v1.0.1
v1.0.0
v0.9.99
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
Mirrored from GitHub Pull Request
No Label
type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/gitea#11414
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @zjjhot on GitHub (Aug 7, 2023).
Originally assigned to: @wolfogre on GitHub.
Description
visit http://giteaurl/issues
then click "Closed" tab on right side
there is an error page displayed 500 internal error,and in log file:The incoming request has too many parameters. This server supports a maximum of 2100 parameters. Please reduce the number of parameters and resend the request.
This is due to the default selection behavior of the issues page, as there are too many repos passed in later on &repos=...
There are differences in the concepts of between "select all repos " and "select every repo"
If 'select all' is understood as' select everything ', then&repos=.... Later, if there are 1000+ repos, then 1000+ parameters need to be passed in ...
Gitea Version
1.21.0+dev-892-g8e8f55839
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
1.21.0+dev-892-g8e8f55839
Operating System
windows
How are you running Gitea?
windows exe
Database
None
@techknowlogick commented on GitHub (Aug 7, 2023):
Which database are you using?
@KN4CK3R commented on GitHub (Aug 7, 2023):
I'm sure it's one of the
GetIssuesByIDsmethods which do a.In("id", lots of ids). We may workaround the limitation by building a raw where conditionid IN (1,2,3,4,5,6, ...)without the use of parameters. Or we need something completly different.@zjjhot commented on GitHub (Aug 7, 2023):
ms sqlserver , thank you.
@zjjhot commented on GitHub (Aug 7, 2023):
I think ,when select all repos, the .in sql string shoud be " not in (null)" rather then " in (id1,id2,id3.....ids)".
@CaiCandong commented on GitHub (Aug 7, 2023):
I think it's pointless to discuss this, in some cases I only want to view the two I care about inside the 10,000 repos, but in other cases I only want to view the other repos inside the 10,000 repos other than those two. It's hard to tell which is more important,
inornot in.@zjjhot commented on GitHub (Aug 8, 2023):
" not in (null)" means select all, or default show all
" in (id1,id2,id3.....ids)" means select every thing.
if you need reach "view something or view other", it is best to add checkbox before repo list.
For SQL statements, concatenating too many parameters after IN is not a good way.
@CaiCandong commented on GitHub (Aug 8, 2023):
If you have a good solution to fix this, you can initiate a PR @zjjhot
@zjjhot commented on GitHub (Aug 8, 2023):
I'm not good at golang ⊙﹏⊙。Very thanks for every contributor.
@zjjhot commented on GitHub (Aug 10, 2023):
visit this url : http://your-gitea-url/issues?state=closed&q=
then logged this : 500 Internal Server Error , .../web/user/home.go:510 buidIssueOverview() [E] CountIssuesByRepo : unable to CountIssuesByRepo: mssql : The incoming request has too many parameters. This server supports a maximum of 2100 parameters.
I EVEN NOT input repos id param in the url string..., that just only 1 param is : state=closed.
so , what happend .... ⊙﹏⊙
@cassiozareck commented on GitHub (Aug 13, 2023):
The issue is with the DB parameters rather than Web.
I was exploring some actions we can take to solve this problem. RAW sql IN statements seems feasible but it would have some limit for different DBMS and as of my search for large lists it can have some performance impact (not so sure about it I need to study more this).
What if we try to create a temporary table to store those issues IDS coming from
issueIDsFromSearch. Then we can do a join instead of.In(ids...)insideapplyConditions?Also Im with trouble to reproduce this bug. In my local gitea instance Im not even close to 2100 issues. Is there a way to reproduce this bug locally?
@yp05327 commented on GitHub (Aug 15, 2023):
Migrating Gitea to local with issues. Then you will get 2k+ opening issues and 9k+ closed issues.
But this will take a long time. 😕
Maybe you can find a repo in GitHub with 2k open issue and 2k closed issue.
@zjjhot commented on GitHub (Aug 22, 2023):
Any one can help to fix this 😕
@zjjhot commented on GitHub (Aug 22, 2023):
@lunny commented on GitHub (Aug 22, 2023):
regression from #26012 @wolfogre
@KN4CK3R commented on GitHub (Aug 22, 2023):
I don't think it's a regression. The query was not changed.