Version
0.14.5
Operating System
Windows
Distribution Method
msi (Windows)
Describe the issue
With the latest release I gave SSH signing on Windows another go, this used to show Program not found.
It's now getting further but I'm still hitting an issue with it now instead returning Failed to sign SSH: Cannot open C:UsersDanielWAppDataLocalTemp.tmp1cG0m8 for signing: No such file or directory
Looks like sh from Git likes the windows formatted path being passed in, curiously the signing key which is also a similar path does work though.
How to reproduce (Optional)
- Open Gitbutler & Navigate to the Git settings of a Project
- Select to Sign commits & configure for SSH signing with a valid key & signing program empty (default)
- Click Test Signing
Expected behavior (Optional)
I should be able to sign using SSH on Windows without receiving an error.
Relevant log output (Optional)
From Test in Settings
2025-01-20T21:05:10.414873Z INFO check_signing_settings: crates\gitbutler-tauri\src\repo.rs:39: new id=7f364b41-2e01-4bef-abb3-9529ca64f1c6
2025-01-20T21:05:10.468239Z ERROR check_signing_settings: crates\gitbutler-tauri\src\repo.rs:39: error=Error(Failed to sign SSH: Cannot open C:UsersDanielWAppDataLocalTemp.tmp1id5Uw for signing: No such file or directory
) id=7f364b41-2e01-4bef-abb3-9529ca64f1c6
2025-01-20T21:05:10.468268Z INFO check_signing_settings: crates\gitbutler-tauri\src\repo.rs:39: close time.busy=53.4ms time.idle=10.2µs id=7f364b41-2e01-4bef-abb3-9529ca64f1c6
From Committing
2025-01-20T20:56:33.865799Z INFO commit_virtual_branch: crates\gitbutler-tauri\src\virtual_branches.rs:31: new project_id=7f364b41-2e01-4bef-abb3-9529ca64f1c6 branch=2d6b08c6-db63-4e8c-9d18-ed34e411a83a Test commit ownership=Some(BranchOwnershipClaims { claims: [OwnershipClaim { file_path: "CHANGELOG.md", hunks: [Hunk { hash: Some(75b3ae88934aac9988ec5ca701136536), start: 1, end: 7 }] }] })
2025-01-20T20:56:33.973946Z ERROR commit_virtual_branch: crates\gitbutler-tauri\src\virtual_branches.rs:31: error=Error(failed to commit
Caused by:
0: errors.commit.signing_failed
1: Failed to sign commit: Failed to sign SSH: Cannot open C:UsersDanielWAppDataLocalTemp.tmpdhLpLR for signing: No such file or directory
) project_id=7f364b41-2e01-4bef-abb3-9529ca64f1c6 branch=2d6b08c6-db63-4e8c-9d18-ed34e411a83a Test commit ownership=Some(BranchOwnershipClaims { claims: [OwnershipClaim { file_path: "CHANGELOG.md", hunks: [Hunk { hash: Some(75b3ae88934aac9988ec5ca701136536), start: 1, end: 7 }] }] })
2025-01-20T20:56:33.973978Z INFO commit_virtual_branch: crates\gitbutler-tauri\src\virtual_branches.rs:31: close time.busy=108ms time.idle=9.50µs project_id=7f364b41-2e01-4bef-abb3-9529ca64f1c6 branch=2d6b08c6-db63-4e8c-9d18-ed34e411a83a Test commit ownership=Some(BranchOwnershipClaims { claims: [OwnershipClaim { file_path: "CHANGELOG.md", hunks: [Hunk { hash: Some(75b3ae88934aac9988ec5ca701136536), start: 1, end: 7 }] }] })
Version
0.14.5
Operating System
Windows
Distribution Method
msi (Windows)
Describe the issue
With the latest release I gave SSH signing on Windows another go, this used to show
Program not found.It's now getting further but I'm still hitting an issue with it now instead returning
Failed to sign SSH: Cannot open C:UsersDanielWAppDataLocalTemp.tmp1cG0m8 for signing: No such file or directoryLooks like sh from Git likes the windows formatted path being passed in, curiously the signing key which is also a similar path does work though.
How to reproduce (Optional)
Expected behavior (Optional)
I should be able to sign using SSH on Windows without receiving an error.
Relevant log output (Optional)
From Test in Settings
From Committing