-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Error on PR creating with previously forked repository #13910
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
Comments
Does /srv/repositories/lvtemplate/1900.git still exist? |
|
v1.13.0 face the same problem for a normal repo. Other repos are able to create merge requests normally. Logs like
Actually the path XX exists. No other special logs were found. |
May be related to #13597 Probolem repo has LFS. |
Fixed the wrong version. The problem was firsted visible in 1.12.5 and now in the most recent release. @zeripath The path does exist and is writable. It is a single repository which works in every aspect except PRs. It once had forks. @NepPure The repository is using LFS. I now notice the other issue, which seems to be the problem. I'll investigate in a second. |
I removed a bunch of hooks which did only check for LFS. Now the PR (created again) does not show this particular error message anymore. Thanks, especially @NepPure. Sorry for the diplicate. |
[x]
):Description
There is a repository which once had some forks around. This usage scenario did not quite match our requirements, so I manually removed the forks once. The web interface shows no forks, so does the database in the table
repository
with columnsis_fork
,fork_id
andnum_forks
.When creating a PR inside this particular repository the user gets a 500. The PR is created nethertheless in the background, but shows message attached as screenshot.
The log information do not help either, because the remote seems right. The path exists and is the correct one.
How to fix this behavior? There must be some fork information which I did not remove yet.
Thanks in advance.
Screenshots
Edit: Fixed gitea version.
The text was updated successfully, but these errors were encountered: