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

[JellyBrick]

• 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

[jolheiser]

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

Can you check your action table?

[moepman]

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]

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 Migration fixes for gogs (0.11.66) to gitea (1.6.0) #5318
• start gitea 1.6.4 (since Migration fixes for gogs (0.11.66) to gitea (1.6.0) #5318 seems to imply this is supported without going through previous versions)
• sop gitea
• start gitea 1.11.6 (with Remove migration support from versions earlier than 1.6.0 #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 How can i switch from gogs to gitea with less pain? #3558 for Details)
• Run "Resynchronize pre-receive, update and post-receive hooks of all repositories" (or PRs will break push commits after upgrade from 1.8.3 to 1.9.3 errors happen #8208)

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

[moepman]

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;