File edit didn't make it into Pending Change Set

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

Posts: 24
Joined: Fri Apr 30, 2004 2:38 pm

File edit didn't make it into Pending Change Set

Post by mattGreatPond » Thu May 06, 2004 8:29 am

We just made a modification to a file but the file didn't make it into the Pending Change Set. My co-worker first set the refresh interval to 1 minute, with no luck. The he discovered Refresh (F5) which also didn't work. Restarting the Vault client did work. I wish I could be more helpful, but this smells like something that could be hard to reproduce :cry:

Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear

Post by dan » Thu May 06, 2004 8:53 am

Vault uses file system notifications from .Net to be notified when a file changes while the GUI client is running. It is possible that the notification event wasn't sent to or recieved by Vault. We do scan working folders on certain operations such as setting a working folder (and on startup of the client) to update the status of any files that may not have been caught by the notification. Refresh is not included, because scanning is a really expensive operation when you have a lot of files within defined working folders.

If you explicitly check out a file, it will always appear in the pending change set.