-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Cannot see Repositories on Gitea Dashboard after Gitea update (1.4.1 -> 1.6.4 -> 1.12.5) #13300
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
Are there any error log on your log file or console. |
@lunny Hi... Didn't see any error log on my log file or console... |
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. |
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 ) |
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 |
@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=
|
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 |
I wonder if @aswild 's suggestion is happening here and the archived value is somehow different. |
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... |
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). |
@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 |
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. |
[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
The text was updated successfully, but these errors were encountered: