Hi,
first of all, thanks for the wonderful tool. I do have one small problem to report, though. I have renamed one of my files on one of the two computers from which I access my source code repository. Note that the only difference was case - I renamed something like "color.cs" to "Color.cs".
I had Vault open on the other machine (not the one where rename was performed from) but it was not active - this machine is laptop, and was in hibernate at that moment.
When I started using the laptop, I did usual "Get latest version" and noticed that I still have renamed file (old name, "color.cs") marked as "Modified" (+22 bytes) even though the file itself was identical to the repository version.
Trying to fix things, I deleted complete folder and did another "Get latest version", but no change.
Now I have both "color.cs" and "Color.cs" marked as changed, I can do whatever I want with the "Color.cs" (new name) and it will work as expected, but the file-change with old name "color.cs" is stuck "nowhere" and I cannot do anything with it, not even "Undo Change" - when I try that, simply nothing happens.
Is there any way to get rid of this phantom file-change? It's really irritating to have this phony change constantly in my changeset...
Thanks in advance,
Drazen
Renamed files on one computer not recognized on another
Moderator: SourceGear
I'm not sure I fully understand what is happening:
1. Are you using the GUI client or the IDE client?
2. Is the problem in the pending change set only? If so, you can simply remove the file that shouldn't belong from there.
3. Is the problem that both color.cs and Color.cs are showing up in the file list in the GUI client? Or are they both showing up in the IDE file list?
1. Are you using the GUI client or the IDE client?
2. Is the problem in the pending change set only? If so, you can simply remove the file that shouldn't belong from there.
3. Is the problem that both color.cs and Color.cs are showing up in the file list in the GUI client? Or are they both showing up in the IDE file list?
Renaming a file makes its change get "stuck"
Ahh,dan wrote:I'm not sure I fully understand what is happening:
1. Are you using the GUI client or the IDE client?
2. Is the problem in the pending change set only? If so, you can simply remove the file that shouldn't belong from there.
3. Is the problem that both color.cs and Color.cs are showing up in the file list in the GUI client? Or are they both showing up in the IDE file list?
as a programmer myself, I should have known that my "bug report" should have been more detailed and including better "steps to reproduce"...
Here we go, this time I hope I'll be more precise:
1. I am using GUI client on two machines (server runs on third), all machines have version 2.0.6 running on them
2. The problem is only false report of changed file that does not exist in the repository any more. How do I remove it from there if not by either commit or undo change? As I've mentioned, neither of these operations work on this phantom change. There is one entry in the change set that I cannot get rid of, stating that "color.cs' has +22 bytes change. "color.cs" does not exist any more, it has been replaced correctly with "Color.cs", but note that the change happened on the other machine (and the problem does not exhibit itself there).
3. No, the file exist as only one in the repository, with a new name, and I can normally work with it. It has its history preserved, and is in good state.
I should probably add that I do not have "auto-commit" option turned on, so I had to manually commit this change. I also use CVS style of work.
If there's anything else to add, please let me know.
Thanks,
Drazen
It looks like the renamed file had been modified on the other machine, and now is stuck in your pending change set, because it no longer matches a file in the file list.
I'll log this as an issue, since you should be able to remove a file from the change set, even if it no longer exists in the repository.
In the meantime, you'll need to clean out your pending change set by removing the cache file. See http://support.sourcegear.com/viewtopic.php?t=6 for how to do this - you want to remove either the CacheMember_ChangeSetItems or CacheMember_KnownChanges files from %APPDATA%\SourceGear\Vault_1\Client\{repository-guid}\{vaultuser}\
Note that removing these files will remove all items from your change set, so you'll need make sure it is in a state that you are happy with. A file scan on Vault startup should repopulate it with files that have been modified though.
I'll log this as an issue, since you should be able to remove a file from the change set, even if it no longer exists in the repository.
In the meantime, you'll need to clean out your pending change set by removing the cache file. See http://support.sourcegear.com/viewtopic.php?t=6 for how to do this - you want to remove either the CacheMember_ChangeSetItems or CacheMember_KnownChanges files from %APPDATA%\SourceGear\Vault_1\Client\{repository-guid}\{vaultuser}\
Note that removing these files will remove all items from your change set, so you'll need make sure it is in a state that you are happy with. A file scan on Vault startup should repopulate it with files that have been modified though.
I made sure that I did "Undo change" on the other machine. The change set list was empty when I left...dan wrote:It looks like the renamed file had been modified on the other machine, and now is stuck in your pending change set, because it no longer matches a file in the file list.
I'll log this as an issue, since you should be able to remove a file from the change set, even if it no longer exists in the repository.
In the meantime, you'll need to clean out your pending change set by removing the cache file. See http://support.sourcegear.com/viewtopic.php?t=6 for how to do this - you want to remove either the CacheMember_ChangeSetItems or CacheMember_KnownChanges files from %APPDATA%\SourceGear\Vault_1\Client\{repository-guid}\{vaultuser}\
Note that removing these files will remove all items from your change set, so you'll need make sure it is in a state that you are happy with. A file scan on Vault startup should repopulate it with files that have been modified though.
I have no changes at the moment besides this phantom one, so the cure you propose should do the trick.
Thanks again,
Drazen