Skip to content
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

fix db transaction #3

Conversation

wxiaoguang
Copy link

No description provided.

Prevent multiple upload version creation.
@wxiaoguang wxiaoguang force-pushed the workaround-blob-upload branch from 75f1f97 to e673b96 Compare November 18, 2022 17:34
@KN4CK3R KN4CK3R force-pushed the workaround-blob-upload branch from a76aa77 to 815bad2 Compare November 18, 2022 20:27
@KN4CK3R KN4CK3R deleted the branch KN4CK3R:workaround-blob-upload December 15, 2022 11:48
@KN4CK3R KN4CK3R closed this Dec 15, 2022
@wxiaoguang wxiaoguang deleted the workaround-blob-upload branch February 9, 2023 16:47
KN4CK3R pushed a commit that referenced this pull request Dec 11, 2023
…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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants