gitea: sub-branches throw 500
- Gitea version (or commit ref): 1.9.3 built with go1.13.1
- Git version: 2.23.0
- Operating system: FreeBSD (Freenas)
- Database (use
[x]):- PostgreSQL
- MySQL
- MSSQL
- SQLite
- Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
- Log gist:
Description
I’m able to create a feature/nameoffeature branch but when I try to load it on gitea it throws 500 errors …
Screenshots
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 42 (22 by maintainers)
Commits related to this issue
- vendor: go-git: import IsDir() check for readReferenceFile() This fix has been accepted and merged upstream; the gist of the problem is that readReferenceFile() must check that what it's been request... — committed to kevans91/gitea by kevans91 4 years ago
- vendor: go-git: import IsDir() check for readReferenceFile() This fix has been accepted and merged upstream; the gist of the problem is that readReferenceFile() must check that what it's been request... — committed to kevans91/gitea by kevans91 4 years ago
- www/gitea: Fix viewing of branches with a slash in the name An issue[0] was filed upstream in January that branches with a slash in their name (e.g. stable/11) result in a 500 error when attempting t... — committed to freebsd/freebsd-ports by deleted user 4 years ago
- www/gitea: Fix viewing of branches with a slash in the name An issue[0] was filed upstream in January that branches with a slash in their name (e.g. stable/11) result in a 500 error when attempting t... — committed to freebsd/freebsd-ports by kevans91 4 years ago
- MFH: r534921 www/gitea: Fix viewing of branches with a slash in the name An issue[0] was filed upstream in January that branches with a slash in their name (e.g. stable/11) result in a 500 error whe... — committed to freebsd/freebsd-ports by kevans91 4 years ago
- www/gitea: Fix viewing of branches with a slash in the name An issue[0] was filed upstream in January that branches with a slash in their name (e.g. stable/11) result in a 500 error when attempting t... — committed to Jehops/freebsd-ports-legacy by kevans91 4 years ago
Hi,
I sent a PR and was told it can’t be merged until a release of go-git is cut that includes it. =( #11208
It does fix the problem on FreeBSD and I’ve got a patch for our ports system that we can carry locally with no real problem until a new release is made.
Hello,
I don’t know If my problem is related to this issue, but I got a similar behavior when I want to display the branch page of my repos.
I don’t know why but on my branch settings (on the protected branch section) there are an unknown branch named:
._master. When I want select this unknown branch, I got an error 500.I success to resolve my problem with step below:
On my server, I created the
._masterreference file:Try to select the
._masterbranch on the protected section (without validate the forms).Then remove the
._masterfile previously created:At this moment, the ._master branch seem be deleted from gitea database.
I hope It’s can help (If my problem is related to this issue ^^) …
Default is Master,
@guillep2k Yes,