Error while displaying public repo (404) #740

Originally created by @DblK on GitHub (May 24, 2017).

I saw something that could be a bug (maybe Units).
If you following the procedure you will see a 404 error:

Create an organization with user1 (user1 is in owner team)
Create public repo with user1
Add user2 to organization but do not put him in a team
Access with user2 to the organization page
click on the repository
404 error

You can also have a 404, by accessing a public repository in organization with a user not part of it.

It seems that the 404 error is triggered by routers/repo/view.go#L270.

commit: 977dcf96e0

Originally created by @DblK on GitHub (May 24, 2017). I saw something that could be a bug (maybe Units). If you following the procedure you will see a 404 error: 1) Create an organization with user1 (user1 is in owner team) 2) Create public repo with user1 3) Add user2 to organization but do not put him in a team 4) Access with user2 to the organization page 5) click on the repository 6) 404 error You can also have a 404, by accessing a public repository in organization with a user not part of it. It seems that the 404 error is triggered by [routers/repo/view.go#L270](https://github.com/go-gitea/gitea/blob/master/routers/repo/view.go#L270). commit: 977dcf96e0d9c5dded47ac6066fad8979a9f74f9

GiteaMirror added the type/bug label 2025-11-02 03:34:37 -06:00

GiteaMirror closed this issue

GiteaMirror commented

@lunny commented on GitHub (May 24, 2017):

So what's permission should a member of an organization who are not in any team have?

@lunny commented on GitHub (May 24, 2017): So what's permission should a member of an organization who are not in any team have?

GiteaMirror commented

@pgaskin commented on GitHub (May 24, 2017):

I had this bug too after I updated my server yesterday.

@pgaskin commented on GitHub (May 24, 2017): I had this bug too after I updated my server yesterday.

GiteaMirror commented

@DblK commented on GitHub (May 24, 2017):

@lunny, depend on the type of the repo:

If it's private none but should lead to 403 in my opinion instead of 404. (but actually I think they are not displayed)
If it's public, all access like he is not part of the organization at all

And obviously, permit a user outside of an organization to view public repository even if not part of it.

Another way to have 404, seems #1797

@DblK commented on GitHub (May 24, 2017): @lunny, depend on the type of the repo: - If it's private none but should lead to 403 in my opinion instead of 404. (but actually I think they are not displayed) - If it's public, all access like he is not part of the organization at all And obviously, permit a user outside of an organization to view public repository even if not part of it. Another way to have 404, seems #1797

GiteaMirror commented

@lunny commented on GitHub (May 25, 2017):

@DblK, in fact, we need a document to describe all the permission settings we like Gitea do.

@lunny commented on GitHub (May 25, 2017): @DblK, in fact, we need a document to describe all the permission settings we like Gitea do.

GiteaMirror commented

@camlafit commented on GitHub (May 25, 2017):

Hi

In my case if an user is only organization collaborators and in any orgnization team , i can't see any organization repo.
To get repo list , it's possible only if set in organization owner team.

But in this case this user get a 404 on repo page. In log I show :

[...routers/repo/view.go:270 Home()] [E] Home: Cannot find any unit on this repository which you are allowed to acces

It's possible I've followed #1797 before (convert a personal repo to organization repo)

@camlafit commented on GitHub (May 25, 2017): Hi In my case if an user is only organization collaborators and in any orgnization team , i can't see any organization repo. To get repo list , it's possible only if set in organization owner team. But in this case this user get a 404 on repo page. In log I show : ``` [...routers/repo/view.go:270 Home()] [E] Home: Cannot find any unit on this repository which you are allowed to acces ``` It's possible I've followed #1797 before (convert a personal repo to organization repo)

GiteaMirror commented

@lunny commented on GitHub (May 25, 2017):

Which version did you use? I think b0308d86dc has fixed that.

@lunny commented on GitHub (May 25, 2017): Which version did you use? I think https://github.com/go-gitea/gitea/commit/b0308d86dc124f17d6b67e9d1022a4085c9267e1 has fixed that.

GiteaMirror commented

@camlafit commented on GitHub (May 25, 2017):

I've just tried with master, 5min ago

On 1.1.1 it's ok

@camlafit commented on GitHub (May 25, 2017): I've just tried with master, 5min ago On 1.1.1 it's ok

GiteaMirror commented

@lunny commented on GitHub (May 25, 2017):

So a public repo of an organization should be visited by anyone? So that the units of team should be only applied for private repos of organization?

@lunny commented on GitHub (May 25, 2017): So a public repo of an organization should be visited by anyone? So that the units of team should be only applied for private repos of organization?

GiteaMirror commented

@camlafit commented on GitHub (May 25, 2017):

If an user is set as collaborator or as member to any team (owner or not), he should be show repositories.
If a organization is public, their repositories should be public also

@camlafit commented on GitHub (May 25, 2017): If an user is set as collaborator or as member to any team (owner or not), he should be show repositories. If a organization is public, their repositories should be public also

GiteaMirror commented

@lunny commented on GitHub (May 26, 2017):

Please confirm #1812 fix this issue.

@lunny commented on GitHub (May 26, 2017): Please confirm #1812 fix this issue.

GiteaMirror commented

@lunny commented on GitHub (Jun 20, 2017):

I think #1812 resolved this and please feel free to reopen it.

@lunny commented on GitHub (Jun 20, 2017): I think #1812 resolved this and please feel free to reopen it.

GiteaMirror commented

@camlafit commented on GitHub (Jun 20, 2017):

Hi

sorry :/
Can you reopen, just tried with master. 404 is again present.

2017/06/20 10:36:54 [I] Log Mode: File(Info)
2017/06/20 10:36:54 [I] XORM Log Mode: File(Info)
2017/06/20 10:36:54 [I] Cache Service Enabled
2017/06/20 10:36:54 [I] Session Service Enabled
2017/06/20 10:36:54 [I] Migration: add user openid table
2017/06/20 10:36:56 [I] Migration: change the key_id and primary_key_id type
2017/06/20 10:36:58 [I] Migration: add show field in user openid table
2017/06/20 10:36:59 [I] Migration: generate and migrate repo and wiki Git hooks
2017/06/20 10:37:00 [I] Migration: change mirror interval from hours to time.Duration
2017/06/20 10:37:01 [I] Migration: add field for repo size
2017/06/20 10:37:01 [I] This migration could take up to minutes, please be patient.
2017/06/20 10:37:21 [I] Migration: add commit status table
2017/06/20 10:37:22 [I] Migration: add primary key to external login user
2017/06/20 10:37:24 [I] Migration: add field for login source synchronization
2017/06/20 10:37:25 [I] Migration: add units for team
2017/06/20 10:37:26 [I] Migration: remove columns from action
2017/06/20 10:38:19 [I] Migration: give all units to owner teams
2017/06/20 10:38:30 [I] Git Version: 2.1.4
2017/06/20 10:38:31 [I] Run Mode: Production
2017/06/20 10:38:31 [I] Listen: http://0.0.0.0:3001

Use is admin and owner organization, it can't access or change settings on repository. 404 display
I can provide an access to this server.

@camlafit commented on GitHub (Jun 20, 2017): Hi sorry :/ Can you reopen, just tried with master. 404 is again present. ``` 2017/06/20 10:36:54 [I] Log Mode: File(Info) 2017/06/20 10:36:54 [I] XORM Log Mode: File(Info) 2017/06/20 10:36:54 [I] Cache Service Enabled 2017/06/20 10:36:54 [I] Session Service Enabled 2017/06/20 10:36:54 [I] Migration: add user openid table 2017/06/20 10:36:56 [I] Migration: change the key_id and primary_key_id type 2017/06/20 10:36:58 [I] Migration: add show field in user openid table 2017/06/20 10:36:59 [I] Migration: generate and migrate repo and wiki Git hooks 2017/06/20 10:37:00 [I] Migration: change mirror interval from hours to time.Duration 2017/06/20 10:37:01 [I] Migration: add field for repo size 2017/06/20 10:37:01 [I] This migration could take up to minutes, please be patient. 2017/06/20 10:37:21 [I] Migration: add commit status table 2017/06/20 10:37:22 [I] Migration: add primary key to external login user 2017/06/20 10:37:24 [I] Migration: add field for login source synchronization 2017/06/20 10:37:25 [I] Migration: add units for team 2017/06/20 10:37:26 [I] Migration: remove columns from action 2017/06/20 10:38:19 [I] Migration: give all units to owner teams 2017/06/20 10:38:30 [I] Git Version: 2.1.4 2017/06/20 10:38:31 [I] Run Mode: Production 2017/06/20 10:38:31 [I] Listen: http://0.0.0.0:3001 ``` Use is admin and owner organization, it can't access or change settings on repository. 404 display I can provide an access to this server.

GiteaMirror commented

@lunny commented on GitHub (Jun 20, 2017):

Please give more details.

@lunny commented on GitHub (Jun 20, 2017): Please give more details.

GiteaMirror commented

@camlafit commented on GitHub (Jun 26, 2017):

Hi

On my log server I get this :

2017/06/20 10:38:31 [I] Listen: http://0.0.0.0:3001
2017/06/20 11:35:12 [...routers/repo/view.go:274 Home()] [E] Home: Cannot find any unit on this repository which you are allowed to access
2017/06/20 11:35:22 [...routers/repo/view.go:274 Home()] [E] Home: Cannot find any unit on this repository which you are allowed to access
2017/06/20 11:35:37 [...routers/repo/view.go:274 Home()] [E] Home: Cannot find any unit on this repository which you are allowed to access
2017/06/20 11:36:15 [...routers/repo/view.go:274 Home()] [E] Home: Cannot find any unit on this repository which you are allowed to access
2017/06/20 11:36:39 [...routers/repo/view.go:274 Home()] [E] Home: Cannot find any unit on this repository which you are allowed to access
2017/06/20 11:36:43 [...ules/context/repo.go:529 func1()] [E] CheckUnit: You are not allowed to visit this repository unit: 7
[...]

As I don't what kind of information could be useful, I can provide an access to this server.

@camlafit commented on GitHub (Jun 26, 2017): Hi On my log server I get this : ``` 2017/06/20 10:38:31 [I] Listen: http://0.0.0.0:3001 2017/06/20 11:35:12 [...routers/repo/view.go:274 Home()] [E] Home: Cannot find any unit on this repository which you are allowed to access 2017/06/20 11:35:22 [...routers/repo/view.go:274 Home()] [E] Home: Cannot find any unit on this repository which you are allowed to access 2017/06/20 11:35:37 [...routers/repo/view.go:274 Home()] [E] Home: Cannot find any unit on this repository which you are allowed to access 2017/06/20 11:36:15 [...routers/repo/view.go:274 Home()] [E] Home: Cannot find any unit on this repository which you are allowed to access 2017/06/20 11:36:39 [...routers/repo/view.go:274 Home()] [E] Home: Cannot find any unit on this repository which you are allowed to access 2017/06/20 11:36:43 [...ules/context/repo.go:529 func1()] [E] CheckUnit: You are not allowed to visit this repository unit: 7 [...] ``` As I don't what kind of information could be useful, I can provide an access to this server.

GiteaMirror commented

@lunny commented on GitHub (Jun 27, 2017):

@camlafit could you tell me the example?

@lunny commented on GitHub (Jun 27, 2017): @camlafit could you tell me the example?

GiteaMirror commented

@camlafit commented on GitHub (Jun 27, 2017):

Hi

On 1.1.1 , I've an organization with some repositories. Two account an admin (created on installation) and an normal user set as owner on the organization.

admin and user can check all repositories .

If I update to master, these accounts can always view organization and theirs repositories. But to one repositories, show it return a 404 (to each account)
And setting repository is also a 404.

I presume difference between this repository and the others, is the creation step. Normaly from admin account I create repository set directly on the organization. For this repo, I think to have create first on user workspace and move to organization after.

On log I get this error : cannot find any unit.

@camlafit commented on GitHub (Jun 27, 2017): Hi On 1.1.1 , I've an organization with some repositories. Two account an admin (created on installation) and an normal user set as owner on the organization. admin and user can check all repositories . If I update to master, these accounts can always view organization and theirs repositories. But to one repositories, show it return a 404 (to each account) And setting repository is also a 404. I presume difference between this repository and the others, is the creation step. Normaly from admin account I create repository set directly on the organization. For this repo, I think to have create first on user workspace and move to organization after. On log I get this error : cannot find any unit.

GiteaMirror commented

@pgaskin commented on GitHub (Jun 27, 2017):

It seems to be a migration issue with the newer finer repository permission settings.

@pgaskin commented on GitHub (Jun 27, 2017): It seems to be a migration issue with the newer finer repository permission settings.

GiteaMirror commented

@lunny commented on GitHub (Jun 28, 2017):

@camlafit Is this repo a private or a public? Is this repo on one organization?

@lunny commented on GitHub (Jun 28, 2017): @camlafit Is this repo a private or a public? Is this repo on one organization?

GiteaMirror commented

@camlafit commented on GitHub (Jun 28, 2017):

It's in an organization and it's private
Other repo is this organization are also private

@camlafit commented on GitHub (Jun 28, 2017): It's in an organization and it's private Other repo is this organization are also private

GiteaMirror commented

@lunny commented on GitHub (Jun 28, 2017):

Then if all the people is on a team? and is this team have read or write permission to the repo?

@lunny commented on GitHub (Jun 28, 2017): Then if all the people is on a team? and is this team have read or write permission to the repo?

GiteaMirror commented

@camlafit commented on GitHub (Jun 28, 2017):

the two accounts are set in team owner , first is an admin account, other standard.
an other account is set only as collaborator with write right and not set in owner team

In this 3 cases, they get a 404 after update

@camlafit commented on GitHub (Jun 28, 2017): the two accounts are set in team owner , first is an admin account, other standard. an other account is set only as collaborator with write right and not set in owner team In this 3 cases, they get a 404 after update

GiteaMirror commented

@lunny commented on GitHub (Jun 28, 2017):

@camlafit maybe #1873 and #1968 fix this? which version did you test recently?

@lunny commented on GitHub (Jun 28, 2017): @camlafit maybe #1873 and #1968 fix this? which version did you test recently?

GiteaMirror commented

@camlafit commented on GitHub (Jun 28, 2017):

I've tried master version two day ago : 5db8cf3bd1 then these commits should be present.

@camlafit commented on GitHub (Jun 28, 2017): I've tried master version two day ago : 5db8cf3bd1505c5c829de2a928d35ea19808b6c2 then these commits should be present.

GiteaMirror commented

@lunny commented on GitHub (Jul 2, 2017):

@DblK please confirm your issue.
@camlafit have your instance migrated from Gogs?

@lunny commented on GitHub (Jul 2, 2017): @DblK please confirm your issue. @camlafit have your instance migrated from Gogs?

GiteaMirror commented

@camlafit commented on GitHub (Jul 2, 2017):

It's a from scratch gitea installation, gitosis import with api.

@camlafit commented on GitHub (Jul 2, 2017): It's a from scratch gitea installation, gitosis import with api.

GiteaMirror commented

@lafriks commented on GitHub (Jul 2, 2017):

@lunny maybe when creating repository from API units are not correctly created?

@lafriks commented on GitHub (Jul 2, 2017): @lunny maybe when creating repository from API units are not correctly created?

GiteaMirror commented

@camlafit commented on GitHub (Jul 2, 2017):

In this specific case, repo and orgo was created only with gitea interface.

@camlafit commented on GitHub (Jul 2, 2017): In this specific case, repo and orgo was created only with gitea interface.

GiteaMirror commented

@lunny commented on GitHub (Jul 2, 2017):

@lafriks Yes. maybe you are right! I will check that.

@lunny commented on GitHub (Jul 2, 2017): @lafriks Yes. maybe you are right! I will check that.

GiteaMirror commented

@olymk2 commented on GitHub (Jul 12, 2017):

Just hit this myself, anyone find a work around ?

I cant change the settings of the repo as admin because the page just 404s and i get the error below in the logs.

Home: Cannot find any unit on this repository which you are allowed to access

@olymk2 commented on GitHub (Jul 12, 2017): Just hit this myself, anyone find a work around ? I cant change the settings of the repo as admin because the page just 404s and i get the error below in the logs. Home: Cannot find any unit on this repository which you are allowed to access

GiteaMirror commented

@camlafit commented on GitHub (Jul 12, 2017):

Hi

Actual better solution (in my case) revert in 1.1.1 version. I don't try
with 1.1.2

At least allow admin account to go settings page to any repo/organization
should be interessting. So should be possible to correct manualy

@camlafit commented on GitHub (Jul 12, 2017): Hi Actual better solution (in my case) revert in 1.1.1 version. I don't try with 1.1.2 At least allow admin account to go settings page to any repo/organization should be interessting. So should be possible to correct manualy

GiteaMirror commented

@lunny commented on GitHub (Jul 13, 2017):

I have tested many times but didn't reproduce the issue. @camlafit could you show me some tables data on your database so that I can investigate the reason. On team table there is a column named unit_types. If it's empty, you will get 404 on repository page.

@lunny commented on GitHub (Jul 13, 2017): I have tested many times but didn't reproduce the issue. @camlafit could you show me some tables data on your database so that I can investigate the reason. On team table there is a column named `unit_types`. If it's empty, you will get 404 on repository page.

GiteaMirror commented

@camlafit commented on GitHub (Jul 13, 2017):

Hi

select * from team;
| id | org_id | lower_name | name   | description | authorize | num_repos
| num_members | unit_types          |
|  1 |      2 | owners     | Owners |             |         4 |         7
|           3 | [1,2,3,4,5,6,7,8,9] |

It's same list on unit_types to all row.

GiteaMirror commented

@lunny commented on GitHub (Jul 13, 2017):

@camlafit OK. The table is normal. Then could you find the repo_unit table and execute SELECT * FROM repo_unit WHERE repo_id =? the ? should be the 404 repository's id.

@lunny commented on GitHub (Jul 13, 2017): @camlafit OK. The table is normal. Then could you find the `repo_unit` table and execute `SELECT * FROM repo_unit WHERE repo_id =?` the ? should be the 404 repository's id.

GiteaMirror commented

@camlafit commented on GitHub (Jul 17, 2017):

It's empty.

SELECT * FROM repo_unit WHERE repo_id=25;
Empty set (0.00 sec)

@camlafit commented on GitHub (Jul 17, 2017): It's empty. ``` SELECT * FROM repo_unit WHERE repo_id=25; Empty set (0.00 sec) ```

GiteaMirror commented

@lafriks commented on GitHub (Jul 17, 2017):

@camlafit are there any records in rep_unit table?

@lafriks commented on GitHub (Jul 17, 2017): @camlafit are there any records in rep_unit table?

GiteaMirror commented

@camlafit commented on GitHub (Jul 17, 2017):

With repo without problem I get data.

MariaDB [gitea-webelys]> SELECT * FROM repo_unit WHERE repo_id=16;

+----+---------+------+-------+--------+--------------+
| id | repo_id | type | index | config | created_unix |
+----+---------+------+-------+--------+--------------+
| 69 |      16 |    1 |     1 | {}     |   1490025629 |
| 70 |      16 |    2 |     2 | {}     |   1490025630 |
| 71 |      16 |    3 |     3 | {}     |   1490025630 |
| 72 |      16 |    4 |     4 | {}     |   1490025630 |
| 73 |      16 |    5 |     5 | {}     |   1490025630 |
| 74 |      16 |    6 |     6 | {}     |   1490025630 |
| 75 |      16 |    7 |     7 | {}     |   1490025630 |
+----+---------+------+-------+--------+--------------+
7 rows in set (0.00 sec)

@camlafit commented on GitHub (Jul 17, 2017): With repo without problem I get data. MariaDB [gitea-webelys]> SELECT * FROM repo_unit WHERE repo_id=16; ``` +----+---------+------+-------+--------+--------------+ | id | repo_id | type | index | config | created_unix | +----+---------+------+-------+--------+--------------+ | 69 | 16 | 1 | 1 | {} | 1490025629 | | 70 | 16 | 2 | 2 | {} | 1490025630 | | 71 | 16 | 3 | 3 | {} | 1490025630 | | 72 | 16 | 4 | 4 | {} | 1490025630 | | 73 | 16 | 5 | 5 | {} | 1490025630 | | 74 | 16 | 6 | 6 | {} | 1490025630 | | 75 | 16 | 7 | 7 | {} | 1490025630 | +----+---------+------+-------+--------+--------------+ 7 rows in set (0.00 sec) ```

GiteaMirror commented

@lafriks commented on GitHub (Jul 17, 2017):

than it looks like it is migration issue and unit types must be added to that repository

@lafriks commented on GitHub (Jul 17, 2017): than it looks like it is migration issue and unit types must be added to that repository

GiteaMirror commented

@camlafit commented on GitHub (Jul 17, 2017):

How ?

But if I understand your queries, if we have data in team.unit_types we must get also data in repo_unit ? Is not possible to check it and update database ?

At least a generic SQL workaround could be useful :)

