[Bug] Occasional "handle is invalid" error when tagging commits

[ravindUwU]

I've noticed a dialog with this message pop up sometimes, when tagging commits: run 'C:\Users\ravindUwU\scoop\apps\git\current\bin\git.exe tag --annotate tagMessage c5ac73 -F C:\Users\ravindUwU\AppData\Local\Temp\Fork\fork-tagMessage.txt': The handle is invalid. (os error 6).

Checking the folder %LOCALAPPDATA%\Temp\Fork afterward, I noticed that the referenced file %LOCALAPPDATA%\Temp\Fork\fork-tagMessage.txt doesn't exist (although I guess it's possible that it was quickly created and deleted by Fork 🤷).

Retrying after restarting Fork usually helps, but not always 🤷. Fork 2.3.1.0 running on Windows 11 Enterprise 23H2 22631.4460.

[DanPristupov]

Please contact me by email ([email protected]).

[assuiedmilan]

I have the same error, the file is indeed deleted when we try to create a tag.

[DanPristupov]

I can't reproduce the problem myself. So I need someone to contact me, otherwise I won't be able to fix this.

[laomao800]

I have the same error, the file is indeed deleted when we try to create a tag.

For me, it was solved after reinstalling the program.
👀

[DanPristupov]

@laomao800 no, it wasn't.

[force-net]

Same issue. If it still not reproduced, I can contact by email

[zootius]

Just to say I encountered this same error today when trying to add a tag. However I closed and restarted Fork and then it allowed me to tag without error.

Fork v2.3.1.0 running on Windows 10

[force-net]

run 'C:\Users\force\AppData\Local\Fork\gitInstance\2.45.2\bin\git.exe tag --annotate test commit_hash -F C:\Users\force\AppData\Local\Temp\1\Fork\fork-tagMessage.txt': The handle is invalid. (os error 6)

Folder C:\Users\force\AppData\Local\Temp\1\Fork\ exists.
Remove folder - new folder is created, same error message.
Deny permissions to remove file. fork-tagMessage.txt is created with correct contents, error is same.
Another try to create tag - all fine.
Restoring permissions, deleting file - all fine.

Looks like magic

[aledalmas]

Same problem, restarting fork solved the issue today

[KENNYSOFT]

I've reproduced it.
The first tagging after the program startup is always a success, and the following tagging to the different commits always fails.

[DanPristupov]

@KENNYSOFT can you contact me by email ([email protected]) so we can confirm if the problem is fixed?