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]
clojure-mode SCM update failed 5 months ago and hasn't been tried again since then
The enlistment of clojure-mode (https://www.ohloh.net/p/clojure-mode) shows that the last update has failed 5 months ago, and it seems ohloh didn't try again since then.
I've checked the git URL, and it's correct. I've tried removing and adding it again, but that didn't help. How can I tell ohloh that it should try again?
Tassilo,
There are some tricks to it but let me look first and I'll report back in the morning Eastern US time and let you know what I find...
Thanks!
Tassilo,
Problem solved. Needed to start nearly fresh to clear a conflict which finished OK (504 total commits). An update started immediately and also finished OK (56 added commits). Analysis is now at May 31, 2013 on code collected on May 31, 2013 and last commit is at May 30, 2013 - about 11 hours ago.
Suggestions for self-help in case this happens again: First (and least troublesome if we do need to go back and diagnose an error later) is to add a nonsense ignore order by pressing the Edit ignored files
button on the enlistments page. Select one file or a class of files that we don't process anyway like an image file to ignore. This will force a re-analysis and may solve the problem. Please document what you've done and observe what change, if any, it makes, and be patient. Sometimes it may take hours to process. Second, try enlisting the same repository a different way; for example, if you use a git repository, try enlisting it as git://blahblahblah or, if it's available, try https://blahblahblah which ohloh interprets as a different repository entirely. Again, document what you tried and watch the results. This way, we can un-thread the needle should we need to later.
Thanks!
Ok, thank you!