github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Repository Release 500 Error #13693

New Issue
Closed
opened 2025-11-02 10:50:34 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 10:50:34 -06:00
Owner
Copy Link

Originally created by @House-Men on GitHub (Nov 10, 2024).

Description

When core.edito is not configured in .gitconfig, the release version reports the following error

CreateRelease, exit status 1 - error: Terminal is dumb, but EDITOR unset
Please supply the message using either -m or -F option.
 - error: Terminal is dumb, but EDITOR unset
Please supply the message using either -m or -F option.

.gitconfig configures core.edito=nano, and the released version reports the following error

CreateRelease, exit status 1 - Too many errors from stdin
error: There was a problem with the editor 'nano'.
Please supply the message using either -m or -F option.
 - Too many errors from stdin
error: There was a problem with the editor 'nano'.
Please supply the message using either -m or -F option.

.gitconfig configure core.edito=vim, release version POST URL "https://[host]/[organize]/[repository]/releases/new" infinite wait

root@test:~# ps aux | grep vim
git       199487  0.1  0.0  11088  8804 ?        S    13:53   0:00 /usr/bin/vim /var/lib/gitea/data/gitea-repositories/[organize]/[repository].git/TAG_EDITMSG
root@test:~# kill 199487

After kill vim pid

CreateRelease, exit status 1 - Vim: Warning: Output is not to a terminal
Vim: Warning: Input is not from a terminal

Press ENTER or type command to continueerror: vim died of signal 9
error: There was a problem with the editor 'vim'.
Please supply the message using either -m or -F option.
 - Vim: Warning: Output is not to a terminal
Vim: Warning: Input is not from a terminal

Press ENTER or type command to continueerror: vim died of signal 9
error: There was a problem with the editor 'vim'.
Please supply the message using either -m or -F option.

Gitea Version

Gitea version 1.22.3 built with GNU Make 4.3, go1.22.8 : bindata, sqlite, sqlite_unlock_notify

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

git version 2.30.2

Operating System

Debian 11(Linux 5.10.0-26-amd64 #1 SMP Debian 5.10.197-1 x86_64 GNU/Linux)

How are you running Gitea?

Binary Download：https://dl.gitea.com/gitea/1.22.3/gitea-1.22.3-linux-amd64
Using systemd Running：https://github.com/go-gitea/gitea/blob/release/v1.22/contrib/systemd/gitea.service

Database

PostgreSQL

Originally created by @House-Men on GitHub (Nov 10, 2024). ### Description When core.edito is not configured in .gitconfig, the release version reports the following error ``` CreateRelease, exit status 1 - error: Terminal is dumb, but EDITOR unset Please supply the message using either -m or -F option. - error: Terminal is dumb, but EDITOR unset Please supply the message using either -m or -F option. ``` .gitconfig configures core.edito=nano, and the released version reports the following error ``` CreateRelease, exit status 1 - Too many errors from stdin error: There was a problem with the editor 'nano'. Please supply the message using either -m or -F option. - Too many errors from stdin error: There was a problem with the editor 'nano'. Please supply the message using either -m or -F option. ``` .gitconfig configure core.edito=vim, release version POST URL "https://[host]/[organize]/[repository]/releases/new" infinite wait ``` root@test:~# ps aux | grep vim git 199487 0.1 0.0 11088 8804 ? S 13:53 0:00 /usr/bin/vim /var/lib/gitea/data/gitea-repositories/[organize]/[repository].git/TAG_EDITMSG root@test:~# kill 199487 ``` After kill vim pid ``` CreateRelease, exit status 1 - Vim: Warning: Output is not to a terminal Vim: Warning: Input is not from a terminal Press ENTER or type command to continueerror: vim died of signal 9 error: There was a problem with the editor 'vim'. Please supply the message using either -m or -F option. - Vim: Warning: Output is not to a terminal Vim: Warning: Input is not from a terminal Press ENTER or type command to continueerror: vim died of signal 9 error: There was a problem with the editor 'vim'. Please supply the message using either -m or -F option. ``` ### Gitea Version Gitea version 1.22.3 built with GNU Make 4.3, go1.22.8 : bindata, sqlite, sqlite_unlock_notify ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version git version 2.30.2 ### Operating System Debian 11(Linux 5.10.0-26-amd64 #1 SMP Debian 5.10.197-1 x86_64 GNU/Linux) ### How are you running Gitea? Binary Download：https://dl.gitea.com/gitea/1.22.3/gitea-1.22.3-linux-amd64 Using systemd Running：https://github.com/go-gitea/gitea/blob/release/v1.22/contrib/systemd/gitea.service ### Database PostgreSQL
GiteaMirror added the issue/not-a-bug label 2025-11-02 10:50:34 -06:00
GiteaMirror commented 2025-11-02 10:50:36 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Nov 10, 2024):

It is not related to "EDITOR" or core.editor (do not set them)

The problem seems to be that the git command used to create the tag is not valid.

@wxiaoguang commented on GitHub (Nov 10, 2024): It is not related to "EDITOR" or `core.editor` (do not set them) The problem seems to be that the git command used to create the tag is not valid.
GiteaMirror commented 2025-11-02 10:50:36 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Nov 10, 2024):

What's the "git" command when "create release"?

You could figure it out by either way:

  1. Still set the "core.editor", when the editor process hangs, check its parent process to see the git command
  2. Enable debug logs to see the git commands

I guess there is something wrong with you git command (mixed version? wrapped shell?)

@wxiaoguang commented on GitHub (Nov 10, 2024): What's the "git" command when "create release"? You could figure it out by either way: 1. Still set the "core.editor", when the editor process hangs, check its parent process to see the git command 2. Enable debug logs to see the git commands I guess there is something wrong with you git command (mixed version? wrapped shell?)
GiteaMirror commented 2025-11-02 10:50:36 -06:00
Author
Owner
Copy Link

@House-Men commented on GitHub (Nov 10, 2024):

@wxiaoguang After commenting tag.gpgsign = true, everything works fine.

@House-Men commented on GitHub (Nov 10, 2024): @wxiaoguang After commenting tag.gpgsign = true, everything works fine.
GiteaMirror commented 2025-11-02 10:50:36 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Nov 10, 2024):

Glad to hear it it works.

Most Gitea's git config options should only be managed by Gitea itself

@wxiaoguang commented on GitHub (Nov 10, 2024): Glad to hear it it works. Most Gitea's git config options should only be managed by Gitea itself
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 issue/not-a-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#13693
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?