not updating pending changes list

nmcalpin · Post by **nmcalpin** » Fri Aug 19, 2005 11:57 am

one of our developers reported this to me today:

"
I am still having a problem with Vault not updating the pending changes list
when I make a change to a file. I notice this happens most often when I
have a different folder selected in Vault from the folder I am currently
editing the file in. To fix this I have to select the file's folder, then
go to 'tools' and 'options' to force it to reload the current pending
changes worklist.
"

he said it's happening a LOT more often now that we updated to 3.1.1. We were running 3.0.6 i believe before.

any ideas?

nmcalpin · Post by **nmcalpin** » Fri Aug 19, 2005 12:02 pm

additional info from another one of our developers:

"
I suspect it has something to do with the depth of our folders, in that I
find things in shallow folders always get added to pending change list, but
things deep in our hierarchy do not. Anecdotal evidence at best at this
point, though -- I haven't actually tried to test this.
"

lbauer · Post by **lbauer** » Fri Aug 19, 2005 12:48 pm

I could use more information.

Are you using Vault 3.1.1 clients?

I am still having a problem with Vault not updating the pending changes list when I make a change to a file.

What kind of change did you make and what update did you expect to see in the pending change set? What did you see instead?

I notice this happens most often when I
have a different folder selected in Vault from the folder I am currently
editing the file in.

Do you mean you have FolderA highlighted in the Vault GUI Client and you're editing a file from FolderB? And the pending change set doesn't show any change to the file from FolderB?

To fix this I have to select the file's folder, then
go to 'tools' and 'options' to force it to reload the current pending
changes worklist.

Which option are you using in Tools-> Options to reload? The refresh every X minutes option?

If you use View->Refresh (F5) does it cause the pending change set to update properly?

nmcalpin · Post by **nmcalpin** » Thu Sep 22, 2005 9:37 am

lbauer wrote:I could use more information.

Are you using Vault 3.1.1 clients?

Yes - we upgraded all clients and server to 3.1.1 at the exact same time

lbauer wrote: What kind of change did you make and what update did you expect to see in the pending change set? What did you see instead?

I made a change to an asp file and I expected the change to appear on the
pending change set, so that I can check it in. Instead I saw the pending
change set remain empty.

lbauer wrote:Do you mean you have FolderA highlighted in the Vault GUI Client and you're editing a file from FolderB? And the pending change set doesn't show any change to the file from FolderB?

Correct.

lbauer wrote:Which option are you using in Tools-> Options to reload? The refresh every X minutes option?

No, I am opening the Tools-> Options screen, and then closing it. This
seems to force the pending change set to immediately refresh.

lbauer wrote:If you use View->Refresh (F5) does it cause the pending change set to update properly?

We believe so but I'm not 100% sure at this point.

nmcalpin · Post by **nmcalpin** » Thu Sep 22, 2005 9:39 am

Additional information from one of our developers:

I suspect it has something to do with the depth of our folders, in that I
find things in shallow folders always get added to pending change list, but
things deep in our hierarchy do not. Anecdotal evidence at best at this
point, though -- I haven't actually tried to test this.

dan · Post by **dan** » Thu Sep 22, 2005 1:17 pm

We fixed a bug in the 3.0.x timeframe where too many files were changed at the same time (because a program was modifying the file datetimes), and the .Net class that sends edited files to Vault overflows at a certain point.

Turn on GUI client logging and when this happens again, check the log to see whether an overflow error happened. What should happen in that case is that a full working folder scan will be started, but if you have a lot of working folders defined, it may take up to a few mintues to scan them all and update status.

Also, I would make absolutely sure that the user who reported this is on the latest client, by manually checking Help->About on that machine. Sometimes a user thinks they upgraded, but it is possible something went wrong and unnoticed and they are actually at a lower version, which in this case would be important.