Call to /api/v1/repos/{:user}/{:repo}/branches/{:branch} fails unexpectedly #5118

New Issue

GiteaMirror · 2025-11-02T06:14:58-06:00

GiteaMirror commented

2025-11-02 06:14:58 -06:00

Originally created by @CirnoT on GitHub (Mar 25, 2020).

Gitea version (or commit ref): 1.12.0+dev-33-gc61b90253 running from Docker
Operating system: Linux gitea 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64 GNU/Linux
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:

2020/03/25 05:01:05 ...ules/context/repo.go:789:func1() [E] GetCommitsCount: Unsupported cached value type: <nil>

Description

The call to /api/v1/repos/{:user}/{:repo}/branches/{:branch} seems to fail unexpectedly and seemingly randomly, possibly due to high I/O load on machine.

It breaks havoc with Renovate Bot making it mark PRs for which request failed as edited.

Originally created by @CirnoT on GitHub (Mar 25, 2020).   - Gitea version (or commit ref): 1.12.0+dev-33-gc61b90253 running from Docker - Operating system: `Linux gitea 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64 GNU/Linux` - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ``` 2020/03/25 05:01:05 ...ules/context/repo.go:789:func1() [E] GetCommitsCount: Unsupported cached value type: <nil> ``` ## Description The call to `/api/v1/repos/{:user}/{:repo}/branches/{:branch}` seems to fail unexpectedly and seemingly randomly, possibly due to high I/O load on machine. It breaks havoc with [Renovate Bot](https://github.com/renovatebot/renovate) making it mark PRs for which request failed as edited.

GiteaMirror added the type/bug label 2025-11-02 06:14:58 -06:00

GiteaMirror closed this issue

2025-11-02 06:14:58 -06:00

GiteaMirror commented

2025-11-02 06:14:59 -06:00

@stale[bot] commented on GitHub (May 25, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (May 25, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:14:59 -06:00

@6543 commented on GitHub (May 28, 2020):

do this still happen @CirnoT ?

@6543 commented on GitHub (May 28, 2020): do this still happen @CirnoT ?

GiteaMirror commented

2025-11-02 06:14:59 -06:00

@CirnoT commented on GitHub (May 28, 2020):

I was unable to reproduce it ever since I've switched to memcached as cache storage and configured higher cache timeouts.

I'll close it for now, will open with more details and debug logging if it ever happens again.

@CirnoT commented on GitHub (May 28, 2020): I was unable to reproduce it ever since I've switched to memcached as cache storage and configured higher cache timeouts. I'll close it for now, will open with more details and debug logging if it ever happens again.

GiteaMirror referenced this issue

2025-11-02 14:44:44 -06:00

[PR #5118] [MERGED] Fix deadlock when sqlite #17650

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#5118