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]
KDE still not updated
Something must be really wrong in your crawler algorithms, KDE is still not updated in 7 months sigh
FYI: I have checked ALL our code location repositories myself, they are ALL accessible, but there is still no update?
Also: how is it possible that one single code location failing (btw, git://anongit.kde.org/calligra works perfectly fine, just checked again for about the 10th time, so something is wrong on your side, really) blocks the complete project to be updated? How about adapting your code to prevent this? Doesn't make sense that a very active project with over 500 active contributors and over 22M lines of code just doesn't update in more than half a year...
I sent a mail 3 days ago after over a months of no news to [email protected] , again no news...
ping?
Hi Mamarok;
Sorry for the delay. The problem was indeed on our side. We've rescheduled the job for the problem repository and will be monitoring it.
Thanks for coming back to me, Peter. How long do we have to wait for this problem to be resolved? I have the same problem with the Amarok project, and I can reach the git repository without any problems. Ditto for the Calligra repo in KDE which your system still says is not reachable as of today.
I've been asked to comment here. In regards to KDE Infrastructure, we do impose connection limits of 5 connections per IP address per anongit host (of which there are two) on the anongit.kde.org network. When these limits are reached all further connections will fail with a connection reset error until you fall under the limit again.
You can reproduce this locally by setting per_source = 5 in a xinetd service statement and running your indexer against that.
Other than that we don't impose any other blocks on git:// protocol access to our repositories. Please ensure you are trying to access it via git://anongit.kde.org/ though (as http://anongit.kde.org/ is much slower and server resource intensive on our side).
Thanks,
Ben
KDE Sysadmin
Hi Mamarok;
We got the analysis completed. Yes, one blocked repository will block the analysis job from starting. However, we are able to get to through [calligra|https://www.openhub.net/p/kde/enlistments?query=call&sort=by_url] repository. The problem was temporary, but hadn't gotten automatically cleared.
Thanks for the information, bcooksley. I check the 364 repositories in the KDE project for any that start with http://
and didn't find any.
I do appreciate your time in bringing these issues to our attention and apologize for the delay in getting things resolved.
Hi Peter: thank you very much, it indeed completed the job now.
I was wondering: currently we have only about 360 of our ~800 mainline repos indexed. Is there another way to get those in than adding each one manually?
Please note that the same applies to all projects under the KDE organization. Could you please schedule an update for them as well, and apply the same settings for them?
