github-forks
/
gitea
mirror of https://github.com/go-gitea/gitea.git
1
0
Fork 0
Code Projects Releases Activity
gitea/models/migrations/v1_21
History
Nate Levesque f891172ef4
handle repository.size column being NULL in migration v263 () 
This resolves a problem I encountered while updating gitea from 1.20.4
to 1.21. For some reason (correct or otherwise) there are some values in
`repository.size` that are NULL in my gitea database which cause this
migration to fail due to the NOT NULL constraints.

Log snippet (excuse the escape characters)
```
ESC[36mgitea                |ESC[0m 2023-12-04T03:52:28.573122395Z 2023/12/04 03:52:28 ...ations/migrations.go:641:Migrate() [I] Migration[263]: Add git_size and lfs_size columns to repository table
ESC[36mgitea                |ESC[0m 2023-12-04T03:52:28.608705544Z 2023/12/04 03:52:28 routers/common/db.go:36:InitDBEngine() [E] ORM engine initialization attempt #3/10 failed. Error: migrate: migration[263]: Add git_size and lfs_size columns to repository table failed: NOT NULL constraint failed: repository.git_size
```

I assume this should be reasonably safe since `repository.git_size` has
a default value of 0 but I don't know if that value being 0 in the odd
situation where `repository.size == NULL` has any problematic
consequences.
..
main_test.go
…
v260.go
…
v261.go
…
v262.go Support `pull_request_target` event ()
v263.go handle repository.size column being NULL in migration v263 ()
v264.go Drop the correct deleted branch table ()
v265.go Actions Artifacts support uploading multiple files and directories ()
v266.go Restore warning commit status ()
v267.go Reduce unnecessary DB queries for Actions tasks ()
v268.go Implement auto-cancellation of concurrent jobs if the event is push ()
v269.go Drop the correct deleted branch table ()
v270.go Fix typo in metadata ()
v271.go Allow to archive labels ()
v272.go Add optimistic lock to ActionRun table ()
v273.go chore(actions): support cron schedule task ()
v274.go Artifacts retention and auto clean up ()
v275.go Add a new column schedule_id for action_run to track ()
v276.go Fix wrong xorm get usage on migration ()
v277.go Add index to `issue_user.issue_id` ()
v278.go Add Index to `comment.dependent_issue_id` ()
v279.go Add Index to `action.user_id` ()