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.blackduck.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 2 days ago.)
Step 1 of 3: Downloading source code history (Failed 2 days ago.)
https://www.ohloh.net/p/vbsas
https://github.com/phpkd/vbsas
What a great customer support! No reply for a problem occured 5 days ago, and reported 3 days ago..!! Thank you!!!
Abdelrahman,
We aim to please (but sometimes our aim is off...)
I am working on it but I've run into an unexpected error.
Please ping me here if I don't respond in a timely manner.
(Software bugs are stubborn and don't respond to bug spray...)
Thanks!
Looking forward for you genius resolution, I've always respected how Black Duck
do business, so please don't disappoint me..
Just FYI, I've tried to delete code location, re-add it, remove the whole project & re-add it, but all was hopeless, same failed result! I hope you fix it.. Thank you
Abdelrahman,
Removing the code location often doesn't help since ohloh has the memory of an elephant and you're back where you started. Only trick is to alter the address for the enlistment slightly and it will treat it as a new enlistment.
For example: substitute https: for git: in the URL if that will work. Often it doesn't but???
Eventually management will catch on and fix that back-door...
In the meantime, I'll keep at it.
Thanks!
Abdelrahman,
Looks as if you've already figured that one out...
Thanks!
No, it's NOT!
Step 1 of 3: Downloading source code history (Failed 7 minutes ago.)
Approximately 8 days until now without any solution, any hope?!
https://www.ohloh.net/p/12131/enlistments
https://www.ohloh.net/p/mrc/enlistments
https://www.ohloh.net/p/oink/enlistments
all of them is (Failed over 2 years ago.)
and never retry again even i just re-add the source
Xuefer,
It's odd... All three failed about 850 days ago for the same reason: Subversion returned an error message in Chinese for all three. This confused the heck out of our systems. (If you want I can send you a copy of the error.) (Translated: svn: File System Module
fsfsversion mismatch: found 1.6.15, 1.6.16 expected
.)
Rescheduled all three updates. All three finished OK (taCo=46 added commits, mrc=6 added commits, oink=6 added commits.) Analysis is now at August 30, 2013 on code collected on August 30, 2013 and last commits are at August 03, 2013, June 27, 2012 and November 12, 2012 respectively.
Please remind me here if the project goes astray again.
Thanks!
Abdelrahman,
Just tried to re-fetch the enlistment with the same error. Need to have someone in engineering observe the interaction between our system and GitHub's to determine the cause for failure. I understand it may be a problem with an older version of git running on our servers here. We are performing acceptance testing on a newer version before deploying it to the systems.
Standby.
Thanks!
Please do so as soon as possible & let me know results.
It's just a normal public github repo, and I've already 20 other github repos linked to ohloh without any issue!
Is there an ETA for any expected resolution?
Abdelrahman,
That's the odd thing about this... We have a metric ton of GitHub enlistments that go through day-to-day without any errors at all. The ones that do fail don't seem to have any common thread except that the failure is persistent. It's more than a little annoying.
Thanks!
Any updates?!
Step 1 of 3: Downloading source code history (Failed 9 days ago.)
Step 1 of 3: Downloading source code history (Failed 14 days ago.)
Any serious support there?!!
Abdelrahman,
Sorry it took so long but another failure (in another project) suggested the fix for this one. Fetched the enlistment with a git: transport which finished OK (22 total commits). Analysis is now at December 16, 2013 on code collected on December 16, 2013 and last commit is at September 26, 2013 (confirmed with web interface).
Please tell me here if the project stumbles again.
Thanks!