-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
"slice bounds out of range error" in signature_nogogit.go due to an empty author name #21900
Labels
Comments
ghost
added
the
type/bug
label
Nov 22, 2022
zeripath
added a commit
to zeripath/gitea
that referenced
this issue
Nov 22, 2022
Although git does expect that author names should be of the form: `NAME <EMAIL>` some users have been able to create commits with: `<EMAIL>` Fix go-gitea#21900 Signed-off-by: Andrew Thornton <[email protected]>
lunny
added a commit
that referenced
this issue
Nov 23, 2022
Although git does expect that author names should be of the form: `NAME <EMAIL>` some users have been able to create commits with: `<EMAIL>` Fix #21900 Signed-off-by: Andrew Thornton <[email protected]> Co-authored-by: delvh <[email protected]> Co-authored-by: Lauris BH <[email protected]> Co-authored-by: Lunny Xiao <[email protected]>
zeripath
added a commit
to zeripath/gitea
that referenced
this issue
Dec 4, 2022
Backport go-gitea#21902 Although git does expect that author names should be of the form: `NAME <EMAIL>` some users have been able to create commits with: `<EMAIL>` Fix go-gitea#21900 Signed-off-by: Andrew Thornton <[email protected]>
zeripath
added a commit
to zeripath/gitea
that referenced
this issue
Dec 4, 2022
Backport go-gitea#21902 Although git does expect that author names should be of the form: `NAME <EMAIL>` some users have been able to create commits with: `<EMAIL>` Fix go-gitea#21900 Signed-off-by: Andrew Thornton <[email protected]>
lunny
pushed a commit
that referenced
this issue
Dec 6, 2022
Backport #21902 Although git does expect that author names should be of the form: `NAME <EMAIL>` some users have been able to create commits with: `<EMAIL>` Fix #21900 Signed-off-by: Andrew Thornton <[email protected]> Co-authored-by: Lauris BH <[email protected]>
lunny
added a commit
that referenced
this issue
Dec 6, 2022
Backport #21902 Although git does expect that author names should be of the form: `NAME <EMAIL>` some users have been able to create commits with: `<EMAIL>` Fix #21900 Signed-off-by: Andrew Thornton <[email protected]> Co-authored-by: Lauris BH <[email protected]> Co-authored-by: Lunny Xiao <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Not sure how it happened, I have commits without an author name in a repository.
Pushing this repository will lead to a 500 error when visiting the repository page on gitea, due to the following exception :
because emailStart == 0 in modules/git/signature_nogogit.go:54
Gitea Version
e77b764
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
2.35.1
Operating System
debian testing
How are you running Gitea?
Built from source.
Database
SQLite
The text was updated successfully, but these errors were encountered: