github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-11 17:46:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

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

New Issue
Closed
opened 2025-11-02 05:23:19 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 05:23:19 -06:00
Owner
Copy Link

Originally created by @ghost on GitHub (Aug 4, 2019).

  • Gitea version (or commit ref): 1.9.0 / 76408d50fb
  • 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.

cd238bc415/models/issue.go (L1357-L1366)

cd238bc415/models/issue.go (L1649-L1658)

cd238bc415/models/issue.go (L1708-L1710)

Originally created by @ghost on GitHub (Aug 4, 2019). - Gitea version (or commit ref): 1.9.0 / 76408d50fb - Git version: 2.20.1 - Operating system: macOS - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] 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. https://github.com/go-gitea/gitea/blob/cd238bc41598e69a78b4d17370c8929911c5f249/models/issue.go#L1357-L1366 https://github.com/go-gitea/gitea/blob/cd238bc41598e69a78b4d17370c8929911c5f249/models/issue.go#L1649-L1658 https://github.com/go-gitea/gitea/blob/cd238bc41598e69a78b4d17370c8929911c5f249/models/issue.go#L1708-L1710
GiteaMirror added the issue/confirmedtype/bug labels 2025-11-02 05:23:19 -06:00
GiteaMirror commented 2025-11-02 05:23:20 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Oct 4, 2019):

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.

@stale[bot] commented on GitHub (Oct 4, 2019): 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.
GiteaMirror commented 2025-11-02 05:23:21 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Oct 5, 2019):

This should be closed by #8347

@lunny commented on GitHub (Oct 5, 2019): This should be closed by #8347
GiteaMirror commented 2025-11-02 05:23:21 -06:00
Author
Owner
Copy Link

@guillep2k commented on GitHub (Oct 8, 2019):

This should be reopened as per #8427

@guillep2k commented on GitHub (Oct 8, 2019): This should be reopened as per #8427
GiteaMirror commented 2025-11-02 05:23:21 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Dec 31, 2019):

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.

@stale[bot] commented on GitHub (Dec 31, 2019): 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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
Mirrored from GitHub 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
No Label issue/confirmed type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3729
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?