-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
User dashboard repositories filter incorrectly handles repos with NULL "is_archived" column #12037
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
Comments
I think migrating |
|
Hmm we did this: Looks like you have to manually run doctor command for 1.12 to fix this issue |
@oreineke are you sure you are on 1.12.1 ? |
Yes, I am sure, this is a copy and paste from the web page: "Powered by Gitea Version: 1.12.1" |
Maybe also relevant: I am running Gitea in Docker, so I pulled image gitea/gitea:1.12 (before, I was running gitea/gitea:1.11). |
On closer inspection I see in the "gitea doctor --all" output
The "OK" is kind of misleading. |
These are the Migrations I see in the log:
|
This is not a migration on Gitea 1.12 (see previously linked issue) thats why it was added to the doctor command. Looks like it worked based on the doctor output above? |
OK, I see! Running |
[x]
):Description
If you have repos that have a NULL "is_archived" value in the "repositories" table, they are not shown if you filter for not-archived repositories in the user's dashboard repositories widget.
This is because the related SQL queries filter for "is_archived=false", which does not match NULL.
Repos that have a NULL "is_archived" value are those created before the archive feature was introduced in Gitea I suspect.
A possible solution might be to automatically migrate "is_archived=NULL" to "is_archived=false" in the "repositories" table.
The text was updated successfully, but these errors were encountered: