Jump to page: 1 2
Thread overview
code.dlang.org having problems?
Mar 24, 2018
Russel Winder
Mar 24, 2018
rikki cattermole
Mar 24, 2018
Russel Winder
Mar 24, 2018
rikki cattermole
Mar 24, 2018
Andre Pany
Mar 24, 2018
Seb
Mar 24, 2018
Russel Winder
Mar 26, 2018
Atila Neves
Mar 26, 2018
Seb
Mar 26, 2018
Atila Neves
Mar 26, 2018
Seb
Mar 27, 2018
Atila Neves
Apr 04, 2018
Atila Neves
Mar 27, 2018
Anton Fediushin
March 24, 2018
It seems Dub is dead, and thus so are new Dub builds.

code.dlang.org appears to be having a 500 problem. I think the website is recovering as I write, but still no Dub builds so the point remains: no code.dlang.org, no Dub builds. :-(

-- 
Russel.
==========================================
Dr Russel Winder      t: +44 20 7585 2200
41 Buckmaster Road    m: +44 7770 465 077
London SW11 1EN, UK   w: www.russel.org.uk


March 25, 2018
On 25/03/2018 4:48 AM, Russel Winder wrote:
> It seems Dub is dead, and thus so are new Dub builds.
> 
> code.dlang.org appears to be having a 500 problem. I think the website is
> recovering as I write, but still no Dub builds so the point remains: no
> code.dlang.org, no Dub builds. :-(
> 

Tip: $ dub --skip-registry=all
March 24, 2018
On Sun, 2018-03-25 at 04:50 +1300, rikki cattermole via Digitalmars-d wrote:
> On 25/03/2018 4:48 AM, Russel Winder wrote:
> > It seems Dub is dead, and thus so are new Dub builds.
> > 
> > code.dlang.org appears to be having a 500 problem. I think the website is recovering as I write, but still no Dub builds so the point remains: no code.dlang.org, no Dub builds. :-(
> > 
> 
> Tip: $ dub --skip-registry=all

Not useful just no, I need new versions. Two reasons: 1. I didn't have the latest version locally; and 2. I deleted ~/.dub as a clean up measure to get rid of all the crap accrued over the years.

Useful for non-dependency upgrade features though.

-- 
Russel.
==========================================
Dr Russel Winder      t: +44 20 7585 2200
41 Buckmaster Road    m: +44 7770 465 077
London SW11 1EN, UK   w: www.russel.org.uk


March 25, 2018
On 25/03/2018 5:10 AM, Russel Winder wrote:
> On Sun, 2018-03-25 at 04:50 +1300, rikki cattermole via Digitalmars-d wrote:
>> On 25/03/2018 4:48 AM, Russel Winder wrote:
>>> It seems Dub is dead, and thus so are new Dub builds.
>>>
>>> code.dlang.org appears to be having a 500 problem. I think the website is
>>> recovering as I write, but still no Dub builds so the point remains: no
>>> code.dlang.org, no Dub builds. :-(
>>>
>>
>> Tip: $ dub --skip-registry=all
> 
> Not useful just no, I need new versions. Two reasons: 1. I didn't have the
> latest version locally; and 2. I deleted ~/.dub as a clean up measure to get
> rid of all the crap accrued over the years.

$ git clone https://yyyy/xx/zz
$ dub add-local zz

These are workarounds, to keep you going.
Preferable no, but what else can you do really?

The only thing comes to mind is allow dub itself to retrieve the projects zip and cache the database locally.
March 24, 2018
On Saturday, 24 March 2018 at 15:48:21 UTC, Russel Winder wrote:
> It seems Dub is dead, and thus so are new Dub builds.
>
> code.dlang.org appears to be having a 500 problem. I think the website is recovering as I write, but still no Dub builds so the point remains: no code.dlang.org, no Dub builds. :-(

Are you using an old dub binary?

Since 1.6 dub has built-in mirrors like e.g. https://code-mirror.dlang.io
And since 1.7. it has even more like https://dub-registry.herokuapp.com

So this should cause no outage as the dub binary will softly fallback to its mirrors.
Regarding the current code.dlang.org problems, see:

https://github.com/dlang/dub-registry/issues/298
March 24, 2018
On Sat, 2018-03-24 at 16:59 +0000, Seb via Digitalmars-d wrote:
> On Saturday, 24 March 2018 at 15:48:21 UTC, Russel Winder wrote:
> > It seems Dub is dead, and thus so are new Dub builds.
> > 
> > code.dlang.org appears to be having a 500 problem. I think the website is recovering as I write, but still no Dub builds so the point remains: no code.dlang.org, no Dub builds. :-(
> 
> Are you using an old dub binary?
> 
> Since 1.6 dub has built-in mirrors like e.g.
> https://code-mirror.dlang.io
> And since 1.7. it has even more like
> https://dub-registry.herokuapp.com
> 
> So this should cause no outage as the dub binary will softly
> fallback to its mirrors.
> Regarding the current code.dlang.org problems, see:
> 
> https://github.com/dlang/dub-registry/issues/298

I am using the Debian Stable packaged version which is 1.7.2

|> dub build
Error querying versions for dinotify, registry at https://code.dlang.org/ (fallback ["registry at http://code.dlang.org/", "registry at https://code-mirror.dlang.io/", "registry at https://code-mirror2.dlang.io/", "registry at https://dub-registry.herokuapp.com/"]): HTTP request returned status code 0 ()
Selected package dinotify 0.3.0 doesn't exist. Using latest matching version instead.
Error querying versions for unit-threaded, registry at https://code.dlang.org/ (fallback ["registry at http://code.dlang.org/", "registry at https://code-mirror.dlang.io/", "registry at https://code-mirror2.dlang.io/", "registry at https://dub-registry.herokuapp.com/"]): HTTP request returned status code 0 ()
Selected package unit-threaded 0.7.38 doesn't exist. Using latest matching version instead.
Error querying versions for gtk-d, registry at https://code.dlang.org/ (fallback ["registry at http://code.dlang.org/", "registry at https://code-mirror.dlang.io/", "registry at https://code-mirror2.dlang.io/", "registry at https://dub-registry.herokuapp.com/"]): HTTP request returned status code 0 ()
Selected package gtk-d 3.7.3 doesn't exist. Using latest matching version instead.
Package gtk-d not found in registry at https://code.dlang.org/ (fallback ["registry at http://code.dlang.org/", "registry at https://code-mirror.dlang.io/", "registry at https://code-mirror2.dlang.io/", "registry at https://dub-registry.herokuapp.com/"]): HTTP request returned status code 0 ()
Package dinotify not found in registry at https://code.dlang.org/ (fallback ["registry at http://code.dlang.org/", "registry at https://code-mirror.dlang.io/", "registry at https://code-mirror2.dlang.io/", "registry at https://dub-registry.herokuapp.com/"]): HTTP request returned status code 0 ()
Package unit-threaded not found in registry at https://code.dlang.org/ (fallback ["registry at http://code.dlang.org/", "registry at https://code-mirror.dlang.io/", "registry at https://code-mirror2.dlang.io/", "registry at https://dub-registry.herokuapp.com/"]): HTTP request returned status code 0 ()
Root package me-tv references unknown package gtk-d:gstreamer

-- 
Russel.
==========================================
Dr Russel Winder      t: +44 20 7585 2200
41 Buckmaster Road    m: +44 7770 465 077
London SW11 1EN, UK   w: www.russel.org.uk


March 24, 2018
On Saturday, 24 March 2018 at 16:14:20 UTC, rikki cattermole wrote:
> On 25/03/2018 5:10 AM, Russel Winder wrote:
>> On Sun, 2018-03-25 at 04:50 +1300, rikki cattermole via Digitalmars-d wrote:
>>> On 25/03/2018 4:48 AM, Russel Winder wrote:
>>>> It seems Dub is dead, and thus so are new Dub builds.
>>>>
>>>> code.dlang.org appears to be having a 500 problem. I think the website is
>>>> recovering as I write, but still no Dub builds so the point remains: no
>>>> code.dlang.org, no Dub builds. :-(
>>>>
>>>
>>> Tip: $ dub --skip-registry=all
>> 
>> Not useful just no, I need new versions. Two reasons: 1. I didn't have the
>> latest version locally; and 2. I deleted ~/.dub as a clean up measure to get
>> rid of all the crap accrued over the years.
>
> $ git clone https://yyyy/xx/zz
> $ dub add-local zz
>
> These are workarounds, to keep you going.
> Preferable no, but what else can you do really?
>
> The only thing comes to mind is allow dub itself to retrieve the projects zip and cache the database locally.

There are currently 2 interesting dub pull requests. First one allows you to specify git dependencies. Second one allows you to connect to maven repositories. If e.g. the dub packages also beeing cloned to a maven repository this would increase the safety net.
Next step of course would be a pull request to allow url (zip) dependencies. May someone is so kind to create a pr.

Kind regards
Andre
March 26, 2018
On Saturday, 24 March 2018 at 15:48:21 UTC, Russel Winder wrote:
> It seems Dub is dead, and thus so are new Dub builds.
>
> code.dlang.org appears to be having a 500 problem. I think the website is recovering as I write, but still no Dub builds so the point remains: no code.dlang.org, no Dub builds. :-(

code.dlang.org being down is now the main reason I experience build failures.

Atila
March 26, 2018
On Monday, 26 March 2018 at 14:16:28 UTC, Atila Neves wrote:
> On Saturday, 24 March 2018 at 15:48:21 UTC, Russel Winder wrote:
>> It seems Dub is dead, and thus so are new Dub builds.
>>
>> code.dlang.org appears to be having a 500 problem. I think the website is recovering as I write, but still no Dub builds so the point remains: no code.dlang.org, no Dub builds. :-(
>
> code.dlang.org being down is now the main reason I experience build failures.
>
> Atila

Even with a recent DUB binary (e.g. 1.7.2 or 1.8.0)?
(=2.078.3 or 2.079.0)

Anything that you are being able to reproduce with a "fake" always failing registry?

In theory the recent DUB binaries comes with multiple backup mirrors and a more advanced retry logic.
We even have a few tests for this now, e.g.

https://github.com/dlang/dub/blob/master/test/timeout.sh
https://github.com/dlang/dub/blob/master/test/fetchzip.sh
March 26, 2018
On Monday, 26 March 2018 at 15:34:12 UTC, Seb wrote:
> On Monday, 26 March 2018 at 14:16:28 UTC, Atila Neves wrote:
>> On Saturday, 24 March 2018 at 15:48:21 UTC, Russel Winder wrote:
>>> [...]
>>
>> code.dlang.org being down is now the main reason I experience build failures.
>>
>> Atila
>
> Even with a recent DUB binary (e.g. 1.7.2 or 1.8.0)?
> (=2.078.3 or 2.079.0)
>
> Anything that you are being able to reproduce with a "fake" always failing registry?
>
> In theory the recent DUB binaries comes with multiple backup mirrors and a more advanced retry logic.
> We even have a few tests for this now, e.g.
>
> https://github.com/dlang/dub/blob/master/test/timeout.sh
> https://github.com/dlang/dub/blob/master/test/fetchzip.sh

Yes. Today it took too long to respond and my travis build failed because it was hung for >10min.

Atila
« First   ‹ Prev
1 2