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]

Commits from merges does not count to project activity

https://www.openhub.net/p/RapidClipse/enlistments

The project RapidClipse recently merged all their year-old git repositories into one.
I you look at the direct commits to the repository 1 you see only 2 recent commits - this seems what OpenHub uses as it shows new project and the Project Summary shows no commits in the graphical view.
If you look at the commits directly you see 639 commits, 17 in the last 30 days.

Is there a way to fix this counting? (I plan to do the same for another project that is on OpenHub, this would be interesting to know...)

Simon Sobisch about 7 years ago
 

Hi Simon;

Hmm, interesting. Sure looks like something isn't right on our side even though the repository was processed without errors.

I just tried it again to see it myself. But it still didn't generate what we expected. I'll open a ticket so that we can explore this in greater detail.

Peter Degen-Por... about 7 years ago
 

Any update?

Simon Sobisch about 7 years ago
 

Helllo Simon,

After doing a deep dive into Git, we identified, it looks like an issue with the data itself, the initial commit was made recently and the other (merge) commits and not taken into consideration, as it is back dated from the initial commit. This as per the OpenHub(OhlohScm) architecture.

In other words, OhlohSCM uses --first-parent for getting the first commit date. Only commits that are in master’s --first-parent history are taken into analysis. This allows us to keep and maintain a linear history.

Hope this helps!

Anonymous Coward about 7 years ago
 

Hi rapbhan,

while this helps to explain the current analysis data it shows one mayor issue with OhlohSCM: The history of branches is simply missing (Summary, language summary).
Actually I don't understand this as the analysis data on contributors page is correct - is this a different algorithm that cannot be used for the other analysis parts?

Simon

Simon Sobisch about 7 years ago
 

Hello Simon,

Yes, for the charting purposes it looks for the first initial commit and from there to get the linear history of the commits and thats why the chart is empty(and so few analysis).

Hope this answers your question.

Thank you!

Anonymous Coward about 7 years ago
 

raphan, wouldn't it be more reasonable to do the following:

1 get first initial commit
2 if any merge is found which creates new files/folders: store merge origin for later reference
3 when the current working thread is finishing use the first reference as new working thread, go to 1

This way OhlohSCM would be fixed for scenarios where different parts are merged into one repository, something that is not that uncommon.

Simon Sobisch about 7 years ago