@camlafit commented on GitHub (Jul 17, 2017): How ? But if I understand your queries, if we have data in team.unit_types we must get also data in repo_unit ? Is not possible to check it and update database ? At least a generic SQL workaround could be useful :)

GiteaMirror commented

@lunny commented on GitHub (Jul 18, 2017):

@lafriks @camlafit we could do two work, first is fix the bug, and second is add an reset button on admin panel to reset all repo's units. I will send a PR to do them.

@lunny commented on GitHub (Jul 18, 2017): @lafriks @camlafit we could do two work, first is fix the bug, and second is add an reset button on admin panel to reset all repo's units. I will send a PR to do them.

GiteaMirror commented

@olymk2 commented on GitHub (Jul 18, 2017):

exactly the same for missing missing entries in the unit_types tables, is there a way to regenerate the correct entries ?

@olymk2 commented on GitHub (Jul 18, 2017): exactly the same for missing missing entries in the unit_types tables, is there a way to regenerate the correct entries ?

GiteaMirror commented

@lafriks commented on GitHub (Jul 18, 2017):

@lunny why reset all repo units? That would be very dangerous as it would lose repository settings on disabled (wiki/issues) etc

@lafriks commented on GitHub (Jul 18, 2017): @lunny why reset **all** repo units? That would be very dangerous as it would lose repository settings on disabled (wiki/issues) etc

