github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-21 14:06:26 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Windows only: Unable to open checker for <commit id>. Error: failed to run attr-check. Error: exit status 1 #14120

New Issue
Closed
opened 2025-11-02 11:03:30 -06:00 by GiteaMirror · 13 comments
GiteaMirror commented 2025-11-02 11:03:30 -06:00
Owner
Copy Link

Originally created by @yp05327 on GitHub (Feb 10, 2025).

Description

Image

binary file: gitea-1.23.3-windows-4.0-amd64.exe
git version: git version 2.47.1.windows.1

Gitea Version

1.23.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

windows binary file

Database

None

Originally created by @yp05327 on GitHub (Feb 10, 2025). ### Description ![Image](https://github.com/user-attachments/assets/862cdc1c-d8bf-4536-a731-33c3433990f8) binary file: gitea-1.23.3-windows-4.0-amd64.exe git version: git version 2.47.1.windows.1 ### Gitea Version 1.23.3 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? windows binary file ### Database None
GiteaMirror added the type/bug label 2025-11-02 11:03:30 -06:00
GiteaMirror commented 2025-11-02 11:03:31 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Feb 12, 2025):

Are you able to reproduce in 1.24? I have refactored many legacy "repo" middlewares.

Maybe it's not related to 1.23/1.24 and it only happens randomly, but we need to know how to reproduce it.

@wxiaoguang commented on GitHub (Feb 12, 2025): Are you able to reproduce in 1.24? I have refactored many legacy "repo" middlewares. ---- Maybe it's not related to 1.23/1.24 and it only happens randomly, but we need to know how to reproduce it.
GiteaMirror commented 2025-11-02 11:03:31 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Feb 26, 2025):

I only met this error once for test other things in a clean newly installed instance, and didn't try it in 1.24.
But I saw others who is running 1.23.4-windows also got this error today.

It is hard to say how to completely reproduce it.

@yp05327 commented on GitHub (Feb 26, 2025): I only met this error once for test other things in a clean newly installed instance, and didn't try it in 1.24. But I saw others who is running 1.23.4-windows also got this error today. It is hard to say how to completely reproduce it.
GiteaMirror commented 2025-11-02 11:03:31 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Feb 26, 2025):

Image
This is the log, it seems that every time reviewing the PR, this error will occur.

Then I ask let him to try it again, and he got the error again:

Image

@yp05327 commented on GitHub (Feb 26, 2025): ![Image](https://github.com/user-attachments/assets/03dd97f5-53c4-42a3-b624-1b3182058f73) This is the log, it seems that every time reviewing the PR, this error will occur. Then I ask let him to try it again, and he got the error again: ![Image](https://github.com/user-attachments/assets/ad65d7e8-949d-41c0-95db-fe543a122add)
GiteaMirror commented 2025-11-02 11:03:31 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Feb 26, 2025):

I tried again in 1.23.4, I found this:
Image

@yp05327 commented on GitHub (Feb 26, 2025): I tried again in 1.23.4, I found this: ![Image](https://github.com/user-attachments/assets/71fee3b9-3f99-4fbb-a2a4-63594154ce3f)
GiteaMirror commented 2025-11-02 11:03:32 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Mar 16, 2025):

related to #31600

@lunny commented on GitHub (Mar 16, 2025): ~related to #31600~
GiteaMirror commented 2025-11-02 11:03:32 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Mar 16, 2025):

I do not think it's related, this error is "exit status 1", it could be caused by incorrect git command or incorrect git repo.

@wxiaoguang commented on GitHub (Mar 16, 2025): I do not think it's related, this error is "exit status 1", it could be caused by incorrect git command or incorrect git repo.
GiteaMirror commented 2025-11-02 11:03:32 -06:00
Author
Owner
Copy Link

@chris-08154711 commented on GitHub (Mar 19, 2025):

This error occurs once in every GET https://[gitea]/[org]/[repo]/commit/[hash] request cycle.
Found in: 1.21.11, 1.23.5, 100% reproducible

@chris-08154711 commented on GitHub (Mar 19, 2025): This error occurs once in every GET https://[gitea]/[org]/[repo]/commit/[hash] request cycle. Found in: 1.21.11, 1.23.5, 100% reproducible
GiteaMirror commented 2025-11-02 11:03:32 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Mar 19, 2025):

