-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
tcp: write: broken pipe: [E] Render failed: failed to render template + [E] plainTextInternal (status=500) #30792
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
If you didn't experience any problem during usage, it's safe to ignore them . It is a false alarm. Some error messages are reported too aggressively. |
If there are some problems when browsing the pages ..... it looks more like an OS/envorinment related problem. Usually |
ok, thanks for the info. I didn't have any problems in usage and only saw this message in the logs. |
-> Ignore uesless error message "broken pipe" #30801 Let's make Gitea never show such useless logs 😁 |
…#30842) Backport go-gitea#30801 by wxiaoguang Fix go-gitea#30792 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> (cherry picked from commit ab2ef1a)
Description
In the log it show the following:
2024/04/30 23:21:27 .../context_response.go:87:HTML() [E] Render failed: failed to render template: home, error: write tcp 127.0.0.1:3000->127.0.0.1:50284: write: broken pipe
2024/04/30 23:21:27 .../context_response.go:89:HTML() [E] plainTextInternal (status=500): write bytes failed: write tcp 127.0.0.1:3000->127.0.0.1:50284: write: broken pipe
Installed via docker compose on Synology NAS.
Gitea Version
gitea-1.22.0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Git Version
No response
Operating System
Synology DSM
How are you running Gitea?
Docker Container
Database
None
Additional remarks
I already did this setting: Administration -> Konfiguration -> Einstellungen -> Gravatar deaktivieren
The text was updated successfully, but these errors were encountered: