Repositories not showing langauge statistics #5612

Closed
opened 2025-11-02 06:30:53 -06:00 by GiteaMirror · 7 comments
Owner

Originally created by @SuNNjek on GitHub (Jun 22, 2020).

  • Gitea version (or commit ref): 1.12.1
  • Git version: -
  • Operating system: Raspbian 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

Shortly after upgrading from 1.11.7 to 1.12.0 the web interface hung (I assume while analysing the languages used in my repos) so I decided to restart Gitea, which made it respond again. However, I just realized my older repositories don't show any language statistics at all, even though they should.
I don't know if there currently is a way to manually trigger another analysis (if there is I can't find it), but if there isn't, it would be nice if you could do that from the admin page.

Screenshots

Originally created by @SuNNjek on GitHub (Jun 22, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.12.1 - Git version: - - Operating system: Raspbian 10 - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description Shortly after upgrading from 1.11.7 to 1.12.0 the web interface hung (I assume while analysing the languages used in my repos) so I decided to restart Gitea, which made it respond again. However, I just realized my older repositories don't show any language statistics at all, even though they should. I don't know if there currently is a way to manually trigger another analysis (if there is I can't find it), but if there isn't, it would be nice if you could do that from the admin page. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
Author
Owner

@lafriks commented on GitHub (Jun 22, 2020):

If no language stats are calculated for repository it should calculate automatically on Gitea restart

@lafriks commented on GitHub (Jun 22, 2020): If no language stats are calculated for repository it should calculate automatically on Gitea restart
Author
Owner

@SuNNjek commented on GitHub (Jun 23, 2020):

@lafriks Having restarted my Gitea, I unfortunately cannot confirm this, the statistics are still missing

@SuNNjek commented on GitHub (Jun 23, 2020): @lafriks Having restarted my Gitea, I unfortunately cannot confirm this, the statistics are still missing
Author
Owner

@lafriks commented on GitHub (Jun 23, 2020):

Can you check does table repo_indexer_status has record for specific repository

@lafriks commented on GitHub (Jun 23, 2020): Can you check does table `repo_indexer_status` has record for specific repository
Author
Owner

@SuNNjek commented on GitHub (Jun 23, 2020):

@lafriks No, there are too few entries in the table. I also checked a specific repo and there is no entry with the repo id in that table.

@SuNNjek commented on GitHub (Jun 23, 2020): @lafriks No, there are too few entries in the table. I also checked a specific repo and there is no entry with the repo id in that table.
Author
Owner

@SuNNjek commented on GitHub (Jun 24, 2020):

@lafriks I just noticed something else. I don't know if this has anything to do with it, but for some reason on my dashboard I see this:
grafik

Notice it says I have only 13 repos (the repo_indexer_status table also only has 13 entries 🤔) when my user does in fact have 39 repositories (as it correctly says at the top)

@SuNNjek commented on GitHub (Jun 24, 2020): @lafriks I just noticed something else. I don't know if this has anything to do with it, but for some reason on my dashboard I see this: ![grafik](https://user-images.githubusercontent.com/20151081/85528867-c0e02800-b60c-11ea-8d0b-5539802633e6.png) Notice it says I have only 13 repos (the `repo_indexer_status` table also only has 13 entries :thinking:) when my user does in fact have 39 repositories (as it correctly says at the top)
Author
Owner

@SuNNjek commented on GitHub (Jun 24, 2020):

@lafriks so it seems these ominous 13 repos all have is_archived=false while the others have is_archived=NULL and therefore get filtered out. I assume this goes for the statistics too?

EDIT: Same goes for the is_empty column

A bit of background info on my installation:
I'm running Gitea on a Raspberry Pi 4B running Raspbian 10 on Docker (self built image on the latest 1.12.1 tag). The repos that are missing info are all older from before the Pi 4 was released (and I was on a Pi 3B). I tried the backup/restore function to migrate to the new Pi, and I had some problems with some indexes if I recall correctly, so maybe this could be a consequence of this?

@SuNNjek commented on GitHub (Jun 24, 2020): @lafriks so it seems these ominous 13 repos all have `is_archived=false` while the others have `is_archived=NULL` and therefore get filtered out. I assume this goes for the statistics too? EDIT: Same goes for the `is_empty` column A bit of background info on my installation: I'm running Gitea on a Raspberry Pi 4B running Raspbian 10 on Docker (self built image on the latest 1.12.1 tag). The repos that are missing info are all older from before the Pi 4 was released (and I was on a Pi 3B). I tried the backup/restore function to migrate to the new Pi, and I had some problems with some indexes if I recall correctly, so maybe this could be a consequence of this?
Author
Owner

@SuNNjek commented on GitHub (Jun 24, 2020):

Ok, after executing UPDATE repository SET is_empty=FALSE, is_archived=FALSE; everything seems to be fine, so I'm gonna close this issue

@SuNNjek commented on GitHub (Jun 24, 2020): Ok, after executing `UPDATE repository SET is_empty=FALSE, is_archived=FALSE;` everything seems to be fine, so I'm gonna close this issue
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5612