last updated in repo list is not updated #2946

New Issue

GiteaMirror · 2025-11-02T04:54:58-06:00

GiteaMirror commented

2025-11-02 04:54:58 -06:00

Originally created by @noerw on GitHub (Feb 20, 2019).

Gitea version (or commit ref): 1.7.2
Git version: 2.16.5
Operating system: debian
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

On my instance, the Updated X time ago information (as shown in the explore page for example) is not updated when I push commits to repositories.
This happens since at least v1.6, as the last updated timestamp currently says "Updated 3 months ago".
I am not sure why I can't reproduce this on try.gitea.io, could it be a DB migration path problem?

Originally created by @noerw on GitHub (Feb 20, 2019).  - Gitea version (or commit ref): 1.7.2 - Git version: 2.16.5 - Operating system: debian - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ## Description On my instance, the `Updated X time ago` information (as shown in the explore page for example) is not updated when I push commits to repositories. This happens since at least v1.6, as the last updated timestamp currently says "Updated 3 months ago". I am not sure why I can't reproduce this on try.gitea.io, could it be a DB migration path problem?

GiteaMirror added the type/question issue/stale labels 2025-11-02 04:54:58 -06:00

GiteaMirror closed this issue

2025-11-02 04:54:58 -06:00

GiteaMirror commented

2025-11-02 04:54:59 -06:00

@noerw commented on GitHub (Feb 20, 2019):

It does not seem to be a migration issue, as it also happens with newly created repos.
This does not occur when committing in the webinterface.

Could this be related to incorrect ssh / authorized_keys setup?

@noerw commented on GitHub (Feb 20, 2019): - It does not seem to be a migration issue, as it also happens with newly created repos. - This does not occur when committing in the webinterface. Could this be related to incorrect ssh / authorized_keys setup?

GiteaMirror commented

2025-11-02 04:54:59 -06:00

@lafriks commented on GitHub (Feb 20, 2019):

check that there are no errors in gitea.log or serv.log when pushing to repositories

@lafriks commented on GitHub (Feb 20, 2019): check that there are no errors in gitea.log or serv.log when pushing to repositories

GiteaMirror commented

2025-11-02 04:54:59 -06:00

@lafriks commented on GitHub (Feb 20, 2019):

also check that your filesystem does not have noexec in fstab for partition where repositories are stored

@lafriks commented on GitHub (Feb 20, 2019): also check that your filesystem does not have noexec in fstab for partition where repositories are stored

GiteaMirror commented

2025-11-02 04:54:59 -06:00

@stale[bot] commented on GitHub (Apr 21, 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 (Apr 21, 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:54:59 -06:00

@stale[bot] commented on GitHub (May 5, 2019):

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

@stale[bot] commented on GitHub (May 5, 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:16:07 -06:00

[PR #2946] [MERGED] Drop deprecated GOGS_WORK_DIR use #16675

Sign in to join this conversation.