Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.synopsys.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]
Should a project be left behind for more than two weeks?
tobi has not been updated since April 2. Still trouble with Subversion Sync Beta?
If there is a standard reaction to failures with Sync Beta, you might want to describe it on the Enlistments page...
Same for Heroes of Wesnoth. Not updated for 21 days and also using Subversion (Sync Beta).
I rescheduled downloads for tobi and heroes of wesnoth. They both completed and new analyses are available.
Mel has been sitting a Importing code (Failed)
for quite a while.
I've rescheduled the Mel project. Let me know if you need anything else.
remind admins to reschedule
button? :D
My project (BZLauncher) have not been updated for 18 days.
While I am in no hurry, an update would be nice :)
The project OpenStreetMap
seems to have had no update for almost four weeks now (subversion, too).
@marcin: Good idea. We've discussed this before and I suspect it's something we'll add at some point. However, I have no estimate on when.
@Dennis: I restarted BZLauncher. It's now complete.
@deelkar: It looks like timed-out trying to download a massive revision. I restarted the download and hopefully we'll have more luck this time.
Are you at all in the process of finding out why downloads and imports keep failing? The remind admins
button can't be a permanent solution.
Believe me, no one wants the failing downloads and imports fixed more than I do. I spend a lot of time on this every day.
Most download failures are caused by networking problems or server-side errors. There's little we can do about most of them, other than try again later.
We automatically reschedule certain kinds of well-known failures every hour, so if the failure matches a safe
profile it usually resolves itself without any intervention on our side.
Other types of errors get rescheduled less often, since we want to give the source control server time to recover from whatever is ailing it. This might be several days to a week, depending on when our server farm is most ready for the work.
Then there's the class of unknown errors that are too unsafe to automatically reschedule, such as endless hangs. The reality is that these errors might be harmless and temporary, but it's difficult to tell through automation. These types of errors don't get rescheduled unless someone requests it.
Some errors are indeed caused by problems on our end, but we're usually painfully aware of these issues :-) and as time goes on we have fewer of these.
From reading our forums, I suppose Ohloh looks like a disaster zone of broken updates, but we are successfully updating over 10,000 projects a day, and 0.1% failure rate leads to a lot of support.
Linux updates stopped almost 3 weeks ago. Please update. (I added many aliases and would like to see the result)
Please, GAL Framework, SoTerrain and QIDEdit was not updated since two months, It's same host but it was online as far as I remember.
Hi Radek,
I've rescheduled all of these projects, and they are currently running.
It looks like you do not have a permanent IP address for these projects, and are redirecting through no-ip.org. That's not a problem in itself, but it makes me suspicious that these repositories do not have 100% uptime, which can lead to intermittent failures and removal from the Ohloh queue.
I might be completely wrong, though, and perhaps it's not a significant issue.
Thanks, IP's permanent. It only changes during summer (home/school IP). I use no-ip since I can't pay for better name. Do you know more appropriate free domain name service?