GiteaMirror commented

@camlafit commented on GitHub (Jul 18, 2017):

Hi

A reset GUI looks interestting :) In this case could be accessible repo by
repo from admin/repos page. Repo settings page could be not accessible if
units are missing.
This option could be useful in this case but also if user or admin miss its
configuration and lost access.

@camlafit commented on GitHub (Jul 18, 2017): Hi A reset GUI looks interestting :) In this case could be accessible repo by repo from `admin/repos` page. Repo settings page could be not accessible if units are missing. This option could be useful in this case but also if user or admin miss its configuration and lost access.

GiteaMirror commented

@rhaamo commented on GitHub (Jul 20, 2017):

Hi,

I've got the same issue (table repo_unit empty) from a migration from gogs.

I "manually" created the missing entries in the table with inserts like, for each repository.id :

insert into repo_unit (`repo_id`, `type`, `index`, `config`) values (73, 1, 1, '{}');

With 1,1 replaced by 1,1 to 7,7.

Should that be sufficient ?

@rhaamo commented on GitHub (Jul 20, 2017): Hi, I've got the same issue (table repo_unit empty) from a migration from gogs. I "manually" created the missing entries in the table with inserts like, for each repository.id : ``` insert into repo_unit (`repo_id`, `type`, `index`, `config`) values (73, 1, 1, '{}'); ``` With ```1,1``` replaced by ```1,1``` to ```7,7```. Should that be sufficient ?

