Topic: Related projects - some projects are ...
Related projects - some projects are grouped together by common theme or developers, be handy to be able to indicate that a collection of projects are part of the one group.
Related projects - some projects are grouped together by common theme or developers, be handy to be able to indicate that a collection of projects are part of the one group.
Any chance of getting OpenSim (4753) enrolled in this beta downloader? (We are missing most of our revision history due to us doing some development in branches and moving it back)
Very awesome. :)
Hi -
it would be great if we could embed the Ohloh charts (eg code makeup, LOC over time, etc) onto our project website's "about" page, is it possible to static link these?
Thanks
Adam
Woot! You guys are awesome.
Thought I'd give it another prod since it's been 17 days since the last updates (just want to make sure there's nothing busted on our end) - is the timer just running 'whenever' in a complete loop?
heh no problems.
Hrrm, been 11 days since the openmetaverse projects have updated - anything we need to fix?
Can the CodeBase History scale be shortened to start at the first commit to the last commit (rather than the 5 year view that is is now)?
Just a side question - how often does ohloh attempt to resync?
Alright, incase google ever trawls this thread - that was the problem. It appears that the number of connections ohloh was making was exceeding the inetd limits which was causing SVN connections to be terminated until the number of connections had been reduced through timeout. We increased the maximum number of connections from the default to a fairly healthy amount which seems to have caused the problem to go away.
We think we've found the problem. We are running svn via inetd and inetd has been throwing the error "svn/tcp server failing (looping), service terminated" during the times when ohloh attempts to connect.
Doing some googling returned some sparse results ( http://www.cenqua.com/forums/thread.jspa?messageID=12436 ) which indicated it was caused by a large number of connections in a short period of time - causing the service to deliberately kill new attempts until some had freed - so what I'm doing is I'm upping that to a larger number of simultaneous connections, and we will try again and see if it works.
Still having this problem, I enlisted the new name of the server which advanced it by another week, but it looks like it's cutting out.
Any ideas I can take to the server admin?