Show 404 ERROR when show a commit view with too more files changed #2763

Closed
opened 2025-11-02 04:47:26 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @FalconWu2017 on GitHub (Jan 17, 2019).

  • Gitea version (or commit ref):1.6.4
  • Git version:2.10
  • Operating system:Windows 2012 data center
  • 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:

2019/01/17 14:47:25 [D] Detected encoding: utf-8 (fast)

There are the same 100 lines above.

2019/01/17 14:47:25 [...uters/repo/commit.go:215 Diff()] [E] GetDiffCommit: Wait: exit status 128
2019/01/17 14:47:25 [D] Template: status/404

Description

It will be 404 when you show commit that are more then 100 files changed in the commit.
The MAX_GIT_DIFF_FILES set max number of files in diff view.If I change this setting to large enough,it will be OK.
But in any case,404? Not good.

Originally created by @FalconWu2017 on GitHub (Jan 17, 2019). - Gitea version (or commit ref):1.6.4 - Git version:2.10 - Operating system:Windows 2012 data center - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X] Not relevant - Log gist: 2019/01/17 14:47:25 [D] Detected encoding: utf-8 (fast) > There are the same 100 lines above. 2019/01/17 14:47:25 [...uters/repo/commit.go:215 Diff()] [E] GetDiffCommit: Wait: exit status 128 2019/01/17 14:47:25 [D] Template: status/404 ## Description It will be 404 when you show commit that are more then 100 files changed in the commit. The `MAX_GIT_DIFF_FILES` set max number of files in diff view.If I change this setting to large enough,it will be OK. But in any case,404? Not good.
GiteaMirror added the issue/confirmedtype/enhancement labels 2025-11-02 04:47:26 -06:00
Author
Owner

@stale[bot] commented on GitHub (Mar 18, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 18, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Author
Owner

@delvh commented on GitHub (Apr 29, 2023):

I think the behavior was vastly improved in the meantime.
Please check if your issue still exists, and reopen this issue if yes.

@delvh commented on GitHub (Apr 29, 2023): I think the behavior was vastly improved in the meantime. Please check if your issue still exists, and reopen this issue if yes.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2763