GiteaMirror commented

@lunny commented on GitHub (Jul 20, 2017):

Yes, it's enough for working. @rhaamo

@lunny commented on GitHub (Jul 20, 2017): Yes, it's enough for working. @rhaamo

GiteaMirror commented

@camlafit commented on GitHub (Jul 20, 2017):

Hi

I've done on my server and looks ok. On 28 repo, were 6 without unit values.

@camlafit commented on GitHub (Jul 20, 2017): Hi I've done on my server and looks ok. On 28 repo, were 6 without unit values.

GiteaMirror commented

@olymk2 commented on GitHub (Jul 20, 2017):

@rhaamo cheers, based on that i made a quicker version for anyone that wants it in the future.

tested on sqlite db only


# get repository's ids missing unit types
select repository.id from repository left join repo_unit
on repository.id=repo_id where repo_id is null ;

# create records so you can accually edit and access them again
insert into repo_unit (`repo_id`, `type`, `index`, `config`) 
select repository.id, types.*, '{}' from repository
left join repo_unit on repository.id=repo_id 
left join (
  select 1,1
  UNION ALL select 2,2
  UNION ALL select 3,3
  UNION ALL select 4,4
  UNION ALL select 5,5
  UNION ALL select 6,6
  UNION ALL select 7,7) as types
