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]

#DeVIDE enlistment stuck at "Step 2 of 3: Importing source code into database (Failed) " (24 hours)

Hi there,

Since yesterday, the enlistment of the main #DeVIDE SVN repository ( http://devide.googlecode.com/svn/trunk ) is stuck at Step 2 of 3: Importing source code into database (Failed) It's now 24 hours since I added this enlistment.

Could you take a look at it?

Thanks!
cpbotha

Charl Botha over 15 years ago
 

Hi Charl,

There seems to be some trouble in this repository -- perhaps there is a corrupted file or some other issue.

We get an error when trying to get this file:

$ svn cat -r 2 'http://devide.googlecode.com/svn/trunk/devide/graph_editor.pyc@2'

The output is a lot of gibberish and finally:

svn: GET of '/svn/!svn/bc/2/trunk/devide/graph_editor.pyc': 200 OK (http://devide.googlecode.com)

This is not expected behavior :-). Do you know what is going on here? Are you able to fix/investigate?

Thanks,
Robin

Robin Luckey over 15 years ago
 

Thanks for looking into this!

Apparently I accidentally checked in that PYC file years ago, also with the svn:eol-style native property, hence the error you're seeing. Although I also removed that file a long time ago (it's a generated binary and should not go into SVN), it's obviously still in the history.

This is the discussion as it happen on googlecode: http://groups.google.com/group/google-code-hosting/browse_thread/thread/6ce6ba3bbc6d73fa

So, the history can't be changed. Is there anything else that can be done, except for just accepting that the DeVIDE repo can't be analysed?

Thanks again,
Charl

Charl Botha over 15 years ago
 

Hi Charl,

It's possible that I can manually skip this revision in our report. It's a bit tweaky but I might be able to make it happen. I'll look into it on Monday.

Thanks,
Robin

Robin Luckey over 15 years ago
 

Thank you very much!!

Charl Botha over 15 years ago
 

Hi Charl,

I was able to manually enter revisions 2 and 5 into our system, and the automated importer has picked up from there.

I'll keep an eye on it today, but unless there's more trouble, we should have a new report sometime today.

Thanks,
Robin

Robin Luckey over 15 years ago
 

Looks like I spoke too soon -- we just had another failure.

This time I get an Inconsistent line ending style error in revision 402:

svn cat -r 402 'http://devide.googlecode.com/svn/trunk/devide/modules/resources/python/slice3dVWRFrames.py@402'

Unfortunately, I can only reproduce the error on our local mirror of the repository, not against the original on Google. The original seems to work OK.

The only explanation I can come up with is that either our local mirror is corrupted, or this was a problem in the repository that has been fixed since we made our mirror.

Before I start over, do you know anything about this? Shall I just try again, or does this problem ring any bells?

Thanks,
Robin

Robin Luckey over 15 years ago
 

Thanks again for diagnosing this! It doesn't ring any bells, please start the import over.

Charl Botha over 15 years ago
 

Hi there!

Have you had time to take another look at this?

Thanks,
Charl

Charl Botha over 15 years ago
 

Me again. :) ohloh reports now that all 3 DeVIDE enlistments have gone through. However, it's clear from the commit history and the code analysis that only the two very small C++ enlistments have been analysed, and not the main Python enlistment. Should I give up on this?

Thanks again.

Charl Botha over 15 years ago
 

Sorry, Charl, I lost track of this. I've just started a clean download of the main enlistment and will keep an eye on it today. Hopefully we won't see the same error again.

Thanks,
Robin

Robin Luckey over 15 years ago