Locked out of the ability to comment on the code of a PR sometimes

[parnic-sks]

• Gitea version (or commit ref): 1.12.2
• Git version: 2.27.0.windows.1
• Operating system: Windows Server 2019 Standard
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes https://try.gitea.io/hardi/pull-request-test/pulls/1/files
  • No
  • Not relevant
• Log gist: https://gist.github.com/parnic-sks/32d4e95c485e45a00e551342c0fedaf0

Description

We are using Gitea on a small team (5 programmers) and fairly regularly run into a case where the "Files Changed" tab on a pull request is no longer accessible with some variation on this error message:

1.12.2:

template: repo/diff/box:152:65: executing "repo/diff/box" at <0>: nil pointer evaluating *models.Review.Type

1.12.1:

template: repo/diff/section_unified:28:53: executing "repo/diff/section_unified" at <0>: nil pointer evaluating *models.Review.Type

We have sometimes been able to find the offending comment in the database and update its Review ID to the appropriate ID. This gets difficult when a lot of comments have been made on other PRs between noticing the problem and trying to fix it.

We don't have a specific reproduction case that triggers this, but in general it seems it is sometimes possible to fail to assign the appropriate review ID in a comment which then breaks the ability to review changes line-by-line on a given PR.

Screenshots

Nothing to show, really, since it's just an error. Loading the Files Changed tab attempts to GET /org/repo/pulls/:pull_id/files, which returns 500 and the above error as plain text.

[aloosley]

I seem to have something similar. After commenting for a while on the Files Changed page, this eventually displayed in my browser:

template: repo/diff/box:152:65: executing "repo/diff/box" at <0>: nil pointer evaluating *models.Review.Type

I don't recall any comment being anything special other than containing some code snippets and a weblink. Now I cannot access that part of the PR anymore :-(.

---

• Gitea version (or commit ref): 1.12.1 --> Problem persisted after downgrading to 1.12.0 --> Update problem goes away when downgrading to 1.11.3 (maybe 1.11.* in general but haven't tested)
• Operating system: Pop_OS! 20.04

[lafriks]

To what review ID that comment was pointing to (other PR/repo)?

[aloosley]

To what review ID that comment was pointing to (other PR/repo)?

I don't know, I was using the Add single comment button every time. Do you have any hint on how to get that info?

Later in the day, I decided to avoid the Add single comment button by writing a bunch of comments in a single review submission instead. Later I got a 500 error when I tried to submit the review.

We have since downgraded 1.11.3 (the version we had before upgrading to 1.12.0/1), I've tried all the review / comment functionality and everything seems to work fine again.

We upgraded simply by pulling the new docker image and starting it on top of our pre-existing gitea database. Is it possible the database from 1.11.3 are not compatible with 1.12.0/1?

[parnic-sks]

To what review ID that comment was pointing to (other PR/repo)?

For our case, the comment should have been pointing at PR 35, internal review id 192 or something. I think, based on perusing the pgsql database a bit, that the review ID is actually set to 0 on the offending comment.

I was using the Add single comment button

This is how most of our review comments are done as well.

Later I got a 500 error when I tried to submit the review.

We see this occasionally as well, usually when the code has changed between the time the PR was loaded and the comment was submitted, but we see it other times as well.

Is it possible the database from 1.11.3 are not compatible with 1.12.0/1?

1.12.1 was the first version we installed and we are seeing the issue, so I think it's unlikely to be a db upgrade bug.

[lafriks]

Thanks, will try to reproduce

[tanrui8765]

having the same problem as well. I added several pieces of comments with Add single comment, then click on File Changed tab, problem appeared.

template: repo/diff/box:152:65: executing "repo/diff/box" at <0>: nil pointer evaluating *models.Review.Type

I am using Gitea 1.12.2, too. Windows Server 2008, MySQL.

[svenseeberg]

I can confirm that the issue exists on on Gitea 1.12.3. with sqlite. It worked after creation of the PR, but broke after 1 or 2 inline comments were added. So I guess there is an issue with rendering already existing comments?

Also, one user noted that his comments were not visible at all in the beginning. Not sure if this is related or reproducible.

[bendem]

Having the same issue, let me know if there is anything I can do to help debug this.

[zeripath]

I initially was wondering if this was some issue with a certain number of reviews but I just added >80 reviews to a PR on my test instance and it hasn't failed (albeit this is on master/1.13) Is anyone able to confirm that the bug is not present on master/try?

I would guess that at least a temporary solution would involve monkey patching the template repo/diff/box.tmpl to prevent the NPE around line 152.

[singalen]

Very stable to reproduce here: https://try.gitea.io/hardi/pull-request-test/pulls/1/files

[zeripath]

Cool that means it's definitely not just a 1.12 issue. It's really weird that I can't forcibly reproduce on my dev machine