mirror of
https://github.com/go-gitea/gitea.git
synced 2026-03-14 11:56:41 -05:00
Cannot see Repositories on Gitea Dashboard after Gitea update (1.4.1 -> 1.6.4 -> 1.12.5) #6211
Closed
opened 2025-11-02 06:48:31 -06:00 by GiteaMirror
·
14 comments
No Branch/Tag Specified
main
release/v1.25
release/v1.24
release/v1.23
release/v1.22
release/v1.21
release/v1.20
release/v1.19
release/v1.18
release/v1.17
release/v1.16
release/v1.15
release/v1.14
release/v1.13
release/v1.12
release/v1.11
release/v1.10
release/v1.9
release/v1.8
v1.25.3
v1.25.2
v1.25.1
v1.25.0
v1.24.7
v1.25.0-rc0
v1.26.0-dev
v1.24.6
v1.24.5
v1.24.4
v1.24.3
v1.24.2
v1.24.1
v1.24.0
v1.23.8
v1.24.0-rc0
v1.25.0-dev
v1.23.7
v1.23.6
v1.23.5
v1.23.4
v1.23.3
v1.23.2
v1.23.1
v1.23.0
v1.23.0-rc0
v1.24.0-dev
v1.22.6
v1.22.5
v1.22.4
v1.22.3
v1.22.2
v1.22.1
v1.22.0
v1.23.0-dev
v1.22.0-rc1
v1.21.11
v1.22.0-rc0
v1.21.10
v1.21.9
v1.21.8
v1.21.7
v1.21.6
v1.21.5
v1.21.4
v1.21.3
v1.21.2
v1.20.6
v1.21.1
v1.21.0
v1.21.0-rc2
v1.21.0-rc1
v1.20.5
v1.22.0-dev
v1.21.0-rc0
v1.20.4
v1.20.3
v1.20.2
v1.20.1
v1.20.0
v1.19.4
v1.21.0-dev
v1.20.0-rc2
v1.20.0-rc1
v1.20.0-rc0
v1.19.3
v1.19.2
v1.19.1
v1.19.0
v1.19.0-rc1
v1.20.0-dev
v1.19.0-rc0
v1.18.5
v1.18.4
v1.18.3
v1.18.2
v1.18.1
v1.18.0
v1.17.4
v1.18.0-rc1
v1.19.0-dev
v1.18.0-rc0
v1.17.3
v1.17.2
v1.17.1
v1.17.0
v1.17.0-rc2
v1.16.9
v1.17.0-rc1
v1.18.0-dev
v1.16.8
v1.16.7
v1.16.6
v1.16.5
v1.16.4
v1.16.3
v1.16.2
v1.16.1
v1.16.0
v1.15.11
v1.17.0-dev
v1.16.0-rc1
v1.15.10
v1.15.9
v1.15.8
v1.15.7
v1.15.6
v1.15.5
v1.15.4
v1.15.3
v1.15.2
v1.15.1
v1.14.7
v1.15.0
v1.15.0-rc3
v1.14.6
v1.15.0-rc2
v1.14.5
v1.16.0-dev
v1.15.0-rc1
v1.14.4
v1.14.3
v1.14.2
v1.14.1
v1.14.0
v1.13.7
v1.14.0-rc2
v1.13.6
v1.13.5
v1.14.0-rc1
v1.15.0-dev
v1.13.4
v1.13.3
v1.13.2
v1.13.1
v1.13.0
v1.12.6
v1.13.0-rc2
v1.14.0-dev
v1.13.0-rc1
v1.12.5
v1.12.4
v1.12.3
v1.12.2
v1.12.1
v1.11.8
v1.12.0
v1.11.7
v1.12.0-rc2
v1.11.6
v1.12.0-rc1
v1.13.0-dev
v1.11.5
v1.11.4
v1.11.3
v1.10.6
v1.12.0-dev
v1.11.2
v1.10.5
v1.11.1
v1.10.4
v1.11.0
v1.11.0-rc2
v1.10.3
v1.11.0-rc1
v1.10.2
v1.10.1
v1.10.0
v1.9.6
v1.9.5
v1.10.0-rc2
v1.11.0-dev
v1.10.0-rc1
v1.9.4
v1.9.3
v1.9.2
v1.9.1
v1.9.0
v1.9.0-rc2
v1.10.0-dev
v1.9.0-rc1
v1.8.3
v1.8.2
v1.8.1
v1.8.0
v1.8.0-rc3
v1.7.6
v1.8.0-rc2
v1.7.5
v1.8.0-rc1
v1.9.0-dev
v1.7.4
v1.7.3
v1.7.2
v1.7.1
v1.7.0
v1.7.0-rc3
v1.6.4
v1.7.0-rc2
v1.6.3
v1.7.0-rc1
v1.7.0-dev
v1.6.2
v1.6.1
v1.6.0
v1.6.0-rc2
v1.5.3
v1.6.0-rc1
v1.6.0-dev
v1.5.2
v1.5.1
v1.5.0
v1.5.0-rc2
v1.5.0-rc1
v1.5.0-dev
v1.4.3
v1.4.2
v1.4.1
v1.4.0
v1.4.0-rc3
v1.4.0-rc2
v1.3.3
v1.4.0-rc1
v1.3.2
v1.3.1
v1.3.0
v1.3.0-rc2
v1.3.0-rc1
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.2.0-rc3
v1.2.0-rc2
v1.1.4
v1.2.0-rc1
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.2
v1.0.1
v1.0.0
v0.9.99
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
Mirrored from GitHub Pull Request
No Label
issue/duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/gitea#6211
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @TitaneBoy on GitHub (Oct 25, 2020).
[x]):Description
Hello there. When I tried to update my old version of gogs (1.4.1 Linux Arm7) to the latest version (1.12.5 Arm 6) on my raspberry Pi 3 B+, I've discovered in the gitea logs that I needed to update gitea first to version 1.6.4 and then to the latest version (1.12.5). So this is what I did. Everything seems to work perfectly... Except that when I get to my dashboard, I can see the number of repo I have, but cannot see the list like I was able before in previous version
I can navigate to my repository through the "Explore" tab as you can see here
But as you can see on my first screenshot, I'm unable to have the list of my repositories on my Gitea Dashboard..
Here are the logs you may need, according to the "Debugging problems" section of your docs.
gitea.log
router.log
The actions I did to get these logs is simple: Login...wait few seconds...then logout
Could you help me please to resolve this issue ?
Thank you in advance
...
Screenshots
@lunny commented on GitHub (Oct 25, 2020):
Are there any error log on your log file or console.
@TitaneBoy commented on GitHub (Oct 25, 2020):
@lunny Hi... Didn't see any error log on my log file or console...
@zeripath commented on GitHub (Oct 25, 2020):
Ok first thoughts, In your database could you check that the repository table has the owner_name set correctly for each repository?
Somehow people can end up with migrations incompletely being performed.
@zeripath commented on GitHub (Oct 25, 2020):
The next thing to check is whether it's possible that the issue is actually at your browser. To that end checking the result of:
/api/v1/repos/search?sort=updated&order=desc&uid=1&q=&page=1&limit=15&mode=&archived=false
And
/api/v1/repos/search?sort=updated&order=desc&uid=1&q=&page=1&mode=
Would be helpful to determine if this is a JavaScript or other template issue.
(Although it's notable that both of these requests seem correct to me - suggesting that your js is likely correct )
@aswild commented on GitHub (Oct 25, 2020):
I saw something similar when upgrading to 1.12 or thereabouts - somehow all of my repos got marked as archived and thus wouldn't show up on the dashboard. It happened on two or three installations, all using postgres. This smells like a broken migration, but I didn't dig into it.
I used the psql console to clear the archived column on all the repos (something along the lines of
UPDATE repository SET is_archived = FALSE) but obviously that's not ideal.@TitaneBoy commented on GitHub (Oct 25, 2020):
@zeripath Thanks a lot for your answer and suggestion...Here is what I got:
1 - It seems that "owner_name" value is set properly in the "repository" table

2- Here are the result of the requests to the API
/api/v1/repos/search?sort=updated&order=desc&uid=1&q=&page=1&limit=15&mode=&archived=false
/api/v1/repos/search?sort=updated&order=desc&uid=1&q=&page=1&mode=
@TitaneBoy commented on GitHub (Oct 25, 2020):
Also, just to notify you that when I create a new repository through the Dashboard, I can see the new created repository on the Dashboard, but not the previous repositories I'm trying to display
@zeripath commented on GitHub (Oct 26, 2020):
I wonder if @aswild 's suggestion is happening here and the archived value is somehow different.
@TitaneBoy commented on GitHub (Oct 28, 2020):
From @aswild and @zeripath comment, I decided to take a look to the "is_archived" column value for all my repositories and this is what I got:
When I set the "is_archived" column values to 0, it seems now that I can see all my repositories on the Dashboard 🎉
@TitaneBoy commented on GitHub (Oct 28, 2020):
Thanks a lot @aswild & @zeripath for your support... I think that somehow in the migration process, this column must not be set correctly (at least for MySQL databases)..
@TitaneBoy commented on GitHub (Oct 28, 2020):
Not related anymore to this issue, but I wonder why sometimes, after a successfull login, I am redirected to /user/events
It Happened sometimes since I have done the updated to the latest version. When I disconnect and reconnect after, all seems fine and I get to the dashboard route.. But it seems that after a while, when disconnected, when I log in again, I got redirected to this path (/user/events)...Any ideas of what is happening for this one ? Thanks again for your support and answer...
@aswild commented on GitHub (Oct 28, 2020):
I'm not a maintainer so this is just my unqualified opinion, but I'm not sure that this issue should be closed, unless the migration bug is already being tracked elsewhere.
If there's a bad migration path which can cause all repos to get flagged as archived, that sounds to me like a bug that should be fixed. "Manually fix the database using raw SQL commands" isn't really a great solution, just a quick hack that worked for me personally (since I didn't have any repos that I wanted to be archived).
@TitaneBoy commented on GitHub (Oct 28, 2020):
@aswild I think I'm kind of agree with you...The bug is still here and should be fixed...I can Reopen this issue if needed
@zeripath commented on GitHub (Oct 28, 2020):
This was already fixed in June.
It's fixed in v142.go which is in 1.13 and there is a doctor command to fix it in 1.12.5.
The issue that spurred this was #11824
It was fixed in #11853 which backported to 1.12 the doctor fix as #11853
So no the bug is not still there.