Error 500 when visit /issues and /pulls (too many SQL variables)

• Gitea version (or commit ref): 1.9.0 / 76408d5
• Git version: 2.20.1
• Operating system: macOS
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant
• Log gist:

routers/user/home.go:269:Issues() [E] CountIssuesByRepo: too many SQL variables

Description

The above error should be able to explain this issue.

gitea/models/issue.go

Lines 1357 to 1366 in cd238bc

	if len(opts.IssueIDs) > 0 {
	sess.In("issue.id", opts.IssueIDs)
	}
	if len(opts.RepoIDs) > 0 {
	// In case repository IDs are provided but actually no repository has issue.
	sess.In("issue.repo_id", opts.RepoIDs)
	}

gitea/models/issue.go

Lines 1649 to 1658 in cd238bc

	case FilterModeAll:
	stats.OpenCount, err = x.Where(cond).And("is_closed = ?", false).
	And(builder.In("issue.repo_id", opts.UserRepoIDs)).
	Count(new(Issue))
	if err != nil {
	return nil, err
	}
	stats.ClosedCount, err = x.Where(cond).And("is_closed = ?", true).
	And(builder.In("issue.repo_id", opts.UserRepoIDs)).
	Count(new(Issue))

gitea/models/issue.go

Lines 1708 to 1710 in cd238bc

	stats.YourRepositoriesCount, err = x.Where(cond).
	And(builder.In("issue.repo_id", opts.UserRepoIDs)).
	Count(new(Issue))

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

[lunny]

This should be closed by #8347

[guillep2k]

This should be reopened as per #8427