"Error while getting .editorconfig file" System Notices #13900

New Issue

GiteaMirror · 2025-11-02T10:56:37-06:00

GiteaMirror commented

2025-11-02 10:56:37 -06:00

Originally created by @bartvdbraak on GitHub (Dec 31, 2024).

Description

There seems to be a constant stream of the following system notice:

561698 	Repository 	Error while getting .editorconfig file: io: read/write on closed pipe 	2024-12-31 	
	561697 	Repository 	Error while getting .editorconfig file: io: read/write on closed pipe 	2024-12-31 	
	561696 	Repository 	Error while getting .editorconfig file: io: read/write on closed pipe 	2024-12-31 	
	561695 	Repository 	Error while getting .editorconfig file: io: read/write on closed pipe 	2024-12-31 	
	561694 	Repository 	Error while getting .editorconfig file: io: read/write on closed pipe 	2024-12-31 	
	561693 	Repository 	Error while getting .editorconfig file: io: read/write on closed pipe 	2024-12-31 	
	561692 	Repository 	Error while getting .editorconfig file: io: read/write on closed pipe 	2024-12-31 	
	561691 	Repository 	Error while getting .editorconfig file: io: read/write on closed pipe 	2024-12-31 	
	561690 	Repository 	Error while getting .editorconfig file: io: read/write on closed pipe 	2024-12-31 	
	561689 	Repository 	Error while getting .editorconfig file: io: read/write on closed pipe 	2024-12-31 	
	561688 	Repository 	Error while getting .editorconfig file: io: read/write on closed pipe 	2024-12-31 	
	561687 	Repository 	Error while getting .editorconfig file: io: read/write on closed pipe

I tried looking for an issue using the logs but was only able to find some instances of

gitea.log:752264:2024/12/31 11:46:35 ...eb/routing/logger.go:68:func1() [W] router: slow      HEAD /Christophe-Marois/blender-manual/src/commit/372323b2b7858c13b06499ecaf56df1259dab423/.editorconfig for 172.18.0.3:60166, elapsed 3228.3ms @ context/repo.go:885(web.registerRoutes.func51.12.RepoRefByType.3)

Gitea Version

1.22.6 built with GNU Make 4.4.1, go1.22.10 : bindata, timetzdata, sqlite, sqlite_unlock_notify

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Git Version

2.45.2

Operating System

Ubuntu 24.04

How are you running Gitea?

We maintain a fork ourselves with some custom patches on top.

For this specific version the source of truth is

https://github.com/blender/gitea/tree/apply-patches-v1.22.6

It is then build into an OCI image using the following build pipeline:

https://github.com/blender/gitea/actions/runs/12392734630/job/34592567463

Database

PostgreSQL

Originally created by @bartvdbraak on GitHub (Dec 31, 2024). ### Description There seems to be a constant stream of the following system notice: ``` 561698 Repository Error while getting .editorconfig file: io: read/write on closed pipe 2024-12-31 561697 Repository Error while getting .editorconfig file: io: read/write on closed pipe 2024-12-31 561696 Repository Error while getting .editorconfig file: io: read/write on closed pipe 2024-12-31 561695 Repository Error while getting .editorconfig file: io: read/write on closed pipe 2024-12-31 561694 Repository Error while getting .editorconfig file: io: read/write on closed pipe 2024-12-31 561693 Repository Error while getting .editorconfig file: io: read/write on closed pipe 2024-12-31 561692 Repository Error while getting .editorconfig file: io: read/write on closed pipe 2024-12-31 561691 Repository Error while getting .editorconfig file: io: read/write on closed pipe 2024-12-31 561690 Repository Error while getting .editorconfig file: io: read/write on closed pipe 2024-12-31 561689 Repository Error while getting .editorconfig file: io: read/write on closed pipe 2024-12-31 561688 Repository Error while getting .editorconfig file: io: read/write on closed pipe 2024-12-31 561687 Repository Error while getting .editorconfig file: io: read/write on closed pipe ``` I tried looking for an issue using the logs but was only able to find some instances of ``` gitea.log:752264:2024/12/31 11:46:35 ...eb/routing/logger.go:68:func1() [W] router: slow HEAD /Christophe-Marois/blender-manual/src/commit/372323b2b7858c13b06499ecaf56df1259dab423/.editorconfig for 172.18.0.3:60166, elapsed 3228.3ms @ context/repo.go:885(web.registerRoutes.func51.12.RepoRefByType.3) ``` ### Gitea Version 1.22.6 built with GNU Make 4.4.1, go1.22.10 : bindata, timetzdata, sqlite, sqlite_unlock_notify ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots ![image](https://github.com/user-attachments/assets/575e1ef6-9ece-4098-944a-c2aa143cb99a) ### Git Version 2.45.2 ### Operating System Ubuntu 24.04 ### How are you running Gitea? We maintain a fork ourselves with some custom patches on top. For this specific version the source of truth is - https://github.com/blender/gitea/tree/apply-patches-v1.22.6 It is then build into an OCI image using the following build pipeline: - https://github.com/blender/gitea/actions/runs/12392734630/job/34592567463 ### Database PostgreSQL

GiteaMirror added the type/bug label 2025-11-02 10:56:37 -06:00

GiteaMirror closed this issue

2025-11-02 10:56:37 -06:00

GiteaMirror commented

2025-11-02 10:56:38 -06:00

@wxiaoguang commented on GitHub (Dec 31, 2024):

It is a trivial and useless report, you could just safely ignore it.

(Actually the "notice" page/table is a legacy design and useless in modern days ........)

@wxiaoguang commented on GitHub (Dec 31, 2024): It is a trivial and useless report, you could just safely ignore it. (Actually the "notice" page/table is a legacy design and useless in modern days ........)

GiteaMirror commented

2025-11-02 10:56:38 -06:00

@bartvdbraak commented on GitHub (Dec 31, 2024):

Thanks for letting us know :)

@bartvdbraak commented on GitHub (Dec 31, 2024): Thanks for letting us know :)

GiteaMirror commented

2025-11-02 10:56:38 -06:00

@lunny commented on GitHub (Jan 3, 2025):

Maybe we can remove this notice as it's too noise.

@lunny commented on GitHub (Jan 3, 2025): Maybe we can remove this notice as it's too noise.

GiteaMirror commented

2025-11-02 10:56:39 -06:00

@bartvdbraak commented on GitHub (Feb 7, 2025):

We are still receiving a lot of these notices, can I be assured it's not something major going wrong internally or misconfiguration on our end?

@bartvdbraak commented on GitHub (Feb 7, 2025): We are still receiving a lot of these notices, can I be assured it's not something major going wrong internally or misconfiguration on our end?

GiteaMirror commented

2025-11-02 10:56:39 -06:00

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

It is useless, caused by the disconnected connection from user side.

I have removed that message by Refactor context repository (#33202) in 1.24

You can also apply that change: just apply the diff https://github.com/go-gitea/gitea/pull/33202/files#diff-44c4f500c02f5f3e026bee88df0f21f5e79bf87d13428b8f1202e8501f73413aR21-L31

So I think this issue could be closed.

@wxiaoguang commented on GitHub (Feb 7, 2025): It is useless, caused by the disconnected connection from user side. I have removed that message by Refactor context repository (#33202) in 1.24 You can also apply that change: just apply the diff https://github.com/go-gitea/gitea/pull/33202/files#diff-44c4f500c02f5f3e026bee88df0f21f5e79bf87d13428b8f1202e8501f73413aR21-L31 So I think this issue could be closed.

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