mipi3 Posted July 26, 2012 Report Share Posted July 26, 2012 Hello, we have a problem with one workspace which has several xlinked repositories placed in subfolders. These xlinks, when observed from Items, somehow have type Directory now. Other xlinks that are placed in the root directory looks as they shood - with Type xlink and no problem with them. But weird thing is when we use another workspace of the same repository xlinks are OK there. Maybe the consequence of this weirdness is that when we try to checkin changed items under these xlinks we receive error message with 'item 2 could not be found in the tree. The new tree cannot be built'. The same checkin from healthy workspace works without problems. We use 4.1.10.320 - Santiago version (client and server) Link to comment Share on other sites More sharing options...
manu Posted July 26, 2012 Report Share Posted July 26, 2012 Hello mipi3, it seems that the workspace is somehow corrupted, can you please try the following: 1) Create a new workspace in the machine and update -> Tell me if the xlinks are xlinks. 2) Browse the last changeset you are using -> Tell me if xlinks are shown as xlinks. 3) Manually, from the Windows explorer, remove one of the "corrupted" xlink directories, the pending changes view will recognize it as a "Manually deleted item". Select it and undo the change -> Tell me if it's recreated as an Xlink. Link to comment Share on other sites More sharing options...
mipi3 Posted July 27, 2012 Author Report Share Posted July 27, 2012 1) Create a new workspace in the machine and update -> Tell me if the xlinks are xlinks. Yes xlinks are xlinks there. 2) Browse the last changeset you are using -> Tell me if xlinks are shown as xlinks. from currupted workspace the change of current changeset does not help. The same corrupted xlink here. 3) Manually, from the Windows explorer, remove one of the "corrupted" xlink directories, the pending changes view will recognize it as a "Manually deleted item". Select it and undo the change -> Tell me if it's recreated as an Xlink. No. It was recreated as binary file... I opened it in binary, noticed PNG string, added extension PNG. And hey It was one of many PNG file from the root repository (!!) 89 50 4e 47 0d 0a 1a 0a 00 00 00 0d 49 48 44 52 00 00 00 28 00 00 00 28 08 06 00 00 00 8c fe b8 6d 00 00 00 c4 49 44 41 54 58 85 ed d7 5d 0a 83 30 18 44 d1 db 2c 20 8b cb fe 57 91 0d d4 17 0b 69 9a 5f a3 64 28 df 3c 8a 0c 47 41 c3 bc 42 08 6f b2 c4 18 f3 4b 3f f1 de 77 ef b9 a3 cf dd 59 56 ca 6a df 17 50 0d 07 09 50 11 07 27 50 15 07 e0 94 71 50 f8 48 56 ca 9e 78 d8 26 70 37 0e 1a 6f 50 01 07 15 a0 0a 0e 0a 40 25 1c 64 40 35 1c 24 40 45 1c 9c 40 55 1c 80 53 c6 c1 c0 8f 7a a6 ec 89 87 1d 02 ee 3c 0e bb c0 dd 67 75 13 b8 1b 07 0d a0 02 0e 2a 40 15 1c d8 26 b1 4d 32 57 f6 89 6d 92 ab 65 b6 49 56 cb 5a b1 4d 32 52 56 8a 6d 92 99 b2 34 b6 49 ae 94 81 6d 92 b5 b2 d1 d8 26 a9 95 f5 f2 97 9b e4 00 28 d7 f2 45 74 d3 8f f4 00 00 00 00 49 45 4e 44 ae 42 60 82 And when I pressed update 'Update operation report' window popped up with error on this xlink : 'Could not get revision information for [xlink dirPath]. You may be referencing non-existing item/branch/label. Or this ....'. The second update showed me the same window but with three errors now. The other were saying that item was loaded twice. It said that this binary is loaded in the root repository as png file and in xlink place. The next update doubled these warnings. Then I deleted again this broken xlink, undid the change, and it recreated as Directory again. Update didn't help some object reference exception appeared... so I broke my Workspace completely. Will use a new one. I didn't notice at what point in time this problem started. So I can't reproduce this problem. There is another minor bug, when plastic client loads and you press close button it crashes. Link to comment Share on other sites More sharing options...
manu Posted July 27, 2012 Report Share Posted July 27, 2012 Yep, I think the best option is delete that workspace and create a new one. If it happens again to you I can get connected to try to get more info, thanks for your help. There is another minor bug, when plastic client loads and you press close button it crashes. Good one! Thanks! Link to comment Share on other sites More sharing options...
mipi3 Posted August 2, 2012 Author Report Share Posted August 2, 2012 Hello, Yep, I think the best option is delete that workspace and create a new one. If it happens again to you I can get connected to try to get more info, thanks for your help. It happened again... Yesterday I upgraded to 4.1.10.326 - Liverpool. Maybe upgrade corrupted my workspace... Link to comment Share on other sites More sharing options...
mipi3 Posted August 2, 2012 Author Report Share Posted August 2, 2012 I see that the workspace corrupts at some point. We had some problems with checking in some xlinked file recently from another machine (error about revision that could not be found. 4.1.10.320 version there). We recreated workspace and the problem was solved. It seems that it would be good to have some tool maybe (command line?) to check workspace or fix it or recreate it... Link to comment Share on other sites More sharing options...
mipi3 Posted August 2, 2012 Author Report Share Posted August 2, 2012 Hmmm there is another problem. Maybe it is interconnected with this one somehow. When I open changesets I do not see all changesets but some last ones. I see all changesets in branch explorer. For example xlink references cs1 but I see only 17 and 16 cs from changesets list. Branch explorer however shows all changesets.... Something strange is going on here... Link to comment Share on other sites More sharing options...
anuar Posted August 3, 2012 Report Share Posted August 3, 2012 Hello mipi3, The problem you are having with the changeset view, is not really a problem. In Plastic, to avoid a huge list of changeset for big repositories, there is a filter so only most recent changeset are being showed. You can change this by clicking on the "Advanced" button at the top right of the view. You will see the text of the query used to show the changesets, something like: find changeset where date > 'some_date'. If you want to see all the changesets just write "find changeset" and every changeset will be displayed. About the other issue, if you if you want we can get connected on monday to try to solve it. Link to comment Share on other sites More sharing options...
Thuan.Do Posted July 9, 2014 Report Share Posted July 9, 2014 Sorry to bring this up, but can we add xlink as a subfolder inside our project yet ? Link to comment Share on other sites More sharing options...
manu Posted July 9, 2014 Report Share Posted July 9, 2014 Hi, you can have xlinks in any subdirectory of your root repository, what is not possible is to xlink a subdirectory of the target repository. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.