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]
Project 'lottanzb' not updating
http://www.ohloh.net/p/lottanzb/enlistments states that the import of the Bazaar trunk branch has failed 4 months ago, the URL is perfectly valid though. Since one is not supposed to delete and readd the enlistment, I created this forum post.
Does anyone know what the problem is? Thanks!
Hi Severin,
It looks like we received repeated Bad Gateway errors, and our system finally gave up trying.
However, everything looks just fine now. I've restarted the update, and it's running now. I'll keep an eye on it today.
Thanks,
Robin
Thanks alot for taking care of it, Robin!
The import of the Bazaar trunk branch seems to have stopped again about 4 months ago. May be the web interface should allow the maintainer of a project to manually trigger an import of its enlistments, as the system doesn't seem to recover on its own from a failure like this.
Severin,
The error was the following:
bzr: ERROR: These branches have diverged. Use the missing command to see how. Use the merge command to reconcile them.
We're not currently set up to handle this error intelligently in our automatic source update engine. In this case the error was irretrievable. I have started a re-fetch of this enlistment and hopefully should see some results soon.
Thanks!
Severin,
All jobs completed OK.
Please check the results and let me know if things aren't as you expect them to be.
Thanks!
Thanks a lot for taking care of it, ssnow-blackduck! The new import seems to have taken place without a hitch. Not surprisingly, re-fetching the enlistment has fixed the problem. Is it still true that regular users cannot trigger such a (reasonable) re-fetch by deleting and adding the enlistment again? This would allow me to fix such a problem on my own in the future, without having to bother someone in the support forum.
Kind regards and keep the good work up!
Severin,
For now, we'll still need to be involved. We have made some adjustments so that certain problems (network errors and the like) will begin to be self-correcting over time, but errors like this one haven't been included in the current generation of fixes that have been implemented.
There are many plans in the works for improving the control project managers do have over their projects. Please cruise this forum for other topics that discuss this and add your 2 (or more) cents to the discussion. Your input is always solicited!
Thanks!