-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Issue with recent Migration[156] #13255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with recent Migration[156] #13255
Comments
The problem is here: gitea/models/migrations/v156.go Line 91 in e964c6e
Your database contains orphaned releases. Unfortunately doctor check-db-consistency doesn't check for these. Therefore we need to do two things:
In order to get you going again you could either delete the releases relating to the missing repository with id 370 or create a fake repository with id 370 in the table. |
deleted orphaned objects from the db as discussed using sqlite> delete from release where repo_id=370; rebuilding Gitea, waiting for the result. edit: removing the orphaned objects as suggested by @zeripath helped the migration to run, Gitea restarted without further issues |
Signed-off-by: Andrew Thornton <[email protected]>
* Keep database transactions not too big * Fix #13255 Signed-off-by: Andrew Thornton <[email protected]> * Only cache the last repo Signed-off-by: Andrew Thornton <[email protected]> Co-authored-by: Andrew Thornton <[email protected]>
Gitea version 1.14.0+dev-49-g327f18c3b built with GNU Make 4.3, go1.15.3 : bindata, sqlite, sqlite_unlock_notify
git version 2.29.0.311.g38ddec7408
Description
I moved past the commit with the subject migration (which has been approved in #6025 ) from a pretty recent
commit
.Gitea failed to start properly as the migration failed with the above mentioned messages.
As the migration has not properly executed I could roll back.
The text was updated successfully, but these errors were encountered: