Display error reason, in case GIT repository being corrupted. #6018

New Issue

GiteaMirror · 2025-11-02T06:42:54-06:00

GiteaMirror commented

2025-11-02 06:42:54 -06:00

Originally created by @memdealer on GitHub (Sep 17, 2020).

Gitea version (or commit ref): image: gitea/gitea:1.12.3
Git version: 2.28.0
Operating system: RosberyPi64
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

Hi People,

I wonder if you can add a description on what's going on when a certain repository cannot be reached due to the fact that data is corrupted. This day I found out that one of my local repositories returning 500 whenever I try to see it in the web. The issue was unclear until I tried to push/pull from that repo.

As revealed some objects were corrupted/empty inside of the container, but they're seems to be NOT empty and fine in the local copy. Still not sure why, perhaps due to the power outage/improperly powering off RosberyPi.

PS: I tried to git fisck --full/removing corrupted/empty objects - still no way to reach repository.

Screenshots

Originally created by @memdealer on GitHub (Sep 17, 2020). - Gitea version (or commit ref): image: gitea/gitea:1.12.3 - Git version: 2.28.0 - Operating system: RosberyPi64 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [X] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [X] No - [ ] Not relevant - Log gist: ## Description Hi People, I wonder if you can add a description on what's going on when a certain repository cannot be reached due to the fact that data is corrupted. This day I found out that one of my local repositories returning 500 whenever I try to see it in the web. The issue was unclear until I tried to push/pull from that repo. As revealed some objects were corrupted/empty inside of the container, but they're seems to be NOT empty and fine in the local copy. Still not sure why, perhaps due to the power outage/improperly powering off RosberyPi. PS: I tried to git fisck --full/removing corrupted/empty objects - still no way to reach repository. ## Screenshots ![image](https://user-images.githubusercontent.com/21087423/93468327-757da300-f8f7-11ea-8632-78ebff66736f.png) ![image](https://user-images.githubusercontent.com/21087423/93468464-af4ea980-f8f7-11ea-9031-911f262fc12b.png) ![image](https://user-images.githubusercontent.com/21087423/93468515-c5f50080-f8f7-11ea-8e75-2523b3a920c7.png) ![image](https://user-images.githubusercontent.com/21087423/93468892-5cc1bd00-f8f8-11ea-8ff1-71b82d783cbd.png)

GiteaMirror added the issue/not-a-bug label 2025-11-02 06:42:55 -06:00

GiteaMirror closed this issue

2025-11-02 06:42:55 -06:00

GiteaMirror commented

2025-11-02 06:42:56 -06:00

@lunny commented on GitHub (Sep 17, 2020):

If you run gitea in development mode, it will be displayed.

@lunny commented on GitHub (Sep 17, 2020): If you run gitea in development mode, it will be displayed.

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