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]
Hi guys,
Check this out: https://www.ohloh.net/p/ninjaboard/enlistments?page=1
The weird part is that according to my memory, this path were added and updated from just fine.
So it may have been an Unfuddle downtime or something that caused the error by mere chance.
Anything I can do to help?
Inline help says that deleting and re adding an enlistment only makes things worse, so here I am :)
Thanks
Stian,
A local error here at ohloh caused the update to fail. Re-fetched the broken enlistment which finished OK. This caused all the other enlistments to be updated as well. The analysis page is now up-to-date. Please take a look and let me know if all doesn't look as expected.
Thanks!
It's working correctly now, thanks :)
Stian,
On the enlistment page, all enlistments are showing as Ohloh update completed about 12 hours ago.
I notice one enlistment has an ignore order in place.
No jobs appear to have failed, either.
Analysis and commits seem to be up-to-date.
Were you able to fix this? Let me know.
Thanks!
I removed a few listings that linked to repositories that have been moved right after posting here.
It didn't try to update the enlistments immediately after I removed the culprits, so I didn't think that helped.
But it looks like it fixed itself then, by your bot automatically retrying at set intervals?
I think I fixed it, yeah.
Sorry for wasting your time :)
Stian,
No problem. Let me know here if any problems come up later.
Thanks!