Submit the history html 404 pushed by client #3273

New Issue

GiteaMirror · 2025-11-02T05:06:16-06:00

GiteaMirror commented

2025-11-02 05:06:16 -06:00

Originally created by @ayanjoyful on GitHub (Apr 30, 2019).

Gitea version (or commit ref):
Git version:1.7.6
Operating system:
Database (use [x]):
- PostgreSQL
- [*] MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

Description

As shown in figure:
The commit history in the red circle is from the client,Click on the error.Page 500.
Background the log Error Page 404
...

Screenshots

Originally created by @ayanjoyful on GitHub (Apr 30, 2019). - Gitea version (or commit ref): - Git version:1.7.6 - Operating system: - Database (use `[x]`): - [ ] PostgreSQL - [*] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: ## Description ![QQ图片20190430173321](https://user-images.githubusercontent.com/28719668/56953016-243c0a80-6b6e-11e9-967a-be6c8230dd5e.png) As shown in figure: The commit history in the red circle is from the client,Click on the error.Page 500. Background the log Error Page 404 ... ## Screenshots

GiteaMirror added the type/bug label 2025-11-02 05:06:16 -06:00

GiteaMirror closed this issue

2025-11-02 05:06:16 -06:00

GiteaMirror commented

2025-11-02 05:06:17 -06:00

@lunny commented on GitHub (May 1, 2019):

Could you confirm that v1.8.0 fix that?

@lunny commented on GitHub (May 1, 2019): Could you confirm that v1.8.0 fix that?

GiteaMirror commented

2025-11-02 05:06:17 -06:00

@saitho commented on GitHub (May 1, 2019):

Did you click on the commit hash or did you click on the commit message (7777777777)?
If latter one: that is because Gitea sees that as a possible SHA hash and links it to a commit.

Example on try.gitea.org (latest commit): https://try.gitea.io/saitho/test/commits/branch/test2

@saitho commented on GitHub (May 1, 2019): Did you click on the commit hash or did you click on the commit message (7777777777)? If latter one: that is because Gitea sees that as a possible SHA hash and links it to a commit. Example on try.gitea.org (latest commit): https://try.gitea.io/saitho/test/commits/branch/test2

GiteaMirror commented

2025-11-02 05:06:17 -06:00

@mrsdizzie commented on GitHub (May 1, 2019):

For consistency we probably shouldn't render the commit Subject with the post processors so there aren't any autolink type things generated -- which means every Subject in that main list view will link to the actual commit without the chance that some link elsewhere.

Separate, this is probably another instance where if we checked if a hash existed first it wouldn't generate the link (though none of these subjects should end up links to elsewhere even if they are valid).

@mrsdizzie commented on GitHub (May 1, 2019): For consistency we probably shouldn't render the commit Subject with the post processors so there aren't any autolink type things generated -- which means every Subject in that main list view will link to the actual commit without the chance that some link elsewhere. Separate, this is probably another instance where if we checked if a hash existed first it wouldn't generate the link (though none of these subjects should end up links to elsewhere even if they are valid).

GiteaMirror commented

2025-11-02 05:06:17 -06:00

@lunny commented on GitHub (May 6, 2019):

It seems this should be backport to release/v1.8

@lunny commented on GitHub (May 6, 2019): It seems this should be backport to release/v1.8

GiteaMirror referenced this issue

2025-11-02 12:20:37 -06:00

[PR #3273] [MERGED] Remove unused vendor github.com/stretchr/testify/require #16853

Sign in to join this conversation.