This error occurs once in every GET https://[gitea]/[org]/[repo]/commit/[hash] request cycle. Found in: 1.21.11, 1.23.5, 100% reproducible

How do you run Gitea? Windows or not? Docker or not?

@wxiaoguang commented on GitHub (Mar 19, 2025): > This error occurs once in every GET https://[gitea]/[org]/[repo]/commit/[hash] request cycle. Found in: 1.21.11, 1.23.5, 100% reproducible How do you run Gitea? Windows or not? Docker or not?
GiteaMirror commented 2025-11-02 11:03:33 -06:00
Author
Owner
Copy Link

@chris-08154711 commented on GitHub (Mar 19, 2025):

Windows Server 2016, no Docker, MariaDB

Log attached: gitea.log

@chris-08154711 commented on GitHub (Mar 19, 2025): Windows Server 2016, no Docker, MariaDB Log attached: [gitea.log](https://github.com/user-attachments/files/19340607/gitea.log)
GiteaMirror commented 2025-11-02 11:03:33 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Mar 19, 2025):

Windows Server 2016, no Docker, MariaDB

So I think the attr-check error is only related to Windows servers. Unfortunately, it seems that there is few contributors using Windows to run Gitea server, so the Windows release is not well maintained.

@wxiaoguang commented on GitHub (Mar 19, 2025): > Windows Server 2016, no Docker, MariaDB So I think the `attr-check` error is only related to Windows servers. Unfortunately, it seems that there is few contributors using Windows to run Gitea server, so the Windows release is not well maintained.
GiteaMirror commented 2025-11-02 11:03:33 -06:00
Author
Owner
Copy Link

@eeyrjmr commented on GitHub (Mar 26, 2025):

@yp05327 are you using LFS?
I ask because this week a colleague created a new repo and pushed using LFS and now I have this in my logs and when I increase the logging fidelity it is when the LFS data is checked.
When I then run gitea doctor check --all --fix it would

  1. flag orphaned LFS data
  2. delete the LFS data :( (luckily only 5 LFS files and a backup was created just after the creation)

I am not 100% sure but almost ... ALMOST this is associated with LFS and some metadata isn't being stored and likely windows only :(

@eeyrjmr commented on GitHub (Mar 26, 2025): @yp05327 are you using LFS? I ask because this week a colleague created a new repo and pushed using LFS and now I have this in my logs and when I increase the logging fidelity it is when the LFS data is checked. When I then run **gitea doctor check --all --fix** it would 1) flag orphaned LFS data 2) delete the LFS data :( (luckily only 5 LFS files and a backup was created just after the creation) I am not 100% sure but almost ... ALMOST this is associated with LFS and some metadata isn't being stored and likely windows only :(
GiteaMirror commented 2025-11-02 11:03:33 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Mar 27, 2025):

@eeyrjmr
No. My log is just from a newly installed instance which is for the test.
Only created a new repo, a new branch for a PR, and a PR review.

@yp05327 commented on GitHub (Mar 27, 2025): @eeyrjmr No. My log is just from a newly installed instance which is for the test. Only created a new repo, a new branch for a PR, and a PR review.
GiteaMirror commented 2025-11-02 11:03:34 -06:00
Author
Owner
Copy Link

@eeyrjmr commented on GitHub (Mar 27, 2025):

@eeyrjmr No. My log is just from a newly installed instance which is for the test. Only created a new repo, a new branch for a PR, and a PR review.

ok :(
I am facing two issues then but the common one about attr-check appears to resolve and it looks like a good fix. It might have been co-incidence when I ran into this with regards to orphaned LFS.
It still could be the same thing because if attr-check is used in orphan check then I will also be hitting this.

@eeyrjmr commented on GitHub (Mar 27, 2025): > [@eeyrjmr](https://github.com/eeyrjmr) No. My log is just from a newly installed instance which is for the test. Only created a new repo, a new branch for a PR, and a PR review. ok :( I am facing two issues then but the common one about attr-check appears to resolve and it looks like a good fix. It might have been co-incidence when I ran into this with regards to orphaned LFS. It still could be the same thing because if attr-check is used in orphan check then I will also be hitting this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14120
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?