Opening empty repository -> error 500

[alneo]

• Gitea version (or commit ref): 1.9.1
• Git version:
• Operating system:
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant
• Log gist:
  2019/08/19 16:18:03 ...ules/context/repo.go:594:func1() [E] GetBranches: No branches in non-empty repository /gitea-repositories/xxxxxxxx/xxxxxxxxxxx
  2019/08/19 16:18:03 ...s/context/context.go:137:HTML() [D] Template: status/500

Description

I did an update from 1.7.4 to 1.8.3 and 1.9.1 and in some repositories I get a 500 error
files exist along the path gitea-repositories
How to restore repositories?

Screenshots

[typeless]

If you can open the settings page of the repository, try to select a default branch.

Edit:
The related code is at https://github.com/go-gitea/gitea/blob/release/v1.9/modules/context/repo.go#L592.

I don't know why it would be a branchless repository.
What would you see by typing GIT_DIR=/gitea-repositories/xxxxxxxx/xxxxxxxxxxx git branch -a at your command line?

[abread]

Happened to me as well. I'm not sure if it was introduced in 1.8 or 1.9.
Settings are inacessible and there are indeed no branches.

A branch is just a "pointer" to a commit, so until something is commited no branches actually exist

[lunny]

@abread how did you create that repository on gitea?

[abread]

Just the regular create button, without initializing it. At least one with 1.7.x/1.8.x, the others with older versions.

…

On August 23, 2019 2:40:39 AM UTC, Lunny Xiao ***@***.***> wrote: @abread how did you create that repository on gitea? -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #7914 (comment)

-- Sent from my Android device with K-9 Mail. Please excuse my brevity.

[typeless]

Can you query the database for the is_empty column of the repo table?
This column has been migrated from is_bare recently.
The index would probably need to be re-generated.

As per https://github.com/go-gitea/gitea/blob/master/modules/context/repo.go#L563.
It should return from the function normally if the repo is empty.

[abread]

That seems to be the issue is_empty is NULL on all repositories except the ones that are not empty and were visited, which are 0.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

[nuno-silva]

Please don't close.

[zeripath]

@nuno-silva are you still suffering this? What version of Gitea are you using?

Have you tried setting the values of is_bare manually?

[nuno-silva]

@zeripath yes, I have one repo (laboratorios) still affected, using:

• gitea 1.9.3
• Go1.12.8

The repository has no commits (yet).

MariaDB [gitea]> select id,lower_name,is_bare,is_mirror,is_fork,is_empty,is_archived from repository where lower_name like 'laboratorios' or lower_name like 'testing123';
+-----+--------------+---------+-----------+---------+----------+-------------+
| id  | lower_name   | is_bare | is_mirror | is_fork | is_empty | is_archived |
+-----+--------------+---------+-----------+---------+----------+-------------+
| 484 | laboratorios |       1 |         0 |       0 |     NULL |        NULL |
| 584 | testing123   |    NULL |         0 |       0 |        1 |           0 |
+-----+--------------+---------+-----------+---------+----------+-------------+
2 rows in set (0.00 sec)

If I create a new repo (testing123) it works.

note: this is the same gitea instance as @abread .

edit: testing on a new repo

[holmesb]

In my case, the problem was a mismatch between the port memcached was listening on and app.ini setting:

[cache]
HOST     = 127.0.0.1:<PORT>

[zeripath]

Just set the is_empty value to the correct thing for that repo and it will never happen again. You suffered a migration bug when changing versions - that migration is now fixed and should never happen again.

Edit: mistake in value

[nuno-silva]

@zeripath alright. You mean set is_empty, right (as @zeripath said)?. That works. Thank you!