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]
eAthena project not updated in 5 months
Hi, according to http://www.ohloh.net/p/eathena/enlistments it seems you guys do not periodically scan your database for failed updates, and they don't resume automatically. It's been like this for 5 years now, is there some problem?
ultramage,
Of the two error messages I've seen with this project I'm not sure which one I like least: svn: access forbidden
(the old one) or svn: Corrupt node-revision '0-2.0.r43/4544'
(today's error). I'll need to consult with a senior programmer and discuss this. I'll report back here if I get any satisfaction.
Thanks!
We have the repository mirrored several times; this enlistment is not the master repo (that's on google code), but instead the project administrator's personal mirror (which he enlisted here for some reason or another).
The access denied error was probably a temporary thing if ohloh hit the server while it was undergoing maintenance or downtime (or misconfiguration). That's no reason to quit.
The other error, I have no idea about; I can ask the admin to run svnadmin verify. We can also try looking into it from our side if needed.
ultramage,
Thanks for the offer. I would be interested to see if a similar error is seen on the repository end to the one that I'm seeing here. We do catch the first error but the system rescheduled the job three times and failed each time (perhaps for different reasons?) I have forgotten the sequence but each retry is staggered to come a variable time after the last and the entire series of retries probably took a few weeks to run through.
I look forward to any info you can find.
Thanks!
Hi, sorry for the delay; it turned out that the mirror that's currently recorded as the enlistment did indeed have corrupted data. It was subsequently re-created, so I'd like to ask you to resume the analysis of the repository.
PS: if I'm not mistaken, the reason why a mirror is used instead of the original is because ohloh had issues with the google code. I wonder if it's ok to switch it back now...
ultramage,
Ran a re-fetch on the repaired enlistment. Re-fetch and all following jobs ran OK. Analysis page is at Sep 26 2011 and last commit is at 2011-09-26 (about 19 hours ago).
If you'd like to try the original repository rather than the mirror, let me know and I'll watch the progress in case there is a problem. I wasn't aware there were any issues with Google code repositories - probably from before I started with ohloh. We could give it a try or leave that sleeping dog alone. Your call.
Thanks!