Progress dialog behavior upon cancelling long Git operations

Question

TortoiseGit executes long-running operations such as fetch, push, and clone through a dedicated progress dialog. When a user manually triggers the 'Cancel' action during these operations, the UI's behavior depends on the configuration settings found under Settings > Dialogs 2.
There is an uncertainty regarding how the application distinguishes between an 'interrupted' state and a standard 'failure' when the auto-close logic is applied. While the UI attempts to terminate the process tree, the presence of child processes—such as SSH clients (Plink) or credential helpers—can cause the dialog to appear hung while waiting for those subprocesses to exit gracefully.
How does TortoiseGit classify a manually cancelled operation versus a network timeout in its auto-close logic? Is there a specific configuration to ensure the dialog closes immediately upon cancellation without waiting for child process termination, or is the dialog required to remain open to display diagnostic output?

Muntasir · Answer

Direct Resolution
TortoiseGit does not classify a manually cancelled operation differently from a network timeout regarding the Auto-close if no errors setting (Settings > Dialogs 2); both result in the dialog remaining open because they are treated as errors (non-zero exit codes). There is no configuration to force immediate dialog closure upon cancellation while bypassing the wait for child process termination.

Confirmed Facts on Behavior

Cancellation typically yields exit code 128 (or 130) with a log message indicating 'user cancelled'.
Network timeouts yield exit code 128 but display messages like 'Connection timed out' in the log pane.
The dialog waits for the entire process tree (git.exe, plink.exe, credential helpers) to signal exit before the Close button becomes active.

Necessary Steps for Cancellation

Ensure Auto-close if no errors is unchecked in Settings > Dialogs 2.
Initiate the long Git operation (fetch, push, clone).
Click Cancel; the dialog will remain open immediately without waiting for auto-close logic.
Manually click the Close button once it is enabled, which occurs after the underlying process tree terminates asynchronously.

Diagnostic Requirement
To refine the recommendation, please specify which SSH client is being used (e.g., Plink, Windows OpenSSH, or a custom GIT_SSH_COMMAND).

Progress dialog behavior upon cancelling long Git operations

1 answer

Direct Resolution

Confirmed Facts on Behavior

Necessary Steps for Cancellation

Diagnostic Requirement

Your perspective belongs here.

1 question comment