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

ArchLinux upgrade to 1.15.4 #17336

Closed
smallint opened this issue Oct 17, 2021 · 2 comments
Closed

ArchLinux upgrade to 1.15.4 #17336

smallint opened this issue Oct 17, 2021 · 2 comments

Comments

@smallint
Copy link

Gitea Version

1.15.4

Git Version

2.33.1

Operating System

ArchLinux

How are you running Gitea?

Installed via pacman

Database

PostgreSQL

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Description

After upgrading to 1.15.4 I can't navigate to any repository anymore. The frontend shows error 500 and the backend logs:

2021/10/17 10:56:39 ...ules/context/repo.go:343:repoAssignment() [E] GetUserRepoPermission: skipObjectDecoder: expect object or null, error found in #0 byte of ...|&\003d{\003d}\003d|..., bigger context ...|&\003d{\003d}\003d|...

Screenshots

No response

@smallint
Copy link
Author

OK, I found the issue with table repo_unit and the backup. This I have fixed it by inserting the rows from an older backup.

@zeripath
Copy link
Contributor

In future read the blog entry for the version: https://blog.gitea.io/2021/10/gitea-1.15.4-is-released/

❗ We remind users that a bug was discovered with gitea dump in 1.14.3–1.14.6 and 1.15.0. Database dumps from these versions cause broken fields in the repo_unit and login_source tables causing the issue identified in #16961. Users on 1.14.x must upgrade to 1.14.7 before running gitea dump. If this is not possible and you are affected #17137 provides a new gitea doctor command to fix the repo_unit issue:

gitea doctor --fix --run fix-broken-repo-units

@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants