Dashboard not displaying commit activity details #2650

New Issue

GiteaMirror · 2025-11-02T04:43:27-06:00

GiteaMirror commented

2025-11-02 04:43:27 -06:00

Originally created by @oliviergareau on GitHub (Dec 11, 2018).

Gitea version (or commit ref): v1.6.1
Git version: 2.11.0
Operating system: Debian GNU/Linux 9 (stretch) 4.14.52
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: LINK

Description

Upgraded from v1.4.3 to v1.6.1. Everything seems to work fine, except the Dashboard, which won't display recent commit details anymore. Log details are attached in the gist above, and a screenshot is available on imgur at the link below. 😃

Screenshots

https://i.imgur.com/rnZsONb.png

Originally created by @oliviergareau on GitHub (Dec 11, 2018).  - Gitea version (or commit ref): v1.6.1 - Git version: 2.11.0 - Operating system: Debian GNU/Linux 9 (stretch) 4.14.52 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: [LINK](https://gist.github.com/oliviergareau/018598e49dc7602f48dfec947e3327a9) ## Description Upgraded from v1.4.3 to v1.6.1. Everything seems to work fine, except the Dashboard, which won't display recent commit details anymore. Log details are attached in the gist above, and a screenshot is available on imgur at the link below. :smiley: ## Screenshots https://i.imgur.com/rnZsONb.png

GiteaMirror added the issue/stale label 2025-11-02 04:43:28 -06:00

GiteaMirror closed this issue

2025-11-02 04:43:28 -06:00

GiteaMirror commented

2025-11-02 04:43:28 -06:00

@lunny commented on GitHub (Dec 12, 2018):

could you reproduce that on https://try.gitea.io ? I cannot reproduce it locally.

@lunny commented on GitHub (Dec 12, 2018): could you reproduce that on https://try.gitea.io ? I cannot reproduce it locally.

GiteaMirror commented

2025-11-02 04:43:29 -06:00

@oliviergareau commented on GitHub (Dec 12, 2018):

I can't reproduce it on try.gitea.io.

@oliviergareau commented on GitHub (Dec 12, 2018): I can't reproduce it on try.gitea.io.

GiteaMirror commented

2025-11-02 04:43:29 -06:00

@smorks commented on GitHub (Dec 13, 2018):

I'm having the same issue on 1.6.0, running on Arch Linux, with MySQL as the database.

I checked the "action" table (i'm assuming that's where the info is coming from) and no commits since i upgrade from 1.5.3 to 1.6.0 have been added to the action table.

i couldn't find any relevant errors in any gitea log files either.

i'll try and do some deeper investigation to see if I can figure out why it's happening.

@smorks commented on GitHub (Dec 13, 2018): I'm having the same issue on 1.6.0, running on Arch Linux, with MySQL as the database. I checked the "action" table (i'm assuming that's where the info is coming from) and no commits since i upgrade from 1.5.3 to 1.6.0 have been added to the action table. i couldn't find any relevant errors in any gitea log files either. i'll try and do some deeper investigation to see if I can figure out why it's happening.

GiteaMirror commented

2025-11-02 04:43:29 -06:00

@smorks commented on GitHub (Dec 14, 2018):

it appears that everything is working for me again. my problem was i have a non-standard path for my repositories, and so I needed to add a ReadWritePaths= option to my gitea.service file for systemd to allow gitea to write to that path.

@oliviergareau i realized it was a permissions issue because I tried to create a new test repository, and gitea gave me a 500 error and there was a "handleCreateError" error in my log file.

@smorks commented on GitHub (Dec 14, 2018): it appears that everything is working for me again. my problem was i have a non-standard path for my repositories, and so I needed to add a ReadWritePaths= option to my gitea.service file for systemd to allow gitea to write to that path. @oliviergareau i realized it was a permissions issue because I tried to create a new test repository, and gitea gave me a 500 error and there was a "handleCreateError" error in my log file.

GiteaMirror commented

2025-11-02 04:43:29 -06:00

@oliviergareau commented on GitHub (Dec 14, 2018):

I just tried creating a new repo and pushing to it. It seems that the commits are showing up in the dashboard, but commits from before migrating to 1.6.1 are not showing up. So in my case it does not seem to be a permissions issue.

Also, looking at my log gist in OP, there seems to be an error:
ERROR: invalid character '\n' in string literal

Screenshot of newer commits appearing: https://i.imgur.com/QjrJBpW.png

So I guess it is safe to say that this bug is for the most part harmless, since soon enough there will not be any old commits displayed on my dashboard, right?

@oliviergareau commented on GitHub (Dec 14, 2018): I just tried creating a new repo and pushing to it. It seems that the commits are showing up in the dashboard, but commits from **before migrating to 1.6.1 are not showing up**. So in my case it does not seem to be a permissions issue. Also, looking at my log gist in OP, there seems to be an error: `ERROR: invalid character '\n' in string literal` Screenshot of newer commits appearing: https://i.imgur.com/QjrJBpW.png So I guess it is safe to say that this bug is for the most part harmless, since soon enough there will not be any old commits displayed on my dashboard, right?

GiteaMirror commented

2025-11-02 04:43:29 -06:00

@stale[bot] commented on GitHub (Feb 12, 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 (Feb 12, 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

2025-11-02 04:43:29 -06:00

@stale[bot] commented on GitHub (Feb 26, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 26, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 12:12:38 -06:00

[PR #2651] [MERGED] Fix index column deletion #16524

Sign in to join this conversation.