Opening empty repository -&gt; error 500 #3811

@typeless commented on GitHub (Aug 20, 2019):

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?

@typeless commented on GitHub (Aug 20, 2019): 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?

GiteaMirror commented

@abread commented on GitHub (Aug 22, 2019):

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

@abread commented on GitHub (Aug 22, 2019): 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

GiteaMirror commented

@lunny commented on GitHub (Aug 23, 2019):

@abread how did you create that repository on gitea?

@lunny commented on GitHub (Aug 23, 2019): @abread how did you create that repository on gitea?

GiteaMirror commented

@abread commented on GitHub (Aug 23, 2019):

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 notifications@github.com 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:
https://github.com/go-gitea/gitea/issues/7914#issuecomment-524150235

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

@abread commented on GitHub (Aug 23, 2019): 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 <notifications@github.com> 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: >https://github.com/go-gitea/gitea/issues/7914#issuecomment-524150235 -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

GiteaMirror commented

@typeless commented on GitHub (Aug 23, 2019):

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.

@typeless commented on GitHub (Aug 23, 2019): 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.

GiteaMirror commented

@abread commented on GitHub (Aug 23, 2019):

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.

@abread commented on GitHub (Aug 23, 2019): 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`.

GiteaMirror commented

@stale[bot] commented on GitHub (Oct 22, 2019):

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.

@stale[bot] commented on GitHub (Oct 22, 2019): 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.

GiteaMirror commented

@nuno-silva commented on GitHub (Oct 22, 2019):

Please don't close.

@nuno-silva commented on GitHub (Oct 22, 2019): Please don't close.

GiteaMirror commented

@zeripath commented on GitHub (Oct 22, 2019):

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

Have you tried setting the values of is_bare manually?

@zeripath commented on GitHub (Oct 22, 2019): @nuno-silva are you still suffering this? What version of Gitea are you using? Have you tried setting the values of is_bare manually?

GiteaMirror commented

@nuno-silva commented on GitHub (Oct 22, 2019):

@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

@nuno-silva commented on GitHub (Oct 22, 2019): @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

GiteaMirror commented

@holmesb commented on GitHub (Oct 22, 2019):

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>

@holmesb commented on GitHub (Oct 22, 2019): In [my case](https://github.com/go-gitea/gitea/issues/8023), the problem was a mismatch between the port memcached was listening on and app.ini setting: ``` [cache] HOST = 127.0.0.1:<PORT> ````

GiteaMirror commented