-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
1.23.8 -- crash in fetching notifications #34487
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
Code line doesn't match? https://github.com/go-gitea/gitea/blob/v1.23.8/models/issues/comment.go#L469 |
I've checked this already vs. our slightly patched package, and it looks like the same mismatch... 🤷 |
Well, the stacktrace should match .... Is it possible that the panic is caused by your patch? 🤔 According to the code, the crash is caused by |
No, panic is not caused by our patches.. They are LFS related in completely different part of the code... There's another crash that has to do with deleting comments. It seems also related to an issue+comment combo here.
|
They are the same phenomenons
|
The codepath looks familiar between the two crashes,
|
Also happens after comment.LoadIssue() call |
TBH I don't understand why it happens ... and why the code line in stacktrace doesn't match. Some thoughts (just FYI):
|
So, LoadIssue() doesn't load the issue if the issue != nil. Could it be something else than nil but invalid somehow? I'll look what's causing this more carefully. It's one of these "shouldn't happen but happens". |
Golang only uses "nil" or "non-nil" for struct pointer, no other "invalid value" |
Description
It looks like the issue is null here somehow
Gitea Version
1.23.8
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
self-compiled
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: