Attribute checker for commit xxxx exits with error: failed to run attr-check

[TinyZzh]

Description

When I use Git to commit code to Gitea Repo, error logs related to attr-check are generated. However, I didn't observe any obvious exceptions in practice - the code was successfully committed. I'm unsure about the specific purpose of this attr-check. Could you please clarify:

• What functionality does attr-check serve?
• What impact might it have on operations?

Gitea Version

1.23.6

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

Git Version

gogit

Operating System

Windows 10

How are you running Gitea?

Double-click gitea.exe.

Database

SQLite

[wxiaoguang]

It is a windows only problem, need some people who is using Windows to help to debug.

Duplicate:

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

[eeyrjmr]

I am seeing this as well, only recently and it might coincide with starting to use LFS (gitea keeps wanting to delete LFS data :( ).

Presently I can't associate these commit log issues with a real check to see if there is something to be mindful of.

[eeyrjmr]

TRACE log has shown my five occurances of this is on one specific repository AND it is one where I am also seeing LFS issues where gitea thinks the LFS metadata is ophaned but it is valid lfs data.. funny enough the commit hash doesn't actually exist so something has gone odd...

[eeyrjmr]

@TinyZzh are you using LFS as I have seen an issue with LFS (and windows) and it might be related as right now gitea things LFS data is orphaned and if I run doctor --fix it will delete valid LFS data

--edit--
Added a test pdf, associated with LFS... it was added fine, the LFS repo settings have it ok BUT gitea doctor would still want to delete the LFS as it is saying there is orphaned LFS files. I think this is associated with LFS and windows AND a new [E] Attribute checker appeared on this test repo right after a pdf file was pushed