Commits on Dec 5, 2023

1. handle repository.size column being NULL in migration v263 (go-gitea#… …

   …28336)
   
   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 go-gitea#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.

   

   thenaterhood authored and GiteaBot committed Dec 5, 2023
   Configuration menu

   • View commit details
   • Copy full SHA for aa491b0
   • Browse repository at this point

   Copy the full SHA

   aa491b0 View commit details

   Browse the repository at this point in the history