aboutsummaryrefslogtreecommitdiffstats
path: root/modules/git/diff.go
diff options
context:
space:
mode:
authorcharles <30816317+charles7668@users.noreply.github.com>2024-03-02 21:38:34 +0800
committerGitHub <noreply@github.com>2024-03-02 13:38:34 +0000
commit423372d84ab3d885e47d4a00cd69d6040b61cc4c (patch)
treeb30f51928601801ecd0e30387f5c518ac643755a /modules/git/diff.go
parente650f64d812f5ebeb4a11d2ec20f2376c6d963bc (diff)
downloadgitea-423372d84ab3d885e47d4a00cd69d6040b61cc4c.tar.gz
gitea-423372d84ab3d885e47d4a00cd69d6040b61cc4c.zip
Add a check for when the command is canceled by the program on Window… (#29538)
Close #29509 Windows, unlike Linux, does not have signal-specified exit codes. Therefore, we should add a Windows-specific check for Windows. If we don't do this, the logs will always show a failed status, even though the command actually works correctly. If you check the Go source code in exec_windows.go, you will see that it always returns exit code 1. ![image](https://github.com/go-gitea/gitea/assets/30816317/9dfd7c70-9995-47d9-9641-db793f58770c) The exit code 1 does not exclusively signify a SIGNAL KILL; it can indicate any issue that occurs when a program fails.
Diffstat (limited to 'modules/git/diff.go')
0 files changed, 0 insertions, 0 deletions