Thread overview | ||||||||
---|---|---|---|---|---|---|---|---|
|
October 06, 2018 DUB?? | ||||
---|---|---|---|---|
| ||||
what has happened to dub? 1.11 is current or so it says, but I see 1.9.x and when I click on dub in dub I get vibe errors. What has happened? for DUB I always see 500 - Internal Server Error Internal Server Error Internal error information: vibe.db.mongo.connection.MongoDriverException@../../.dub/packages/vibe-d-0.8.4/vibe-d/mongodb/vibe/db/mongo/cursor.d(304): Query failed. Does the database exist? ---------------- ??:? [0xa7d1ee] ??:? [0xa9dd0a] ??:? [0xa88ad2] exception.d:421 [0x50ea03] exception.d:388 [0x5050dd] cursor.d:304 [0x51ba4c] dbcontroller.d:393 [0x51c5b3] dbcontroller.d:253 [0x51c349] dbcontroller.d:367 [0x539cb4] cursor.d:233 [0x51b538] cursor.d:60 [0x47fdd9] iteration.d:587 [0x64c415] array.d:134 [0x47a42e] dbcontroller.d:325 [0x44b3e3] registry.d:103 [0x418162] web.d:474 [0x4180a1] web.d:1024 [0x5c116a] web.d:194 [0x5c0d5b] router.d:218 [0x91635e] router.d:674 [0x91906e] router.d:607 [0x91602a] router.d:211 [0x915d94] server.d:2247 [0x91ed67] server.d:241 [0x91d396] server.d:233 [0x91cfd7] server.d:2006 [0x926653] libevent2_tcp.d:612 [0x9fd22c] core.d:632 [0x49afcd] core.d:1241 [0x9e3f7f] ??:? [0xa80c81] for a long time now. |
October 07, 2018 Re: DUB?? | ||||
---|---|---|---|---|
| ||||
Posted in reply to steven kladitis | On 07/10/2018 6:36 AM, steven kladitis wrote: > what has happened to dub? > 1.11 is current or so it says, but I see 1.9.x and when I click on dub in dub I get vibe errors. What has happened? 1.11.0 is current https://github.com/dlang/dub/tree/v1.11.0 > for DUB I always see > 500 - Internal Server Error Do you mean code.dlang.org not dub? Because the common cause there is to do with searching and http://code.dlang.org/search?q=printed is working. |
October 06, 2018 Re: DUB?? | ||||
---|---|---|---|---|
| ||||
Posted in reply to rikki cattermole | On Saturday, 6 October 2018 at 17:48:00 UTC, rikki cattermole wrote: > On 07/10/2018 6:36 AM, steven kladitis wrote: >> what has happened to dub? >> 1.11 is current or so it says, but I see 1.9.x and when I click on dub in dub I get vibe errors. What has happened? > > 1.11.0 is current https://github.com/dlang/dub/tree/v1.11.0 > >> for DUB I always see >> 500 - Internal Server Error > > Do you mean code.dlang.org not dub? > Because the common cause there is to do with searching and http://code.dlang.org/search?q=printed is working. When you go to dlang.org then at top click on packages you will see 1.9.0 as current. type -> dub -< in search and you see problem. I do not see on this DB page a download for 1.11.X . this has been true for a long time. on the web pages I click on from dlang.org that takes me to https://code.dlang.org/download. |
October 06, 2018 Re: DUB?? | ||||
---|---|---|---|---|
| ||||
Posted in reply to steven kladitis | On Saturday, 6 October 2018 at 19:07:48 UTC, steven kladitis wrote: > On Saturday, 6 October 2018 at 17:48:00 UTC, rikki cattermole wrote: >> On 07/10/2018 6:36 AM, steven kladitis wrote: >>> [...] >> >> 1.11.0 is current https://github.com/dlang/dub/tree/v1.11.0 >> >>> [...] >> >> Do you mean code.dlang.org not dub? >> Because the common cause there is to do with searching and http://code.dlang.org/search?q=printed is working. > > When you go to dlang.org > then at top click on packages > you will see 1.9.0 as current. > type -> dub -< in search and you see problem. > I do not see on this DB page a download for 1.11.X . > this has been true for a long time. > on the web pages I click on from dlang.org > that takes me to https://code.dlang.org/download. Let's be concise. Click on this https://code.dlang.org/search?q=dub to get the error. |
October 08, 2018 Re: DUB?? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Basile B | On Saturday, 6 October 2018 at 20:27:07 UTC, Basile B wrote:
> On Saturday, 6 October 2018 at 19:07:48 UTC, steven kladitis wrote:
>> On Saturday, 6 October 2018 at 17:48:00 UTC, rikki cattermole wrote:
>>> On 07/10/2018 6:36 AM, steven kladitis wrote:
>>>> [...]
>>>
>>> 1.11.0 is current https://github.com/dlang/dub/tree/v1.11.0
>>>
>>>> [...]
>>>
>>> Do you mean code.dlang.org not dub?
>>> Because the common cause there is to do with searching and http://code.dlang.org/search?q=printed is working.
>>
>> When you go to dlang.org
>> then at top click on packages
>> you will see 1.9.0 as current.
>> type -> dub -< in search and you see problem.
>> I do not see on this DB page a download for 1.11.X .
>> this has been true for a long time.
>> on the web pages I click on from dlang.org
>> that takes me to https://code.dlang.org/download.
>
> Let's be concise. Click on this https://code.dlang.org/search?q=dub to get the error.
Will the search function ever be fixed on code.dlang.org?
|
October 08, 2018 Re: DUB?? | ||||
---|---|---|---|---|
| ||||
Posted in reply to bauss | On Monday, 8 October 2018 at 05:23:33 UTC, bauss wrote: > On Saturday, 6 October 2018 at 20:27:07 UTC, Basile B wrote: >> On Saturday, 6 October 2018 at 19:07:48 UTC, steven kladitis wrote: >>> On Saturday, 6 October 2018 at 17:48:00 UTC, rikki cattermole wrote: >>>> On 07/10/2018 6:36 AM, steven kladitis wrote: >>>>> [...] >>>> >>>> 1.11.0 is current https://github.com/dlang/dub/tree/v1.11.0 >>>> >>>>> [...] >>>> >>>> Do you mean code.dlang.org not dub? >>>> Because the common cause there is to do with searching and http://code.dlang.org/search?q=printed is working. >>> >>> When you go to dlang.org >>> then at top click on packages >>> you will see 1.9.0 as current. >>> type -> dub -< in search and you see problem. >>> I do not see on this DB page a download for 1.11.X . >>> this has been true for a long time. >>> on the web pages I click on from dlang.org >>> that takes me to https://code.dlang.org/download. >> >> Let's be concise. Click on this https://code.dlang.org/search?q=dub to get the error. > > Will the search function ever be fixed on code.dlang.org? This issue is known: https://github.com/dlang/dub-registry/issues/341 And I made a PR fixing it: https://github.com/dlang/dub-registry/pull/383 Sadly, even if I update it and it gets merged and deployed, it won't fix the problem completely. Problem is much deeper in the vibe-d's mongodb driver. What actually happens is mongodb driver throws an exception when there are too many entries returned for the query. This isn't because of memory allocation problems or anything like that - with my pagination PR it still throws on page #14 or so though every page has just 25 packages. |
Copyright © 1999-2021 by the D Language Foundation