Clean clone in progress :-)

Hmm, you're right, and this is a bit of a surprise to me -- I can't think of any technical reason why logout should require Javascript. However, the Ohloh website operates under the blanket ... [More] assumption that Javascript is enabled on the browser. We never test anything with Javascript turned off, and generally don't support that scenario. [Less]

Ohloh uses the wiki collaboration model. Anyone can edit just about anything on the website. To avoid catastrophe, we also have an Undo feature. I've reverted the Firebug logo -- thanks for confessing :-). Robin

Hi Tim, Unfortunately, our Bazaar adapter has some bugs related to incremental updates. Often, after pulling recent changes, we are unable to cleanly update our analyses. Our workaround is to perform ... [More] a full clean analysis of these projects. For small repositories, this is annoying, but not catastrophic. However, for very large projects like Launchpad, it can take up to a week of server time to perform the analysis. I have scheduled clean analyses for all three of these projects. I expect wikkid and drizzle to complete today, but I can't really predict how long launchpad will take. Thanks, Robin [Less]

Hi Brenda, We've been having some intermittent errors trying to fetch from the git server. I forced a couple of retries, and it finally went through. There's an updated report available now. Thanks, Robin

Hi Marco, Unfortunately, Ohloh cannot preserve historical data once the repositories are removed. We require an active, available repository to maintain our reports. Once the repositories are ... [More] de-listed from Ohloh, the commits and code will disappear from our reports. :-( Robin [Less]

Hi Eclesia, I'm afraid I don't quite understand what went wrong here -- Hg reported that we had a merge conflict when trying to pull into our local repository, which is strange because we never make ... [More] any changes to our repositories. I retried the job a few times, and it mysteriously succeeded. An updated report should be online in a few moments. Robin [Less]

Hi Steve, I just want to confirm what James has found: I think you have correctly identified the steps that need to be taken, but it appears that the BioPerl managers have locked down the permissions ... [More] on the project. You'll have to contact one of the managers in order to have the change made. Robin [Less]

Hi Aldric, This was caused by an error on our end. I've cleaned up the problem and updated the project. Let me know if you notice anything out of place. Thanks, Robin

Hi Yann, It appears that we had some kind of data corruption issue that blocked the updates. I've cleared up the problem and restarted the job, and it's running now. I'll keep an eye on it to make sure it finishes. Thanks, Robin