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]
Pike project database corrupted?
For the Pike project, there intially was a download which stopped with an error. Then I added a new enlistment, which resulted in an empty entry with no code. Could it be a problem with ohcount since support for the Pike language has been added just recently?
Or could it be that your git importer dislikes
[repack]
UseDeltaBaseOffset = true
?
Hi Stephen,
There doesn't appear to be any errors in the report... the problem is simply that Ohloh didn't understand Pike until Friday.
Any code counted before then won't show any Pike. I'll schedule this project for a complete recount. Let me know if there is still a problem after the new report.
Thanks,
Robin
The recount worked.
Could you schedule Chilimoon
for a recount as well, as it is written mostly in Pike.
Also, a recount for Caudium
is in order, except, I noticed that Caudium is mixing two branches from the repository (master and caudium), where it should only be using the branch caudium
(the repository is shared between Roxen, Caudium and Chilimoon, since they have common roots). I'm not quite sure where this cross-branch pollution is coming from, it definitely is not in the repository, so it must be your importer being too eager or something.
Hi Stephen,
I've scheduled new counts for both Chilimoon and Caudium.
I believe the branch mixing was caused by a bug in Ohloh which we fixed just a few days ago. I haven't investigated this case closely but it looks like the some problem. Because the bug is now fixed, the recount should clean up the branching.
Again, let me know if anything still looks wrong after the recounts.
Thanks,
Robin