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]
Grid Solutions Framework Source Code Download Fails
Not exactly sure the issue here, but it's been going on for a long time (months). I've tried to get CodePlex to fix - they seem to think it's OK, but maybe Ohloh is not reading the data properly?
- Ohloh site: https://www.ohloh.net/p/gsf
- Main open source site: https://gsf.codeplex.com/
- SVN repository URL: https://gsf.svn.codeplex.com/svn/
Any help would certainly be appreciated.
Thanks,
Ritchie
Ritchie,
First up, Codeplex's subversion interface is an elegant hack
which exposes Team Foundation Server to the world read-only as if it was subversion. It isn't a one-for-one perfect emulation and sometimes it fails under the relentless pummelling it gets from ohloh. (I show at least 15 projects in the same boat today.) I'm trying the same command which fails here on my workstation and I get the same response. We haven't found a work-around so far. You may (but are not certain to) have better luck with their git-style repository. Let me know...
Thanks!
Great news! For what ever magical reason - SVN is now operational for the Grid Solutions Framework project.
Curiously though, only last year's commits are showing up on Ohloh even I can see the latest updates in TortoiseSVN?
Maybe it just needs a swift kick?
Thanks for any help.
Ritchie
Ritchie,
I gave it a couple of kicks but I'm not getting any closer than before. Unfortunately TortoiseSVN isn't like real-world subversion and I wonder if they fine-tuned the elegant hack
to work better with a GUI than it does with cranky old command-line subversion??? I'll take another look once I have a breather.
Keep pinging me here if it seems to take too long.
Thanks!
Ritchie,
The log I got from the subversion starts with r81747 (2012-12-14) and ends with r91307 (2014-08-27). This is a lot different than what we have in the project. I may do a little experiment (outside your project) and report back with any findings.
Steve
Thanks! I am glad you see more recent check-ins - sounds like progress...
Ritchie,
There is very little latitude in how to enlist a Codeplex subversion. With most subversions you have choices of transport: http:, https: and svn: but not so in this case. The only way to have independent enlistments (it turns out) is to include or exclude the final slash in the URL. That's not exactly intuitive, but it does seem to create a separate enlistment. It looks as if today it will retrieve 110 commits. We'll see as we go along if that holds and how the dates for those 110 commits shake out compared to the ones you show in your current project. Standby.
Thanks!
Ritchie,
With an independent enlistment from that of your project, I got the exact same results (I think). I have commits from 2012-09-14 (r79872) to 2012-12-07 (r81704).
I have gotten a log from the repository which shows commits from 2012-09-14 (r79872) through 2012-12-07 (r81704) and another from 2014-09-21 (r91437) back to 2012-12-14 (r81747). It seems to depend on which direction you request. I also notice the logs are extremely verbose with the list of all the files affected in the log. I wonder if all that text is somehow causing a timeout? Perhaps a memory clog?
Hmmm.
FYI - we were able to solve this issue (sort of anyway). Using git-tfs (https://github.com/git-tfs/git-tfs) to clone the CodePlex TFS project (with history) to GitHub (technically we went from CodePlex to local Git to GitHub - but it may work directly to GitHub). Once the code and history was there, I then changed the OpenHub code location to point to the GitHub site and voilà!
I think we'll just leave this running in a daily push to GitHub to keep OpenHub stats updated properly. We are going to do the same for our other troublesome CodePlex site (openHistorian) - the others seem to work fine.
Anyway, wanted to pass this along as a possible solution for others who may be having trouble with this.
Thanks!
Ritchie
Ritchie,
So pleased to hear it. Hope anybody that's having similar problems gives this suggestion a try!
Thanks!