Command line checkout making writeable when checkout fails

[jthrush]

If a file has been checked out (exclusively) by someone else, and I use Vault GUI to try to check out, the check out fails and the file stays read-only. Good. However, if I use the command line vault.exe, the check out fails, but the file is marked writeable.

This is a real problem for our source control integration as it will lead to lost work (someone will think they have the file checked out and commence working with it when they don't, only to be informed on check-in that their changes are useless).

I see this is listed as a "feature" here:
http://support.sourcegear.com/viewtopic ... 13&t=10848 ("Failed check out removes read-only flag for a file")
Why on earth would you do this on purpose? If a check out fails, the file should stay read-only. Any chance of getting a fix for this?

[lbauer]

What version of Vault are you seeing this in?

[jthrush]

Command line client 4.1.4.18402
Server version 4.1.4.18402
Vault client 4.1.4.18402

[lbauer]

I was able to reproduce this and have logged it as bug 14350. I'm not sure when it will be fixed.

I see this is listed as a "feature" here:
viewtopic.php?f=13&t=10848 ("Failed check out removes read-only flag for a file")
Why on earth would you do this on purpose? If a check out fails, the file should stay read-only.

It's actually not a feature, though I agree it's not clearfrom the posting. This was a bug fixed in the Vault GUI Client, but evidently the fix did not extend to the Command Line Client.

[jthrush]

Awesome, thank you!

[lbauer]

You're welcome.