www.digitalmars.com         C & C++   DMDScript  

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

reply "Gary Willoughby" <dev nomad.so> writes:
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.
Jan 10 2014
parent reply Jacob Carlborg <doob me.com> writes:
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
Jan 10 2014
next sibling parent "Gary Willoughby" <dev nomad.so> writes:
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.
Jan 10 2014
prev sibling parent reply "Gary Willoughby" <dev nomad.so> writes:
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
Jan 10 2014
next sibling parent reply "Gary Willoughby" <dev nomad.so> writes:
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.
Jan 10 2014
next sibling parent reply =?UTF-8?B?U8O2bmtlIEx1ZHdpZw==?= <sludwig+dforum outerproduct.org> writes:
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.
Jan 10 2014
parent reply Brad Roberts <braddr puremagic.com> writes:
On 1/10/14 5:26 AM, Sönke Ludwig wrote:

 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!


OAuth is only needed if you need to perform actions as someone else.  Otherwise
your own account 
creds are sufficient to be able to do 5000 queries an hour rather than the
unauth'ed limit of 60 an 
hour.
Jan 10 2014
parent =?UTF-8?B?U8O2bmtlIEx1ZHdpZw==?= <sludwig+dforum outerproduct.org> writes:
Am 10.01.2014 19:18, schrieb Brad Roberts:

 OAuth is only needed if you need to perform actions as someone else.
 Otherwise your own account creds are sufficient to be able to do 5000
 queries an hour rather than the unauth'ed limit of 60 an hour.


Good to know, I'll create a dummy account and test/implement that when I 
get some time (and nobody beats me to it ;)
Jan 11 2014
prev sibling parent reply Mike Parker <aldacron gmail.com> writes:
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.
Jan 10 2014
parent "Gary Willoughby" <dev nomad.so> writes:
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.
Jan 10 2014
prev sibling parent reply Andrej Mitrovic <andrej.mitrovich gmail.com> writes:
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.
Jan 10 2014
next sibling parent "Gary Willoughby" <dev nomad.so> writes:
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.
Jan 10 2014
prev sibling parent reply "Gary Willoughby" <dev nomad.so> writes:
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.


Actually, i'd be more than interested to learn how you support 
X11 (on which tcl/tk depends) on Windows?
Jan 10 2014
parent reply Paulo Pinto <pjmlp progtools.org> writes:
Am 10.01.2014 21:10, schrieb Gary Willoughby:

 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.


 Actually, i'd be more than interested to learn how you support X11 (on
 which tcl/tk depends) on Windows?


Tcl/Tk is also native on Windows, why the X11 question?
Jan 10 2014
parent reply "Gary Willoughby" <dev nomad.so> writes:
On Friday, 10 January 2014 at 20:31:04 UTC, Paulo Pinto wrote:

 Am 10.01.2014 21:10, schrieb Gary Willoughby:

 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.


 Actually, i'd be more than interested to learn how you support 
 X11 (on
 which tcl/tk depends) on Windows?


 Tcl/Tk is also native on Windows, why the X11 question?


Because the Tk headers also import the X11 headers.
Jan 10 2014
parent reply Paulo Pinto <pjmlp progtools.org> writes:
Am 10.01.2014 21:32, schrieb Gary Willoughby:

 On Friday, 10 January 2014 at 20:31:04 UTC, Paulo Pinto wrote:

 Am 10.01.2014 21:10, schrieb Gary Willoughby:

 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.


 Actually, i'd be more than interested to learn how you support X11 (on
 which tcl/tk depends) on Windows?


 Tcl/Tk is also native on Windows, why the X11 question?


 Because the Tk headers also import the X11 headers.


I used to be an heavy Tcl/Tk user on Windows NT/2000 during 1999 - 2001.

Tk only imports X11 on UNIX platforms.

http://core.tcl.tk/tk/tree?ci=tip

--
Paulo
Jan 10 2014
parent reply "Gary Willoughby" <dev nomad.so> writes:
On Friday, 10 January 2014 at 20:57:51 UTC, Paulo Pinto wrote:

 I used to be an heavy Tcl/Tk user on Windows NT/2000 during 
 1999 - 2001.

 Tk only imports X11 on UNIX platforms.

 http://core.tcl.tk/tk/tree?ci=tip

 --
 Paulo


Looking at tk.h i see this:

#ifndef _XLIB_H






#endif

