Forums : Technical Issue Help
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.synopsys.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
Step 1 of 3: Downloading source code history (Failed)
Hi!
I'm maintaining the serendipity enlisting, and added svn://svn.berlios.de/serendipity/trunk
as a SVN repository. But it fails with this message:
Step 1 of 3: Downloading source code history (Failed)
Even though with my SVN client I can access the address mentioned above just fine....?
Best regards,
Garvin
Hi Garvin,
Our connection to berlios is sometimes flaky - which I suspect is the problem we encountered. I've rescheduled the download and will track it's progress.
Hi Jason!
Thanks a lot for your kind response.In the interface it still tells me about download failed, so I suppose the rescheduling is invisible to me?
Best regards,
Garvin
Yeah - we have a job queue that's currently hidden from the general view. We'd like to expose it but we'd probably need to explain it properly first. It's on our feature list somewhere but pretty low-priority at this point.
Hi Jason!
Any news on this? The enlistment sadly has not changed yet...
Regards,
Garvin
I see the same status on project DrJava, with repo URL https://svn.sourceforge.net/svnroot/drjava/trunk/. Any Idea what might be going on here? I've actually tried deleting and resubmitting the enlistment, but I get the same results.
Thanks, Alex
Hi prat,
Yes, I have been investigating the problem with DrJava. It looks like the subversion repository may contain some corrupt data, because the log shows some illegal characters in the comment for a checkin on 2005-04-30, which broke our parser. I've fixed our code to clean up the comment, and have resubmitted the job.
BTW, removing and re-adding the enlistment should have no effect. We keep only a single copy of the enlistment data, no matter how many times it is added to or removed from any number of projects.
Robin
Hi robin!
Any chance that such a commint log entry also causes problem for the Serendipity reimport? Because nothing has changed yet :(
Best regards,
Garvin
Hi garvin,
Sorry, our system has been really slammed for the last week ... some of our hardware failed at about the same the our site started to really pick up on traffic. Our new hardware has just arrived, which will greatly increase our analysis capacity. We'll get it set up later today, and then we can start feeding the failed jobs through the system again.
Thanks for your patience garvin,
Robin
Hi garvin,
I've been investigating the troubles with serendipity, and it looks like there is some problem at revision 1342. Try the following command in a clean directory:
svn checkout svn://svn.berlios.de/serendipity/trunk@1342 -r1342 serendipity
I expect you'll see the following error:
svn: Invalid diff stream: [tgt] insn 335 starts beyond the target view position
I'm still investigating what might be causing this error, but I wanted to let you know why we're having trouble.
Robin
Hi Robin!
Sorry for tuning in later here.
I just checked, and at least I can view this revision using viewSVN:
http://svn.berlios.de/viewcvs/serendipity?rev=1342&view=rev
However the checkout you mention really does not work for me. Seems as if the repository is garbaged at that revision - sadly we're hosted on BerliOS, and their support is known to be non-existant, so I expect no help in this issue.
Is there anyway in your system to skip errors like that and just continue with the next revision? Or, if you happen to know something that I with SVN write access can fix in the repository, please let me know?
Your help is much apprecaited!
Best regards,
Garvin
Checking out Crystal Space failed as well (see http://ohloh.net/projects/3761/enlistments). The source code is fairly big and we experienced checkout troubles in the fast as well. (It's SourceForge's fault - they state that their load balancing mechanism is the cause, in some bug report on the frequent SVN issues.) The checkout apparently never succeeds on the first try. The workaround is to perpetually svn update
until that succeeds (and the repository path is completely fetched).
Although in this particular case (Crystal Space) there exists an SVN mirror that doesn't have the problem: http://crystalspace3d.org/svn/crystal/CS/trunk/ . On the one hand it's easier for me to just enlist that. On the other hand, SourceForge SVN has issues in general, so maybe you need some workaround for it anyway...
Hope that helps,
-f.r.
Hi res,
SourceForge failures are nothing new around here. I saw the troubles with Crystal Space, and with some simple retries on our end it seems to be going through now. I'll keep an eye on it today. It might be interesting to try the mirror, but we're getting pretty good at coaxing code out of SourceForge.
Thanks,
Robin
I've been getting this as well with MelonRPM (3401, I think). It just needs a good kicking to try again, I think- we had some SVN downtime but that's all fixed now, just want to get this updated :p
Cheers.
