No longer showing contributions, even with recent checkins #11956

New Issue

GiteaMirror · 2025-11-02T09:52:50-06:00

GiteaMirror commented

2025-11-02 09:52:50 -06:00

Originally created by @binarydad on GitHub (Nov 5, 2023).

Description

I realized the contribution graph on the home page no longer shows commits, even though there are in fact recent commits - they are just not reflected in the graph of in the list of recent projects. I'm not sure which version this issue started with. Thank you.

Gitea Version

1.20.5

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

Git Version

No response

Operating System

No response

How are you running Gitea?

Self-hosted in docker

Database

SQLite

Originally created by @binarydad on GitHub (Nov 5, 2023). ### Description I realized the contribution graph on the home page no longer shows commits, even though there are in fact recent commits - they are just not reflected in the graph of in the list of recent projects. I'm not sure which version this issue started with. Thank you. ### Gitea Version 1.20.5 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots ![image](https://github.com/go-gitea/gitea/assets/1760607/29a5a97d-5052-4a51-bdb0-0bdda88c98c7) ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Self-hosted in docker ### Database SQLite

GiteaMirror added the issue/needs-feedback type/bug labels 2025-11-02 09:52:50 -06:00

GiteaMirror closed this issue

2025-11-02 09:52:50 -06:00

GiteaMirror commented

2025-11-02 09:52:51 -06:00

@lng2020 commented on GitHub (Nov 6, 2023):

Can u provide more detailed information about the commitment Last month commit? Last month can be 10.1 or 10.30 and I can't tell what the problem is from your screenshot.

@lng2020 commented on GitHub (Nov 6, 2023): Can u provide more detailed information about the commitment `Last month` commit? `Last month` can be 10.1 or 10.30 and I can't tell what the problem is from your screenshot.

GiteaMirror commented

2025-11-02 09:52:51 -06:00

@dousha commented on GitHub (Nov 7, 2023):

I'm having an even stranger issue that none of my code pushes would show on the timeline. Repositories would just say it was "updated last month" even if I'm pushing new code into them every day. My instance was set up after 1.20.5 came out (on 2023-10-05), so my timeline is basically blank with only repository creation and merge requests shown.

I believe it is caused by the same underlying issue.

@dousha commented on GitHub (Nov 7, 2023): I'm having an even stranger issue that none of my code pushes would show on the timeline. Repositories would just say it was "updated last month" even if I'm pushing new code into them every day. My instance was set up after 1.20.5 came out (on 2023-10-05), so my timeline is basically blank with only repository creation and merge requests shown. I believe it is caused by the same underlying issue.

GiteaMirror commented

2025-11-02 09:52:51 -06:00

@wxiaoguang commented on GitHub (Nov 7, 2023):

https://docs.gitea.com/help/faq#push-hook--webhook-arent-running

@wxiaoguang commented on GitHub (Nov 7, 2023): https://docs.gitea.com/help/faq#push-hook--webhook-arent-running

GiteaMirror commented

2025-11-02 09:52:51 -06:00

@dousha commented on GitHub (Nov 8, 2023):

https://docs.gitea.com/help/faq#push-hook--webhook-arent-running

Thank you. After a bit of digging, I have located the problem. It was because the file system used by gitea was mounted with user option which implies noexec. Fixing the mount options and restarting the docker image resolved the problem.

It caught me by surprise. I've checked the log but there was nothing shown. It would be nice if gitea could check if the file system is configured correctly, or at least print a warning in the log.

@dousha commented on GitHub (Nov 8, 2023): > https://docs.gitea.com/help/faq#push-hook--webhook-arent-running Thank you. After a bit of digging, I have located the problem. It was because the file system used by gitea was mounted with `user` option which implies `noexec`. Fixing the mount options and restarting the docker image resolved the problem. It caught me by surprise. I've checked the log but there was nothing shown. It would be nice if gitea could check if the file system is configured correctly, or at least print a warning in the log.

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#11956