Updates failing (different reason)

Mar 26, 2008 at 3:36 PM
Hi,

Updates are probably the most sensitive thing right now for me. I get different errors each time I do a fresh checkout and then try to update afterwards. For example, I did a fresh checkout of a project of mine to "C:\IT\vfx\crusades". Note that I checked out at an earlier revison (and not HEAD) so that after the checkout was complete I would be able to perform updates and receive changes.

Updates will download SOME files, but fail somewhere down the list of downloaded files. Now during my second update, I'm getting the following error message from TortoiseSVN:

Update
Directory 'C:\IT\vfx\crusades\sfml' is missing
Directory 'C:\IT\vfx\crusades\sfml' is missing
Please execute the "Cleanup" command.

There was NEVER an 'sfml' directory in the 'crusades' directory. The only SFML directory is located at 'C:\IT\vfx\crusades\SDKs\sfml'. I think SVN Bridge might be getting paths confused? When I performed the update, I did it to the "C:\IT\vfx\Crusades" directory, so that the entire project would receive updates.

There is no information generated in any of the LOG files about this error. Every single time I try to update the root, this exact error occurs in TortoiseSVN.
Mar 26, 2008 at 7:14 PM
I am sorry that you are still having issues.
I am afraid that the information provides doesn't give me enough information to reproduce.
Can you create a codeplex project and try to reproduce your issues there? That will allow me to test against that.
Mar 27, 2008 at 2:58 AM
One thing you can try that I've seen cause strange issues before, is when you do your checkout in TortoiseSVN, make sure the capitalization of the project name is correct. For example, a checkout of http://localhost:8081/SvnBridge should work fine, but http://localhost:8081/svnbridge might have some abnormal behavior.
Mar 27, 2008 at 1:49 PM

jwanagel wrote:
One thing you can try that I've seen cause strange issues before, is when you do your checkout in TortoiseSVN, make sure the capitalization of the project name is correct. For example, a checkout of http://localhost:8081/SvnBridge should work fine, but http://localhost:8081/svnbridge might have some abnormal behavior.


Why does that seem horribly broken to me? I'll check my stored URL when I get to work to see if I have caps issues.
Mar 27, 2008 at 2:12 PM
Okay, I'm starting to get failures now, and here's what I did:

1) Do a fresh checkout at revision 1282 (this requires not checking out HEAD, but a specific, earlier revision)
2) Perform an update (Update to HEAD) on the root checkout. TortoiseSVN reports for me: "OPTIONS of 'http://localhost:8081/SvnBridgeTest': 500 InternalServerError (http://localhost:8081)"

The .log file for this error message is far too long to paste here, if you guys could give me an email address to send these to I would appreciate it. My email address is mrdoommaster@gmail.com, send me an email there (so I know your email address) and I'll reply with the error log for this specific issue.

Note that this is not an issue I've run into before, each repository yields its own set of random error messages, unfortunately.

The information needed to connect to my test TFS (CodePlex) project is below:
Homepage: http://www.codeplex.com/SvnBridgeTest
Project Name: SvnBridgeTest
Server Name: tfs07.codeplex.com
Port number: 443
Protocol: https

NOTE: Be sure to use the steps I outlined above to reproduce the issues during an update.

      • Email me at mrdoommaster@gmail.com if you want the username/account on the project for testing purposes ***
Mar 27, 2008 at 2:25 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Mar 27, 2008 at 9:17 PM
Okay, I can't reproduce because it takes too long to compute the change set require :-)
The issue is that you have a lot of changes in between, which is requiring trips to the server, which takes time
Working on that for now, we will see if this will affect the way it behaves.
Mar 27, 2008 at 9:59 PM
When you say you're "working on it", does that mean you have a solution, or that you're just going to try some things? In other words, do you even have a solution at all?

By the way, thanks for looking into this for me. Let me know if I can help with anything else.
Mar 28, 2008 at 1:56 AM
Working on it means that I think that I have a solution, but it is a big change, which will take a while.
I am committing the first part one, but it is not used in the app yet, and won't be until I finish this.
Apr 9, 2008 at 12:41 AM
FYI, this should be fixed now.