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
info@openhub.net
Hi, for some reason the first 1,314 commits aren't showing up for the Ubiquity Browser Extensions project:
http://www.ohloh.net/p/ubiquitybx/commits?page=3
We recently moved this repository from its old home using svnsync, but I double-checked that ohloh was resyncing okay after I updated the details (and it was), so that may not be significant.
Any ideas?
Hi Phil,
Unfortunately, Ohloh is unable to follow directory moves within a Subversion repository.
The current /trunk directory did not exist before revision 1311. From looking at the log, it appears that content was then moved from other branches into the /trunk.
Since Ohloh can't follow these moves, from Ohloh's perspective it looks as if the project was begun at revision 1311.
I don't think there is any workaround for this; it's going to require a bug fix on our end.
Thanks,
Robin
Huh... thanks for that Robin, it makes sense. The thing is though, and I'm not discounting personal insanity as the cause of what I'm about to say here, but I'm sure that I've seen these commits show up on ohloh before now (before we svnsynced, I mean). What's with that? Am I mental? For instance, I thought I saw the commits for my profile go down by like a thousand or something a few weeks ago. Was there no identifiable event that would have caused that? Or maybe this crack I've been smoking has started to have an effect on me after all?
Hi Phil --
It's not the drugs. I dug through some old logs of our reports, and we did have all of the old commits once upon a time.
Here's what happened, in painful detail.
Back in the olden days, Ohloh downloaded the whole Subversion history for the project. Every few days, we'd pull the latest few commits, and incrementally add them onto our report. We got up to revision 1308 this way.
Then revision 1311 occurred, creating a discontinuity in the /trunk
history. A few more commits got created, getting the repository up to rev 1313.
A few days later, Ohloh showed up to ask for the latest commits. At this point, Ohloh was unable to see anything before 1311, so we only got 1311, 1312, 1313. So now we're missing commits 1309 and 1310, but no one noticed.
Life pretty much continued as normal for a while. As new commits came in, they were tacked onto the end of our existing report.
Then the hammer fell. Either because of a bug fix, data loss, or some other problem, Ohloh had to recalculate the report from scratch. I'm not sure what the reason was, but it required us to throw away the report and create a full clean one. Now the discontinuity at 1311 is painfully obvious, because Ohloh no longer has any way to read the old commits, and the new report comes up short a thousand commits.
The frustrating thing is that the 1310 commits are sitting right there in the repository for us to process, if only we could write some code to recognize and work around the discontinuity. But so much code, so little time. I do hope to get to this soon.
I hope this rambling explanation makes some kind of sense!
Robin
Hi Robin, no probs and thanks for taking the time to go into detail. I assume that your point 'v' occurred when we svnsynced the repository to Google Code and updated the enlistment details over here. It's no biggie though. You guys have done a great job on this site btw.