Codeberg/Community
54
325
Fork
You've already forked Community
12

issues list error => .."nil pointer evaluating *models.User.ID" #104

Closed
opened 2019年12月04日 17:17:35 +01:00 by libBletchley · 4 comments

Trying to list closed issues gives:

template: repo/issue/list:236:26: executing "repo/issue/list" at <.Poster.ID>: nil pointer evaluating *models.User.ID

Another repo gives:

template: repo/issue/view_content/comments:102:45: executing "repo/issue/view_content/comments" at <.Poster.HomeLink>: error calling HomeLink: runtime error: invalid memory address or nil pointer dereference

Trying to list closed issues gives: `template: repo/issue/list:236:26: executing "repo/issue/list" at <.Poster.ID>: nil pointer evaluating *models.User.ID` Another repo gives: `template: repo/issue/view_content/comments:102:45: executing "repo/issue/view_content/comments" at <.Poster.HomeLink>: error calling HomeLink: runtime error: invalid memory address or nil pointer dereference`

Duplicate of #99

The second error, which repo is that?

As I wrote in the other issue, it happens somehow with deleted users, but is not reproducible.

Duplicate of #99 The second error, which repo is that? As I wrote in the other issue, it happens somehow with deleted users, but is not reproducible.

I don't recall, but the repo I visit the most is crimeflare/cloudflare-tor. I cannot visit the closed issues list because of this. It's a quite serious problem. Perhaps the version should be rolled back to what it was a week or so ago.

I don't recall, but the repo I visit the most is crimeflare/cloudflare-tor. I cannot visit the closed issues list because of this. It's a quite serious problem. Perhaps the version should be rolled back to what it was a week or so ago.

@libBletchley

I know, I have fixed the corrupt database manually again for the fist error (I know the cause, it is known to gitea guys also now, we could reliably reproduce it). The second error I never saw.

The bug is "database corruption if editing issues created by a deleted user via gitea API". Unfortunately your collaborators chose the path to create throwaway users for each and every single comment. And the way they work in addition to using the API causes this.

But again THIS IS A BUG and I will deploy a real fix as soon as I can.

@libBletchley I know, I have fixed the corrupt database manually again for the fist error (I know the cause, it is known to gitea guys also now, we could reliably reproduce it). The second error I never saw. The bug is "database corruption if editing issues created by a deleted user via gitea API". Unfortunately your collaborators chose the path to create throwaway users for each and every single comment. And the way they work in addition to using the API causes this. But again THIS IS A BUG and I will deploy a real fix as soon as I can.

This should fixed, please reopen when it re-occurs

This should fixed, please reopen when it re-occurs
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#104
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?