Does the dub registry at code.dlang.org have problems?

[Sönke Ludwig]

Am 10.01.2014 13:31, schrieb Gary Willoughby:
> On Friday, 10 January 2014 at 10:26:54 UTC, Gary Willoughby wrote:
>> On Friday, 10 January 2014 at 09:27:39 UTC, Jacob Carlborg wrote:
>>> On 2014-01-10 10:21, Gary Willoughby wrote:
>>>> Does the dub registry at code.dlang.org have problems?
>>>>
>>>> I registered two new packages yesterday and they are still not included
>>>> in the registry. It's annoying that registering or updating existing
>>>> packages take ages to be reflected on code.dlang.org.
>>>
>>> I can see that x11 was added/updated yesterday. Note that projects
>>> with a version tag is sorted first.
>>
>> I also have another package waiting called 'tcltk' which hasn't been
>> added yet and now all my packages in the UI have the following error:
>>
>> Failed to get GIT tags/branches: Failed to get tags: Failed to read
>> JSON from https://api.github.com/repos/nomad-software/x11/tags:
>> Unexpected reply for
>> 'https://api.github.com/repos/nomad-software/x11/tags': Forbidden

This most probably indicates that the API request limit for GitHub was 
reached. It will be reset on the next hour after that happens. The limit 
can be increased by registering code.dlang.org as a GitHub application, 
but that needs an OAuth client implementation first. Implementing a 
clear error message in this case would of course also be a good first 
step. Any contributions are welcome there!

>
> Everything seems to be fine now. Whoever is responsible for
> code.dlang.org please look into these issues. If we are going to use it
> as D's default package repository it needs to be bullet-proof and faster
> than it currently is. Waiting 14hrs+ for a package to be accepted or
> updated is quite frankly not good enough, especially if you are trying
> to test dependencies and resolve issues across packages. Thank you.

That it took so long was a bug, which unfortunately is hard to debug as 
the log output isn't verbose enough to show where it failed/hung - I'll 
increase the log level and look into it when/if it happens again. 
Normally, though, it will take a maximum of about 15 minutes, with the 
possibility of triggering a manual update to get an almost instant update.