After updating from gogs 0.11.91 to gitea 1.13, can't access my dashboard #5445

New Issue

GiteaMirror · 2025-11-02T06:25:07-06:00

GiteaMirror commented

2025-11-02 06:25:07 -06:00

Originally created by @JellyBrick on GitHub (May 22, 2020).

Gitea version (or commit ref): 1.13.0+dev-37-g6af13dbac
Gogs version: 0.11.91
Git version: 2.17.1
Operating system: Ubuntu 18.10
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:

Description

If I have signed out, I can access my dashboard.
If I haven't signed out, an error occurs when accessing my dashboard.

(I followed Upgrade from gogs doc and #4286)

Error message:

template: user/dashboard/feeds:94:35: executing "user/dashboard/feeds" at <index .GetIssueInfos 1>: error calling index: reflect: slice index out of range

...

Screenshots

If I have signed out

If I haven't signed out

Originally created by @JellyBrick on GitHub (May 22, 2020).   - Gitea version (or commit ref): 1.13.0+dev-37-g6af13dbac - Gogs version: 0.11.91 - Git version: 2.17.1 - Operating system: Ubuntu 18.10 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description If I have signed out, I can access my dashboard. If I haven't signed out, an error occurs when accessing my dashboard. (I followed `Upgrade from gogs` doc and #4286) Error message: ``` template: user/dashboard/feeds:94:35: executing "user/dashboard/feeds" at <index .GetIssueInfos 1>: error calling index: reflect: slice index out of range ``` ... ## Screenshots ### If I have signed out ![image](https://user-images.githubusercontent.com/16558115/82701685-9b799a80-9cab-11ea-997c-a0c51efbc2f2.png) ### If I haven't signed out ![image](https://user-images.githubusercontent.com/16558115/82701811-d11e8380-9cab-11ea-85a5-6b5f1bd73808.png)

GiteaMirror added the issue/needs-feedback label 2025-11-02 06:25:07 -06:00

GiteaMirror closed this issue

2025-11-02 06:25:08 -06:00

GiteaMirror commented

2025-11-02 06:25:09 -06:00

@jolheiser commented on GitHub (May 24, 2020):

It looks like GetIssueInfos tries to split up content in the action table based on a pipe (|)

Can you check your action table?

@jolheiser commented on GitHub (May 24, 2020): It looks like `GetIssueInfos` tries to split up `content` in the `action` table based on a pipe (`|`) Can you check your `action` table?

GiteaMirror commented

2025-11-02 06:25:09 -06:00

@moepman commented on GitHub (Jun 7, 2020):

I have the exact same error after upgrading from Gogs 0.11.91 using PostgreSQL to Gitea 1.0.2 -> 1.1.4 -> 1.2.3 -> 1.3.3 -> 1.4.3 -> 1.5.3 -> 1.6.4 -> 1.11.6.

What should I look for in the action table?

@moepman commented on GitHub (Jun 7, 2020): I have the exact same error after upgrading from Gogs 0.11.91 using PostgreSQL to Gitea 1.0.2 -> 1.1.4 -> 1.2.3 -> 1.3.3 -> 1.4.3 -> 1.5.3 -> 1.6.4 -> 1.11.6. What should I look for in the action table?

GiteaMirror commented

2025-11-02 06:25:09 -06:00

@moepman commented on GitHub (Jun 8, 2020):

I have found a solution to the problem. I cloned my gogs VM again, and went a different route for the upgrade to gitea:

stop gogs
create a new minimal app.ini
set DB version to 13 as per #5318
start gitea 1.6.4 (since #5318 seems to imply this is supported without going through previous versions)
sop gitea
start gitea 1.11.6 (with #10026 dropping migrations from before 1.6.x in current code that to me implies going from 1.6.4 to 1.11.6 should be safe)
Run "Reinitialize all missing Git repositories for which records exist"
Remove gogs hooks: find $REPO_DIR -path \*-receive.d/\*-receive -delete (see #3558 for Details)
Run "Resynchronize pre-receive, update and post-receive hooks of all repositories" (or PRs will break #8208)

The issue with the dashboard is gone now for my user.

@moepman commented on GitHub (Jun 8, 2020): I have found a solution to the problem. I cloned my gogs VM again, and went a different route for the upgrade to gitea: * stop gogs * create a new minimal app.ini * set DB version to 13 as per #5318 * start gitea 1.6.4 (since #5318 seems to imply this is supported without going through previous versions) * sop gitea * start gitea 1.11.6 (with #10026 dropping migrations from before 1.6.x in current code that to me implies going from 1.6.4 to 1.11.6 should be safe) * Run "Reinitialize all missing Git repositories for which records exist" * Remove gogs hooks: `find $REPO_DIR -path \*-receive.d/\*-receive -delete` (see #3558 for Details) * Run "Resynchronize pre-receive, update and post-receive hooks of all repositories" (or PRs will break #8208) The issue with the dashboard is gone now for my user.

GiteaMirror commented

2025-11-02 06:25:09 -06:00

@moepman commented on GitHub (Jun 9, 2020):

If it helps: I have found out that the op_type (in the action table) used in gogs 0.11.91 and gitea 1.11.x/1.12.x differ for op_type > 15.
Will try migration again with the following SQL script (before starting gitea 1.6.4):

-- fix differnt op_type usage between gogs v19 and gitea
UPDATE action SET op_type = 1000 + op_type WHERE op_type > 15;
UPDATE action SET op_type = 16 WHERE op_type = 1018;
UPDATE action SET op_type = 17 WHERE op_type = 1017;
UPDATE action SET op_type = 1 WHERE op_type = 1019;
UPDATE action SET op_type = 18 WHERE op_type = 1020;
UPDATE action SET op_type = 19 WHERE op_type = 1021;
UPDATE action SET op_type = 20 WHERE op_type = 1022;

@moepman commented on GitHub (Jun 9, 2020): If it helps: I have found out that the `op_type` (in the `action` table) used in gogs 0.11.91 and gitea 1.11.x/1.12.x differ for `op_type > 15`. Will try migration again with the following SQL script (before starting gitea 1.6.4): ```SQL -- fix differnt op_type usage between gogs v19 and gitea UPDATE action SET op_type = 1000 + op_type WHERE op_type > 15; UPDATE action SET op_type = 16 WHERE op_type = 1018; UPDATE action SET op_type = 17 WHERE op_type = 1017; UPDATE action SET op_type = 1 WHERE op_type = 1019; UPDATE action SET op_type = 18 WHERE op_type = 1020; UPDATE action SET op_type = 19 WHERE op_type = 1021; UPDATE action SET op_type = 20 WHERE op_type = 1022; ```

GiteaMirror referenced this issue

2025-11-02 15:52:11 -06:00

[PR #5445] [MERGED] [backport]word-break the WebHook url to prevent a ui-break #17798

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#5445