-
-
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
README.md in npm package cause gitea to crash #23082
Comments
I think the reason of the panic is the Line 615 in 6c35454
gitea/modules/templates/helper.go Lines 177 to 180 in 6c35454
|
lunny
added a commit
that referenced
this issue
Feb 24, 2023
Fix #23082. This bug is caused by a nil context in #23082 (comment) . --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
yardenshoham
pushed a commit
to yardenshoham/gitea
that referenced
this issue
Feb 24, 2023
Fix go-gitea#23082. This bug is caused by a nil context in go-gitea#23082 (comment) . --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
lunny
added a commit
that referenced
this issue
Feb 24, 2023
Backport #23092 Fix #23082. This bug is caused by a nil context in #23082 (comment) . Co-authored-by: Zettat123 <zettat123@gmail.com> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
After the attached file README.md is included in a npm package and published to GITea, and then when package details page is opened in GITea site for this package, GITea crashes (see attached error message)
In the README.md if the following line is removed and published, the gitea app/service does not fail when viewing the package details in GITea.
- The pacakge name @qccat-ui has been renamed to @qccat/core-ui.
Gitea Version
1.18.5
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
GITea is running in windows.
Database
None
The text was updated successfully, but these errors were encountered: