Template Rendering Error When Viewing Pull-Requests

[ghost]

Gitea Version

1.16.1

Git Version

No response

Operating System

Linux Debian 11

How are you running Gitea?

We're using the Gitea binary gitea-1.16.1-linux-amd64 from the "Releases" page.
An Nginx reverse proxy communicates with Gitea via http+unix (HTTP over Unix sockets).

Database

No response

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

https://gist.github.com/rtpt-jonaslieb/23ad0a6d873ade04aac7e2ad55f0dfd2

Description

Gitea displays a 500 server error upon viewing an unmerged pull request. The corresponding log is attached to this issue.
It does not happen with pull requests that have been merged or closed.

The underlying issue appears to be that PullRequestWorkInProgressPrefixes is undefined in sidebar.tmpl.
The corresponding render-call is here:

gitea/routers/web/repo/issue.go

Line 1657 in bb77e6c

ctx.HTML(http.StatusOK, tplIssueView)

in function ViewIssue:

gitea/routers/web/repo/issue.go

Line 1083 in bb77e6c

func ViewIssue(ctx *context.Context) {

The error occurs even if WORK_IN_PROGRESS_PREFIXES = WIP:,[WIP] is explicitly included in the app.ini section repository.pull-request.

I'm not quite sure why the issue cannot be reproduced on the Gitea demo instance.

Screenshots

No response

[ghost]

This appears to happen only if the PR refers to a broken Git state. In our case, this happened by creating a PR via the API.

[wxiaoguang]

Wait for backport

[weezlemsneezle]

Is there a workaround for this issue? After the weekend all of our Pull-Requests suddenly show this error. All Pull-Request were created through the web-interface.
We would like to continue working with Pull-Requests as soon as possible and not wait for this bugfix to be released

[wxiaoguang]

If you are affected by this bug, you can try to download the latest 1.16-dev from https://dl.gitea.io/gitea/1.16/ , it includes this fix.

If the releases in https://dl.gitea.io/gitea/1.16/ doesn't help, then the bug you meet could be a new one.

[weezlemsneezle]

Thanks for the quick reply, I tried the dev-build and it indeed fixes the 500 HTTP-Error.
But, as predicted, the Pull-Request just says This pull request is broken due to missing fork information.
I think I should open a new Issue for this but I don't even know what to title it, I can clone the Project without issues, fsck doesn't say anything and the gitea log file also has nothing special even on debug, only the Pull-Requests seem broken