Troubles with SQLiteDB #11002

New Issue

GiteaMirror · 2025-11-02T09:24:34-06:00

GiteaMirror commented

2025-11-02 09:24:34 -06:00

Originally created by @xavetar on GitHub (Jun 9, 2023).

.

Originally created by @xavetar on GitHub (Jun 9, 2023). .

GiteaMirror added the type/bug label 2025-11-02 09:24:34 -06:00

GiteaMirror closed this issue

2025-11-02 09:24:34 -06:00

GiteaMirror commented

2025-11-02 09:24:35 -06:00

@xavetar commented on GitHub (Jun 10, 2023):

.

@xavetar commented on GitHub (Jun 10, 2023): .

GiteaMirror commented

2025-11-02 09:24:35 -06:00

@lunny commented on GitHub (Jun 21, 2023):

I cannot understand well about the bug. Could you reproduce it on https://try.gitea.io which is running based on sqlite?

@lunny commented on GitHub (Jun 21, 2023): I cannot understand well about the bug. Could you reproduce it on https://try.gitea.io which is running based on sqlite?

GiteaMirror commented

2025-11-02 09:24:36 -06:00

@xavetar commented on GitHub (Jun 21, 2023):

.

@xavetar commented on GitHub (Jun 21, 2023): .

GiteaMirror commented

2025-11-02 09:24:36 -06:00

@lunny commented on GitHub (Jun 22, 2023):

I cannot understand well about the bug. Could you reproduce it on https://try.gitea.io which is running based on sqlite?

Without direct access to the file system, no.

Steps to repeat:
1. Project size >10GB

2. Don't finish uploading the project via: "git push" (it will eat up disk space even if it's not completely pushed - I think this is also a bug)

3. Go to directory: "ata/git/repositories/$REPO.git/"

4. Run command: "git prune"

5. Delete project via gitea interface (may have problems with infinite waiting)

6. Reload the container.

7. The project will disappear, but this junk data will remain in the SQLite database.
Trying to create a project with the same name will fail. Trying to manually delete through other tools for working with databases will not work (there will be no records in the database). I managed to detect this garbage only through a HEX editor.

I don't think it's a normal behaviour to manually operate gitea's repositories directly

@lunny commented on GitHub (Jun 22, 2023): > > I cannot understand well about the bug. Could you reproduce it on https://try.gitea.io which is running based on sqlite? > > Without direct access to the file system, no. > > Steps to repeat: > > 1. Project size >10GB > > 2. Don't finish uploading the project via: "git push" (it will eat up disk space even if it's not completely pushed - I think this is also a bug) > > 3. Go to directory: "ata/git/repositories/$REPO.git/" > > 4. Run command: "git prune" > > 5. Delete project via gitea interface (may have problems with infinite waiting) > > 6. Reload the container. > > 7. The project will disappear, but this junk data will remain in the SQLite database. > > > Trying to create a project with the same name will fail. Trying to manually delete through other tools for working with databases will not work (there will be no records in the database). I managed to detect this garbage only through a HEX editor. I don't think it's a normal behaviour to manually operate gitea's repositories directly

GiteaMirror commented

2025-11-02 09:24:36 -06:00

@xavetar commented on GitHub (Jun 22, 2023):

.

@xavetar commented on GitHub (Jun 22, 2023): .

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#11002