Stream: implementers
Topic: check out failing
Craig Newman (Dec 04 2017 at 13:57):
Is anyone else seeing an error when doing an SVN check out?
I'm getting an error of:
ra-serf: The server sent a truncated HTTP response body.
Lloyd McKenzie (Dec 04 2017 at 14:20):
Yes. We're working on getting it fixed. In the meantime, do an SVN cleanup and an SVN up
Craig Newman (Dec 06 2017 at 19:08):
Any update on this? The load is still failing and the clean up fails too. Thanks
Lloyd McKenzie (Dec 06 2017 at 19:22):
HQ is working on the issue with @Andy Stechishin. The current theory is that the issue is caused with new SVN clients and can only be fixed by upgrading gForge's SVN libraries which will take some time due to testing. I don't yet have an ETA for a fix :( If you wished, you could try experimenting with an alternate/older SVN client and see if that works better.
Craig Newman (Dec 06 2017 at 19:36):
I haven't changed my SVN client lately. I'm using TortoiseSVN now. Is there an alternative?
Lloyd McKenzie (Dec 06 2017 at 22:05):
There are alternatives. I don't know if there's another one that will work better.
John Moehrke (Dec 06 2017 at 22:08):
Yesterday I had to totally kill my whole FHIR directory, and start with a fresh checkout, followed by aditional cleanup and override and administrative scary things... all things that my tortoiseSVN walked me through.
Vadim Peretokin (Dec 07 2017 at 12:38):
So when are we migrating to a version control system that fails less?
Michel Rutten (Dec 07 2017 at 15:34):
I also get the "truncated HTTP response body" message. I noticed that by using the Clean command, I can continue the check out process.
Craig Newman (Dec 08 2017 at 15:23):
Now the SVN commit is failing. I'm being told that the immunization-speadsheet.xml file has a status of conflicted. The SVN tool tried to fix the conflict but all it seemed to do was render the file corrupt (I can't open it in Excel anymore). Anyone have thoughts on how to resolve the conflict? Thanks.
Eric Haas (Dec 08 2017 at 15:29):
conflicts in excel are tricky. you can try to hand edit in xml. (which is tricky because there is a lot of of crap in excel xml) or revert and renter your changes into the excel file. The spreadsheet.txt file is handy to see what you changes were if you can't remember and that is tracked by Travis
Craig Newman (Dec 08 2017 at 15:33):
I was afraid you'd say that I'd have to start again...
Lloyd McKenzie (Dec 09 2017 at 00:18):
You can use SVN show log to see who also changed things and find out what they did. Typically you need to start from one of your versions and re-apply the other person's changes. So the first step is to figure out which starting point is going to result in the least work.
Last updated: Apr 12 2022 at 19:14 UTC
