Jump to page: 1 2
Thread overview
Does the dub registry at code.dlang.org have problems?
Jan 10, 2014
Gary Willoughby
Jan 10, 2014
Jacob Carlborg
Jan 10, 2014
Gary Willoughby
Jan 10, 2014
Gary Willoughby
Jan 10, 2014
Gary Willoughby
Jan 10, 2014
Sönke Ludwig
Jan 10, 2014
Brad Roberts
Jan 11, 2014
Sönke Ludwig
Jan 10, 2014
Mike Parker
Jan 10, 2014
Gary Willoughby
Jan 10, 2014
Andrej Mitrovic
Jan 10, 2014
Gary Willoughby
Jan 10, 2014
Gary Willoughby
Jan 10, 2014
Paulo Pinto
Jan 10, 2014
Gary Willoughby
Jan 10, 2014
Paulo Pinto
Jan 10, 2014
Gary Willoughby
Jan 10, 2014
Paulo Pinto
Jan 11, 2014
Gary Willoughby
Jan 11, 2014
Gary Willoughby
January 10, 2014
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.
January 10, 2014
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.

-- 
/Jacob Carlborg
January 10, 2014
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.

It's literally been added in the last hour and 'My Packages' is now updated. That's over 12 hours of waiting.
January 10, 2014
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
January 10, 2014
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

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.
January 10, 2014
On 1/10/14, Gary Willoughby <dev@nomad.so> wrote:
> 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:

Hi,

I have a D OOP Tk wrapper which I paused working on for a while since I had other plans at the moment. Currently it only works on Win32 (I didn't have the time to work on enabling it on other platforms yet) but it has lots of features and tests too: https://github.com/AndrejMitrovic/dtk/

I'm not home right now though (~ next 3 weeks), so I can only periodically check the e-mail every now and then.
January 10, 2014
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.

January 10, 2014
On 1/10/2014 9:31 PM, Gary Willoughby wrote:

> 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.

To test dependencies and such, you should use 'dub add-local' with your local copy of the source. I currently have a couple of dub-managed libraries I've been working on that I haven't even put on github yet and used add-local so that they're available to my test apps. That way you don't have to register anything with code.dlang.org until you're ready for release.
January 10, 2014
On Friday, 10 January 2014 at 13:45:48 UTC, Mike Parker wrote:
> On 1/10/2014 9:31 PM, Gary Willoughby wrote:
>
>> 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.
>
> To test dependencies and such, you should use 'dub add-local' with your local copy of the source. I currently have a couple of dub-managed libraries I've been working on that I haven't even put on github yet and used add-local so that they're available to my test apps. That way you don't have to register anything with code.dlang.org until you're ready for release.

This is really useful thanks. Even after doing this though we'll still need to test in a live environment.
January 10, 2014
On Friday, 10 January 2014 at 12:47:54 UTC, Andrej Mitrovic wrote:
> On 1/10/14, Gary Willoughby <dev@nomad.so> wrote:
>> 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:
>
> Hi,
>
> I have a D OOP Tk wrapper which I paused working on for a while since
> I had other plans at the moment. Currently it only works on Win32 (I
> didn't have the time to work on enabling it on other platforms yet)
> but it has lots of features and tests too:
> https://github.com/AndrejMitrovic/dtk/
>
> I'm not home right now though (~ next 3 weeks), so I can only
> periodically check the e-mail every now and then.

Awesome! i'm working on one too but approaching it in a different way and hopefully will be fully cross-platform.
« First   ‹ Prev
1 2