Which intimates to me that all platforms include it? Then 
tkDecls.h uses types that the X11 headers define, e.g (XColor):

EXTERN int Tk_CanvasPsColor(Tcl_Interp *interp, Tk_Canvas canvas, 
XColor *colorPtr);
Jan 10 2014
parent reply Paulo Pinto <pjmlp progtools.org> writes:
Am 10.01.2014 22:16, schrieb Gary Willoughby:

 On Friday, 10 January 2014 at 20:57:51 UTC, Paulo Pinto wrote:

 I used to be an heavy Tcl/Tk user on Windows NT/2000 during 1999 - 2001.

 Tk only imports X11 on UNIX platforms.

 http://core.tcl.tk/tk/tree?ci=tip

 --
 Paulo


 Looking at tk.h i see this:

 #ifndef _XLIB_H






 #endif

 Which intimates to me that all platforms include it? Then tkDecls.h uses
 types that the X11 headers define, e.g (XColor):

 EXTERN int Tk_CanvasPsColor(Tcl_Interp *interp, Tk_Canvas canvas, XColor
 *colorPtr);



Yes, but if you cared to look at the rest of the code, you would have 
seen that those X11 calls are mapped to Win32 ones.

Maybe I should have expressed myself better.

--
Paulo
Jan 10 2014
next sibling parent "Gary Willoughby" <dev nomad.so> writes:
On Friday, 10 January 2014 at 22:07:41 UTC, Paulo Pinto wrote:

 Am 10.01.2014 22:16, schrieb Gary Willoughby:

 On Friday, 10 January 2014 at 20:57:51 UTC, Paulo Pinto wrote:

 I used to be an heavy Tcl/Tk user on Windows NT/2000 during 
 1999 - 2001.

 Tk only imports X11 on UNIX platforms.

 http://core.tcl.tk/tk/tree?ci=tip

 --
 Paulo


 Looking at tk.h i see this:

 #ifndef _XLIB_H






 #endif

 Which intimates to me that all platforms include it? Then 
 tkDecls.h uses
 types that the X11 headers define, e.g (XColor):

 EXTERN int Tk_CanvasPsColor(Tcl_Interp *interp, Tk_Canvas 
 canvas, XColor
 *colorPtr);



 Yes, but if you cared to look at the rest of the code, you 
 would have seen that those X11 calls are mapped to Win32 ones.

 Maybe I should have expressed myself better.

 --
 Paulo


I might be a bit tired here but i'm still not understanding what 
you mean. In tk.h, X11 is included for all platform AFAICS and 
the X11 types are use for many cross-platform functions 
parameters.
Jan 10 2014
prev sibling parent "Gary Willoughby" <dev nomad.so> writes:
On Friday, 10 January 2014 at 22:07:41 UTC, Paulo Pinto wrote:

 Am 10.01.2014 22:16, schrieb Gary Willoughby:

 On Friday, 10 January 2014 at 20:57:51 UTC, Paulo Pinto wrote:

 I used to be an heavy Tcl/Tk user on Windows NT/2000 during 
 1999 - 2001.

 Tk only imports X11 on UNIX platforms.

 http://core.tcl.tk/tk/tree?ci=tip

 --
 Paulo


 Looking at tk.h i see this:

 #ifndef _XLIB_H






 #endif

 Which intimates to me that all platforms include it? Then 
 tkDecls.h uses
 types that the X11 headers define, e.g (XColor):

 EXTERN int Tk_CanvasPsColor(Tcl_Interp *interp, Tk_Canvas 
 canvas, XColor
 *colorPtr);



 Yes, but if you cared to look at the rest of the code, you 
 would have seen that those X11 calls are mapped to Win32 ones.

 Maybe I should have expressed myself better.

 --
 Paulo


I understand that the X11 calls will be translated to the Win32 
Api on Windows in the Tk source but i was talking about the 
headers.

I think i have found the problem.

At first glance dub seems to dumbly compile *everything* in the 
source directory whether it's imported or not and in this case 
that's a problem. In a few of the X11 D source files, C macros 
are substituted using functions which call other X11 functions 
which the linker then cannot resolve.

If i compile using the command line on Windows then only x.d and 
xlib.d are in fact compiled which have no calls to any X11 
function so there are no linker errors regarding X11.

Now i just need to understand linking tcl/tk on windows using the 
optlink linker but that's a new thread :) 
http://forum.dlang.org/thread/xbrciixzdwkoysnnymht forum.dlang.org
Jan 11 2014