-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Repo with existing directory misleadingly fails with 500 #7374
Comments
I have same error with empty MSSQL database and initial Gitea config. I tried add LOCAL_ROOT_URL = http://127.0.0.1:3000 to config, change permissions, database, new 1.9.0 version but still same error. |
@dimmuboy Did you also have an exist repository on the same path as your created? |
No I created completely new repo dir |
So you should have a different issue as this one. |
Yes but IMHO it will be problem with database because main dir sctructure "repository/username/" was created. In original post @commel wrote about switch to MSSQL like me. Edit: In my case error 500 shows only when creating new repo and check Initialize Repository otherwise repo is created. |
It has been fixed #24164 by the way |
Hi,
[x]
):Description
we switched servers (and datbase backends from sqlite3 to mssql) but keeped the repository directories. I needed to recreate the former existing repository entries in gitea. After clicking "create repository" it resulted in a 500 error page. After refresh the empty repository was available.
In the logs I found this:
2019/07/08 10:00:23 [...routers/repo/repo.go:146 handleCreateError()] [E] CreatePost: initRepository: initRepository: path already exists: d:\repos\secretuser\secretrepo.git
The error is misleading (and probably not wanted in that way) here as it works in the background. A notification message would be better to inform that the directory is already existing.
The text was updated successfully, but these errors were encountered: