Git with a cup of tea, painless self-hosted git service Mirror for internal git.with.parts use https://git.with.parts

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Nate Levesque f891172ef4 handle repository.size column being NULL in migration v263 (#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 #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.		12 months ago
..
main_test.go	…
v260.go	…
v261.go	…
v262.go	…
v263.go	handle repository.size column being NULL in migration v263 (#28336)	12 months ago
v264.go	…
v265.go	…
v266.go	Restore warning commit status (#27504)	1 year ago
v267.go	…
v268.go	…
v269.go	…
v270.go	…
v271.go	…
v272.go	…
v273.go	…
v274.go	…
v275.go	…
v276.go	…
v277.go	Add index to `issue_user.issue_id` (#27154)	1 year ago
v278.go	Add Index to `comment.dependent_issue_id` (#27325)	1 year ago
v279.go	Add Index to `action.user_id` (#27403)	1 year ago