Vault 4.0.2 command line history file names are truncated
Moderator: SourceGear
Vault 4.0.2 command line history file names are truncated
When invoking the history command with the command line client of Vault 4.0.2, I get an output where the first directory in the file name is missing:
<vault>
<history>
<item txid="52399" date="25.07.2007 10:32:34" name="A/file.xxx" type="60" typeName="CheckIn" version="84" objverid="342905" user="user" comment="comment" actionString="Checked In" />
</history>
<bugsreferenced />
<result>
<success>True</success>
</result>
</vault>
However, the correct file name would be: $/XXXA/file.xxx
Since this command is used by CCNET to detect changes, we get broken names in the build reports too.
<vault>
<history>
<item txid="52399" date="25.07.2007 10:32:34" name="A/file.xxx" type="60" typeName="CheckIn" version="84" objverid="342905" user="user" comment="comment" actionString="Checked In" />
</history>
<bugsreferenced />
<result>
<success>True</success>
</result>
</vault>
However, the correct file name would be: $/XXXA/file.xxx
Since this command is used by CCNET to detect changes, we get broken names in the build reports too.
I need to make sure I understand this fully.
You have a file at $/aa/bb/cc/dd.txt. You run history on $/aa/bb/cc. The results say then cc/dd.txt instead of $/aa/bb/cc/dd.txt?
If that's the case, and you just want to see the path above the folder you ran the history on, then I can create a feature request for the full path name there.
You have a file at $/aa/bb/cc/dd.txt. You run history on $/aa/bb/cc. The results say then cc/dd.txt instead of $/aa/bb/cc/dd.txt?
If that's the case, and you just want to see the path above the folder you ran the history on, then I can create a feature request for the full path name there.
No, it's exactly as I wrote. The name is truncated up to the first char before the second /.
So, if the file in the repository is called
$/XXXA/anything
the history comment will return
A/anything
My guess is that internally there is some code that is supposed to cut off everything before the "$" that just happens to do this on the wrong / character.
So, if the file in the repository is called
$/XXXA/anything
the history comment will return
A/anything
My guess is that internally there is some code that is supposed to cut off everything before the "$" that just happens to do this on the wrong / character.
Client Information
Vault Client Version: 4.0.2.15802
.Net Framework Version: 2.0.50727.42
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 1.0
OS Version: 5.2.3790
Total Physical Memory: 1023.47 MB
Time Zone: (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
Server Information
Vault Server Version: 4.0.2.15802
.Net Framework Version: 2.0.50727.832
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
SQL Version: Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
License Information
30 serial number(s):
1 of 30: 1 full users, permanent
2 of 30: 1 full users, permanent
3 of 30: 1 full users, permanent
4 of 30: 1 full users, permanent
5 of 30: 1 full users, permanent
6 of 30: 1 full users, permanent
7 of 30: 1 full users, permanent
8 of 30: 1 full users, permanent
9 of 30: 1 full users, permanent
10 of 30: 1 full users, permanent
11 of 30: 1 full users, permanent
12 of 30: 1 full users, permanent
13 of 30: 1 full users, permanent
14 of 30: 1 full users, permanent
15 of 30: 1 full users, permanent
16 of 30: 1 full users, permanent
17 of 30: 1 full users, permanent
18 of 30: 1 full users, permanent
19 of 30: 1 full users, permanent
20 of 30: 1 full users, permanent
21 of 30: 1 full users, permanent
22 of 30: 1 full users, permanent
23 of 30: 1 full users, permanent
24 of 30: 1 full users, permanent
25 of 30: 1 full users, permanent
26 of 30: 1 full users, permanent
27 of 30: 1 full users, permanent
28 of 30: 1 full users, permanent
29 of 30: 1 full users, permanent
30 of 30: 1 full users, permanent
Vault Client Version: 4.0.2.15802
.Net Framework Version: 2.0.50727.42
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 1.0
OS Version: 5.2.3790
Total Physical Memory: 1023.47 MB
Time Zone: (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
Server Information
Vault Server Version: 4.0.2.15802
.Net Framework Version: 2.0.50727.832
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
SQL Version: Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
License Information
30 serial number(s):
1 of 30: 1 full users, permanent
2 of 30: 1 full users, permanent
3 of 30: 1 full users, permanent
4 of 30: 1 full users, permanent
5 of 30: 1 full users, permanent
6 of 30: 1 full users, permanent
7 of 30: 1 full users, permanent
8 of 30: 1 full users, permanent
9 of 30: 1 full users, permanent
10 of 30: 1 full users, permanent
11 of 30: 1 full users, permanent
12 of 30: 1 full users, permanent
13 of 30: 1 full users, permanent
14 of 30: 1 full users, permanent
15 of 30: 1 full users, permanent
16 of 30: 1 full users, permanent
17 of 30: 1 full users, permanent
18 of 30: 1 full users, permanent
19 of 30: 1 full users, permanent
20 of 30: 1 full users, permanent
21 of 30: 1 full users, permanent
22 of 30: 1 full users, permanent
23 of 30: 1 full users, permanent
24 of 30: 1 full users, permanent
25 of 30: 1 full users, permanent
26 of 30: 1 full users, permanent
27 of 30: 1 full users, permanent
28 of 30: 1 full users, permanent
29 of 30: 1 full users, permanent
30 of 30: 1 full users, permanent
We haven't been able to reproduce this problem on our end. Could you give me the full path or paths that are giving this problem (you can email it to me with the button below this post if you'd rather not post them)? Also, could you try and query the history on this directory from the gui client and see if it also truncates in the display there?
There's something really odd. The problem occurs on our build server, which has a dedicated user account to retrieve the files. This account has read-only access to the repository (with one exception, a file it is supposed to write to). When I issue the command with this account, on any client (also on my XP dev machine), I get the described behavior consistently. However, when I use my account with full access rights to issue the command, the problem disappears and the result is the same as in previous versions.