Revisions tab and commit signature #1283

New Issue

GiteaMirror · 2025-11-02T03:55:29-06:00

GiteaMirror commented

2025-11-02 03:55:29 -06:00

Originally created by @deguif on GitHub (Nov 27, 2017).

Gitea version (f148a4a):
Git version:
Operating system:
Database:
- PostgreSQL
Can you reproduce the bug at https://try.gitea.io:
- not yet

Description

When displaying the revisions tab on a PR, when there are commit signatures, this error is shown:
template: repo/commits_table:45:90: executing "repo/commits_table" at <.Verification.Verifi...>: can't evaluate field Verification in type interface {}

Originally created by @deguif on GitHub (Nov 27, 2017). - Gitea version (f148a4a): - Git version: - Operating system: - Database: - [x] PostgreSQL - Can you reproduce the bug at https://try.gitea.io: - [ ] not yet ## Description When displaying the revisions tab on a PR, when there are commit signatures, this error is shown: `template: repo/commits_table:45:90: executing "repo/commits_table" at <.Verification.Verifi...>: can't evaluate field Verification in type interface {}`

GiteaMirror added the issue/not-a-bug label 2025-11-02 03:55:29 -06:00

GiteaMirror closed this issue

2025-11-02 03:55:29 -06:00

GiteaMirror commented

2025-11-02 03:55:30 -06:00

@deguif commented on GitHub (Nov 27, 2017):

Need testing on my side, as this probably due to wrong docker image. I suspect wrong version for latest tag on my machine.

@deguif commented on GitHub (Nov 27, 2017): Need testing on my side, as this probably due to wrong docker image. I suspect wrong version for latest tag on my machine.

GiteaMirror commented

2025-11-02 03:55:30 -06:00

@deguif commented on GitHub (Nov 27, 2017):

@lafriks sorry, the bug is my fault. I should have investigated a little more before creating the issue.
This was due to docker compose which doesn't pull latest image when it already has it locally. It instead used my local latest image which was old. That's why commit verification were not present.

This can be closed, and sorry again for this.

@deguif commented on GitHub (Nov 27, 2017): @lafriks sorry, the bug is my fault. I should have investigated a little more before creating the issue. This was due to docker compose which doesn't pull latest image when it already has it locally. It instead used my local latest image which was old. That's why commit verification were not present. This can be closed, and sorry again for this.

GiteaMirror commented

2025-11-02 03:55:30 -06:00

@sapk commented on GitHub (Nov 27, 2017):

@deguif you can close the issue yourself if no admin as done it before you read this message.

@sapk commented on GitHub (Nov 27, 2017): @deguif you can close the issue yourself if no admin as done it before you read this message.

GiteaMirror commented

2025-11-02 03:55:30 -06:00

@lafriks commented on GitHub (Nov 27, 2017):

Thanks for letting know

@lafriks commented on GitHub (Nov 27, 2017): Thanks for letting know

GiteaMirror referenced this issue

2025-11-02 11:56:07 -06:00