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]
Tigase Jabber/XMPP Server not updating
https://www.ohloh.net/p/tigasexmpp/commits
Update status says (Failed 3 months ago.)
, however provided link works for me without any problem:
git.exe clone --progress -v git://repository.tigase.org/git/tigase-server.git
D:\dev\__tigase\_tmp\tigase-server
Cloning into 'D:\dev__tigase_tmp\tigase-server'...
remote: Counting objects: 34043, done.
Receiving objects: 100% (34043/34043), 29.99 MiB | 769 KiB/s, done.
Resolving deltas: 100% (22844/22844), done.
remote: Compressing objects: 100% (8630/8630), done.
remote: Total 34043 (delta 22844), reused 29704 (delta 19767)
Success (47172 ms @ 2013-12-17 06:46:14)
Please assist.
(having more informative errors on the status page would be handy tho)
Wojciech,
Updates stubbornly failed for all three enlistments:
errno=Connection refused
repeated ten times over the last 217 days.
fatal: unable to connect a socket (Connection refused)
Re-fetched the three enlistments which finished OK (214, 264 and 3404 total commits respectively). Analysis is now at December 17, 2013 on code collected on December 17, 2013 and last commit is at December 16, 2013.
Sorry about the lack of error messages so far... we are considering ways to give managers better feedback, however.
Please keep an eye on it for me and remind me here if the updates fail again.
Thanks!
Thanks a million.
Btw. in addition to better error it would be nice to have a way to force re-check of the repository with a button click instead of posting to the forums.
Also - notification to the project owner/manager would be a nice addition :)
Wojciech,
I can see it would make everybody's life easier if the reasons for a failure were more clear. And a re-try would be welcome but we need to balance that out knowing the experience level of the different managers and how the extra detail might be interpreted differently.
We do need to think about how we might notify a manager when a project goes off the rails. Some of them would love the extra detail; others wouldn't be so impressed. I suspect it would need to be an opt-in situation.
Thanks for the suggestions. Will pass them on to management for consideration.
Hello again,
all listed repositories are stuck in Waiting in queue
for quite some time -- is it normal?
Wojciech,
Same problem applies this time. Even saw it on the first attempt to retrieve one of the repositories to my workstation.
fatal: unable to connect to repository....:
errno=Connection refused
Tried a second time and it worked OK with a slightly different address. Following attempts all succeeded even with identical commands to the first. Have rescheduled the updates and will monitor them for their progress.
Thanks!
OK, great, thanks!
Wojciech,
It's dead, Jim...
So, can you contact the support for the repository and see if we have irritated them enough that we are blackballed?
Thanks!
P.S. I'll send along an e-mail with three error messages and you can forward it to their support desk if that will help...
Wojciech,
Tigase Jabber/XMPP Server finished its update OK 7 days ago. An additional update ran about 9 hours ago and added only 3 commits in the server
enlistment. Analysis is now at October 23, 2014 on code collected on October 23, 2014 and last commit is at October 21, 2014.
Please remind me here if the project fails to properly update.
Thanks!
Great! Thank you!