-
-
Notifications
You must be signed in to change notification settings - Fork 6k
Closed
Description
- Gitea version (or commit ref): 1.10rc1 ref: db0d4ff
- Git version:
- Operating system: win7
- Database (use
[x]
):- PostgreSQLMySQLMSSQLSQLiteTo pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.
- Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)NoNot relevantTo pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.
- Log gist:
Description
step1. New/Create Repository
step2. http://xxxxx:3000/xxxx/xxxx/issues/new
or /xxxx/xxxx/settings/hooks/git
response 500 error
...
Screenshots
Metadata
Metadata
Assignees
Labels
Type
Projects
Relationships
Development
Select code repository
Activity
zeripath commentedon Oct 16, 2019
It would be helpful to get the log in cases like this, however it appears simple to replicate.
When trying the /issues/new endpoint I get:
And on /settings/hook/git:
zeripath commentedon Oct 16, 2019
So the problem is that either
ctx.Repo.GitRepo
is nil orctx.Repo
is nil.zeripath commentedon Oct 16, 2019
gitea/modules/context/repo.go
Lines 417 to 428 in 1d9a1a0
Implies that in an empty repo -
ctx.Repo.GitRepo
will be nilzeripath commentedon Oct 16, 2019
Simplest Solution:
Ensure that GitRepo is set on Empty repositories
Ensure that GitRepo is set on Empty repositories (#8539)
Ensure that GitRepo is set on Empty repositories (go-gitea#8539)
Ensure that GitRepo is set on Empty repositories (#8539) (#8541)