Forums : Posts

Glad to have helped you find your work! It looks like one part of our UI was confusing. You can always create a new position for any project, even if it has an enlistment, but going to your profile page and hitting NEW POSITION.

That should probably also be opt-out :-).

I've rescheduled the update. There are many types of errors that require manual rescheduling, but there are a lot of errors that our system will automatically re-attempt after a delay. Over time, we ... [More] are slowly expanding the number of error types that we automatically reschedule. Going forward, you won't see as much of the give up forever behavior as before. This particular job failed because of a permissions failure, which is something we don't currently auto-retry. I'll keep an eye on it. Thanks, Robin [Less]

Ah, Thanks, that's what I have been looking for. Now a chart with a time axis like that one: http://www.ohloh.net/projects/xx/analyses/latest would also be great. But I guess I'll just wait until ... [More] the missing link is restored, perhaps something else is hidden. -Samuel [Less]

Hi mithro, It took me a long time to check out all 41 repositories, but the mystery is pretty simply solved. Sloccount ignores configure files, while Ohcount counts them as a shell scripts. Since ... [More] tpserver-cpp is redundantly included in the Ohloh report four separate times, once for four different branches, Ohloh is counting the code in this directory four times over, which really adds up to a lot of configure files. In general, the list of code at http://www.thousandparsec.net/tp/dev/sloc.php only lists about half of the code listed on Ohloh, so there is a great deal of code that Ohloh is counting (or overcounting in the case of multiple branches) that the sloc.php page does not report. This makes direct comparisons basically impossible. Ohcount does have special language categories for autoconf and automake, and it categorizes files like configure.in as autoconf files instead of shell scripts. I'm not sure why we count the configure file itself as shell script -- it seems to me that we should count it as an autoconf file. Our make/automake/autoconf support was contributed by ciaranm -- Ciaran, any chance you are looking at this thread and can offer an opinion on this? Unless someone objects, I'm sort of inclined to remove configure from the shell script category and label it as autoconf. You can download our line counting tool Ohcount from http://labs.ohloh.net to answer these kinds of questions -- it can give detailed counts, and identify files by language -- you can pretty rapidly find out where the shell script content is coming from. Thanks, Robin [Less]

@robin - thanks for looking into this, and for your helpful response. Please do post an update if you ever add this capability. If I ever have the time and/or inclination to do something like what ... [More] you suggest (which sounds reasonable), I'll let you know how I make out. Richard [Less]

re: Compiz - ran into the same problem we saw earlier; our git importer can't handle out of sequence commits. For now we have to reschedule these failures by hand. Luckily the reimport is fairly ... [More] fast. The Warzone download is still making progress, so far it seems like a better enlistment. [Less]

Yes I've just seen the code. Thanks very much for your help. At all in the future wrappers will be removed from syx. Thanks again.

Thanks for noticing this Tero. It is the same problem. svn info -r HEAD --no-auth-cache 'svn://svn.gna.org/svn/ahven/trunk@HEAD' failed: svn: Malformed network data

Hi flux, This job completed about 12 hours ago. Generally jobs finish in a few hours but can take longer if our system is busy or the project has many changes to process.