Skip to content

User Dashboard: Repository overview not showing all repositories #12051

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

Closed
2 of 7 tasks
Wyall opened this issue Jun 25, 2020 · 6 comments
Closed
2 of 7 tasks

User Dashboard: Repository overview not showing all repositories #12051

Wyall opened this issue Jun 25, 2020 · 6 comments

Comments

@Wyall
Copy link
Contributor

Wyall commented Jun 25, 2020

  • Gitea version (or commit ref): 1.12.1 Docker
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant

Description

I have 3 Repos, all are not archived. It seems like the filter settings in the repository view on the top right are misbehaving. See the screenshots. I would expect that all 3 show up in the first picture, but only 2 do. But maybe I am missing something and this works as intended. All 3 show up with the settings in the third screenshot.

Screenshots

1
2
3

@jangxx
Copy link

jangxx commented Aug 15, 2020

I had the the same problem just now. Apparently, for some of my repos, the is_archived column in the database was set to NULL instead of 0. I fixed it by simply running

UPDATE gitea.repository SET is_archived=0 WHERE is_archived IS NULL

on the database and now the repo overview is working again.

@6543
Copy link
Member

6543 commented Aug 15, 2020

there is a migration task wo take care of when migrating to v1.13.0 and gitea doctor is also able to fix this :) right with gitea >= 1.12.0

#11859

@6543
Copy link
Member

6543 commented Aug 15, 2020

@Wyall is is hard to find reverences to the doctor comand?

@6543
Copy link
Member

6543 commented Aug 15, 2020

./gitea doctor --run check-db-consistency --fix would do it

@warnat
Copy link

warnat commented Sep 17, 2020

seems like it will be/was fixed with one of the next migrations here #11853
and here : b9e2812

So, if the problem itself is not acute right now, please close.

@Wyall
Copy link
Contributor Author

Wyall commented Sep 17, 2020

Then let's see

@Wyall Wyall closed this as completed Sep 17, 2020
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
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

4 participants