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]
Castle project enlistments
Hi admins,
The enlistments on the Castle project ( https://www.ohloh.net/p/castleproject/enlistments ) haven't been updated for several months, and a couple of them have failed.
Cheers and keep up the good work
Hi Mauricio,
your repositories should be up-to-date again. Sorry for the inconvenience. Please let us know if you notice anything else that needs our attention.
Best regards,
Patrick
Unfortunately, it seems ohloh can't detect which revisions are the same subversion revisions in the history since the repositories were split. I am not sure if this is what is causing the stupid LOC count, but it is definitely broken.
https://www.ohloh.net/p/castleproject/analyses/latest
Bump. Any idea why the LOC count is broken?
Bump! This is still broken... maybe rebuilding the whole stats somehow from scratch?
Cheers
Mauricio:
The project stats do not update unless Ohloh is able to successfully contact ALL enlistments.
The enlistment git://github.com/castleproject/Castle.Components.DictionaryAdapter.git master
is failing.
I checked github and it appears that that project doesn't exist.
If it no longer exists I suggest deleting that enlistment in order to allow the project stats to update correctly.
OK. I have removed the DictionaryAdapter enlistment since it was merged into Core, and replaced the broken IOC one with Windsor now that it was renamed.
After waiting about 5 hours ago since all the enlistments were fully updated the codebase still reports at -1.9m. Is there a batch process that will fix this?
Thanks, Jono
Jonathon, ohloh visits every repository in a cycle, once it visits yours again it should be up to date.
Robert, how often does it usually take for the process to make its rounds?
Jonathon:
Originally Ohloh did this every 24 hours or so. Over the past few months it's gotten slower and now it does it every couple days.
I see your enlistments were scraped about 14 hours ago, but the number of lines still reads negative 1.9 million.
This is probably not something that will fix itself. Ohloh has a bug where when an identical text operation appears on two branches and then later those branches are merged, Ohloh doesn't reconcile these and counts the line count deltas twice. This is almost certainly why your line count is messed up.
We know why it happens and we have three different ways to fix it which we are currently evaluating.
It's one of the 'bigger' problems that we here are tackling and as such it'll likely be a while until it get solved as the fix is involved (switching ohloh from a linear commit history to a DAG commit model)
I've added this forum post and your project to the bug that we have that tracks this problem.
When we are fixing it we will be using your project data as an example to ensure that we've fixed it correctly.
I'll update this forum post when it's corrected.
Sorry I don't have better news, we're very busy getting up to speed on how all of Ohloh functions and performing the upcoming server migrations.
Many thanks Robert for the technical detail about why this is broken. We are happy to wait until it is fixed, now that we know it is out of our hands.
Thanks again, Jono