where repo_id is null;

this kicked all my repo's back into action \o/

@olymk2 commented on GitHub (Jul 20, 2017): @rhaamo cheers, based on that i made a quicker version for anyone that wants it in the future. tested on sqlite db only ``` # get repository's ids missing unit types select repository.id from repository left join repo_unit on repository.id=repo_id where repo_id is null ; # create records so you can accually edit and access them again insert into repo_unit (`repo_id`, `type`, `index`, `config`) select repository.id, types.*, '{}' from repository left join repo_unit on repository.id=repo_id left join ( select 1,1 UNION ALL select 2,2 UNION ALL select 3,3 UNION ALL select 4,4 UNION ALL select 5,5 UNION ALL select 6,6 UNION ALL select 7,7) as types where repo_id is null; ``` this kicked all my repo's back into action \o/

GiteaMirror commented

@silverwind commented on GitHub (Aug 11, 2017):

I also got hit by this after updating a instance. The query in https://github.com/go-gitea/gitea/issues/1794#issuecomment-316824479 didn't work on MySQL, so I ran queries suggested in https://github.com/go-gitea/gitea/issues/1794#issuecomment-316613399, which fixed it.

@silverwind commented on GitHub (Aug 11, 2017): I also got hit by this after updating a instance. The query in https://github.com/go-gitea/gitea/issues/1794#issuecomment-316824479 didn't work on MySQL, so I ran queries suggested in https://github.com/go-gitea/gitea/issues/1794#issuecomment-316613399, which fixed it.

GiteaMirror commented

@lunny commented on GitHub (Aug 11, 2017):

I think that's because you lost migration v16 https://github.com/go-gitea/gitea/blob/master/models/migrations/v16.go#L47.

@lunny commented on GitHub (Aug 11, 2017): I think that's because you lost migration v16 https://github.com/go-gitea/gitea/blob/master/models/migrations/v16.go#L47.

GiteaMirror commented

@silverwind commented on GitHub (Aug 11, 2017):

I was upgrading from 1.1.0+135-gfcc7cda to 1.1.0+474-gbe29d5f7, if that's of any help. The affected repos were definitely working before.

@silverwind commented on GitHub (Aug 11, 2017): I was upgrading from `1.1.0+135-gfcc7cda` to `1.1.0+474-gbe29d5f7`, if that's of any help. The affected repos were definitely working before.

GiteaMirror commented