July 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] SmalltalkHub MCRepositoryError, ZnHttpUnsuccessful: 503 Service Temporarily Unavailable

by Sean Glazier

I have also been getting this same error with a number of configurations. I am trying to get Pier 3 loaded and working in Pharo 5. I have been unsuccessful so far though I would like to be able to use and experiment with it. Is there a seaside image out there or a configuration I can load. In the Pharo 5 image, I loaded it and it was tagged Pharo 5 . Has anyone else had this issue? Thank you! Kind Regards, Sean Glazier On Sat, Jul 23, 2016 at 1:15 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > OK. Thanks for the explanation. > > Cheers, > Juraj > > > El 23-07-2016, a las 10:26, Sven Van Caekenberghe <sven(a)stfx.eu> > escribiÃ³: > > > > StHub is behaving very badly lately, which results in many builds > failing (obviously, they all need access to repos). There is nothing you > can do about it, but report it as you did. > > > >> On 23 Jul 2016, at 16:07, Juraj Kubelka <juraj.kubelka(a)icloud.com> > wrote: > >> > >> Hi, > >> > >> It has been already several days that SmalltalkHub say > "ZnHttpUnsuccessful: 503 Service Temporarily Unavailableâ. Is it known > problem? > >> > >> MCRepositoryError: Could not load > ConfigurationOfGlamourCore-JurajKubelka.142.mcz: ZnHttpUnsuccessful: 503 > Service Temporarily Unavailable > >> > >> It happens whenever FogBugz is checking case: > https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/6360//artifact/vali… > >> > >> What I can do about it? > >> Cheers, > >> Juraj > > > > > > >

July 23, 2016

Re: [Pharo-dev] SmalltalkHub MCRepositoryError, ZnHttpUnsuccessful: 503 Service Temporarily Unavailable

by Juraj Kubelka

OK. Thanks for the explanation. Cheers, Juraj > El 23-07-2016, a las 10:26, Sven Van Caekenberghe <sven(a)stfx.eu> escribiÃ³: > > StHub is behaving very badly lately, which results in many builds failing (obviously, they all need access to repos). There is nothing you can do about it, but report it as you did. > >> On 23 Jul 2016, at 16:07, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: >> >> Hi, >> >> It has been already several days that SmalltalkHub say "ZnHttpUnsuccessful: 503 Service Temporarily Unavailableâ. Is it known problem? >> >> MCRepositoryError: Could not load ConfigurationOfGlamourCore-JurajKubelka.142.mcz: ZnHttpUnsuccessful: 503 Service Temporarily Unavailable >> >> It happens whenever FogBugz is checking case: https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/6360//artifact/vali… >> >> What I can do about it? >> Cheers, >> Juraj > >

July 23, 2016

Re: [Pharo-dev] SmalltalkHub MCRepositoryError, ZnHttpUnsuccessful: 503 Service Temporarily Unavailable

by Sven Van Caekenberghe

StHub is behaving very badly lately, which results in many builds failing (obviously, they all need access to repos). There is nothing you can do about it, but report it as you did. > On 23 Jul 2016, at 16:07, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > > Hi, > > It has been already several days that SmalltalkHub say "ZnHttpUnsuccessful: 503 Service Temporarily Unavailableâ. Is it known problem? > > MCRepositoryError: Could not load ConfigurationOfGlamourCore-JurajKubelka.142.mcz: ZnHttpUnsuccessful: 503 Service Temporarily Unavailable > > It happens whenever FogBugz is checking case: https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/6360//artifact/vali… > > What I can do about it? > Cheers, > Juraj

July 23, 2016

Re: [Pharo-dev] SmalltalkHub MCRepositoryError, ZnHttpUnsuccessful: 503 Service Temporarily Unavailable

by Max Leske

This happens from time to time but usually Marcus or Esteban fix it. Now they are both on holiday, so it may take while longer. > On 23 Jul 2016, at 16:07, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > > Hi, > > It has been already several days that SmalltalkHub say "ZnHttpUnsuccessful: 503 Service Temporarily Unavailableâ. Is it known problem? > > MCRepositoryError: Could not load ConfigurationOfGlamourCore-JurajKubelka.142.mcz: ZnHttpUnsuccessful: 503 Service Temporarily Unavailable > > It happens whenever FogBugz is checking case: https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/6360//artifact/vali… > > What I can do about it? > Cheers, > Juraj

July 23, 2016

Re: [Pharo-dev] github-cache organisation

by Dale Henrichs

On 7/23/16 6:51 AM, Ben Coman wrote: > On Sat, Jul 23, 2016 at 8:48 PM, Dale Henrichs > <dale.henrichs(a)gemtalksystems.com> wrote: >> >> On 7/22/16 8:02 PM, Ben Coman wrote: >> >>>> Ben, >>>> >>>> Sorry ... I gave you the wrong issue # for this one ... I opened 3 new >>>> issues for this message and only 2 of them applied directly '#405: Github >>>> .zip download not downloaded to `/tmp` as expected ... Pharo-5.0' and >>>> '#406: >>>> Github .zip download file should be deleted after archive is extracted' >>>> ... >>>> #404 is not really an issue, since the pid is meant for disambiguation of >>>> the file name, which is exactly the same thing that is supposed to be >>>> done >>>> by FileReference class>>newTempFilePrefix:suffix: ... >>>> >>>> Too many windows floating around:) >>>> >>>> Dale >>>> >>> @All, btw in the pharo-project swimlane here [1] it would be nice to >>> have a branch tagged "Pharo5.0" showing the point that was integrated >>> into Pharo 5. >>> cheers -ben >>> >> Ben ... are you missing an url for [1]? I'm afraid I have no idea what a >> "pharo-project swimlane" is. > Whoops. Yes. > [1] https://github.com/dalehenrich/metacello-work/network > > and from that you probably know or guess what a swimlane is, but to be clear... > [2] https://en.wikipedia.org/wiki/Swim_lane I thought perhaps that the "pharo-project swimlane" had something to do with the "divers" over on FogBugz and thought that there was some sort of swimming themed development going on in Pharo land:) The master branch of Metacello includes code for all supported platforms, so I'm not sure what you want a "swimlane" for ... unless you are referring to the fact that there is no way to tell what commit has actually been integrated into the PharoX.0 builds - then I agree. It would also be nice if the latest commit on the master branch was automatically integrated into the Pharo builds ... Dale

July 23, 2016

SmalltalkHub MCRepositoryError, ZnHttpUnsuccessful: 503 Service Temporarily Unavailable

by Juraj Kubelka

Hi, It has been already several days that SmalltalkHub say "ZnHttpUnsuccessful: 503 Service Temporarily Unavailableâ. Is it known problem? MCRepositoryError: Could not load ConfigurationOfGlamourCore-JurajKubelka.142.mcz: ZnHttpUnsuccessful: 503 Service Temporarily Unavailable It happens whenever FogBugz is checking case: https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/6360//artifact/vali… What I can do about it? Cheers, Juraj

July 23, 2016

Re: [Pharo-dev] github-cache organisation

by Ben Coman

On Sat, Jul 23, 2016 at 8:48 PM, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > > > On 7/22/16 8:02 PM, Ben Coman wrote: >> >> On Sat, Jul 23, 2016 at 2:29 AM, Dale Henrichs >> <dale.henrichs(a)gemtalksystems.com> wrote: >>> >>> >>> On 07/22/2016 11:19 AM, Ben Coman wrote: >>>>> >>>>> On 07/21/2016 08:40 PM, Ben Coman wrote: >>>>>> >>>>>> Just a general observation and first impression of installing a github >>>>>> hosted project. >>>>>> >>>>>> After installing OSSubprocess from the Catalog Browser on Pharo 50760, >>>>>> which uses repository... >>>>>> github://marianopeck/OSSubProcess:v0.2.4/repository >>>>>> >>>>>> ...I see file >>>>>> >>>>>> "github--marianopeckOSSubprocessv0241266307023333901887488330764830.zip" >>>>>> sitting next to my .image file. That would seem to dirty up that area >>>>>> when I start to use git more often. I'd expect that file to be placed >>>>>> in >>>>>> one of the cache folders. >>>>>> >>>>>> cheers -ben >>>>> >>>>> >>>>> >>>> On Sat, Jul 23, 2016 at 1:38 AM, Dale Henrichs >>>> <dale.henrichs(a)gemtalksystems.com> wrote: >>>>> >>>>> Ben, >>>>> >>>>> I think I've found the bug ... Metacello intends that the zip file be >>>>> downloaded to /tmp, but the code as implemented 3 years ago for Pharo >>>>> was >>>>> not actually downloading the file to /tmp ... thanks for pointing this >>>>> out, >>>>> I've created a Metacello issue for this[1] ... I will probably fix this >>>>> shortly, but I'm not sure when (or if) my fix will be integrated into >>>>> the >>>>> Pharo-5.0 release. >>>> >>>> Cool. Thanks Dale. I created issues for Pharo 5 & 6 to track this our >>>> end. >>>> https://pharo.fogbugz.com/default.asp?18804 >>>> https://pharo.fogbugz.com/default.asp?18805 >>>> >>>> cheers -ben >>>> >>>> P.S.@All curious why "Area=divers" for "Project=Metacello" >>>> >>>> >>> Ben, >>> >>> Sorry ... I gave you the wrong issue # for this one ... I opened 3 new >>> issues for this message and only 2 of them applied directly '#405: Github >>> .zip download not downloaded to `/tmp` as expected ... Pharo-5.0' and >>> '#406: >>> Github .zip download file should be deleted after archive is extracted' >>> ... >>> #404 is not really an issue, since the pid is meant for disambiguation of >>> the file name, which is exactly the same thing that is supposed to be >>> done >>> by FileReference class>>newTempFilePrefix:suffix: ... >>> >>> Too many windows floating around:) >>> >>> Dale >>> >> @All, btw in the pharo-project swimlane here [1] it would be nice to >> have a branch tagged "Pharo5.0" showing the point that was integrated >> into Pharo 5. >> cheers -ben >> > Ben ... are you missing an url for [1]? I'm afraid I have no idea what a > "pharo-project swimlane" is. Whoops. Yes. [1] https://github.com/dalehenrich/metacello-work/network and from that you probably know or guess what a swimlane is, but to be clear... [2] https://en.wikipedia.org/wiki/Swim_lane cheers -ben > > As an aside, when these bugs are fixed in Metacello the fixes will apply to > Pharo3.0, Pharo4.0, Pharo5.0, and Pharo6.0 ...

July 23, 2016

Re: [Pharo-dev] github-cache organisation

by Dale Henrichs

On 7/22/16 8:02 PM, Ben Coman wrote: > On Sat, Jul 23, 2016 at 2:29 AM, Dale Henrichs > <dale.henrichs(a)gemtalksystems.com> wrote: >> >> On 07/22/2016 11:19 AM, Ben Coman wrote: >>>> On 07/21/2016 08:40 PM, Ben Coman wrote: >>>>> Just a general observation and first impression of installing a github >>>>> hosted project. >>>>> >>>>> After installing OSSubprocess from the Catalog Browser on Pharo 50760, >>>>> which uses repository... >>>>> github://marianopeck/OSSubProcess:v0.2.4/repository >>>>> >>>>> ...I see file >>>>> "github--marianopeckOSSubprocessv0241266307023333901887488330764830.zip" >>>>> sitting next to my .image file. That would seem to dirty up that area >>>>> when I start to use git more often. I'd expect that file to be placed >>>>> in >>>>> one of the cache folders. >>>>> >>>>> cheers -ben >>>> >>>> >>> On Sat, Jul 23, 2016 at 1:38 AM, Dale Henrichs >>> <dale.henrichs(a)gemtalksystems.com> wrote: >>>> Ben, >>>> >>>> I think I've found the bug ... Metacello intends that the zip file be >>>> downloaded to /tmp, but the code as implemented 3 years ago for Pharo was >>>> not actually downloading the file to /tmp ... thanks for pointing this >>>> out, >>>> I've created a Metacello issue for this[1] ... I will probably fix this >>>> shortly, but I'm not sure when (or if) my fix will be integrated into the >>>> Pharo-5.0 release. >>> Cool. Thanks Dale. I created issues for Pharo 5 & 6 to track this our >>> end. >>> https://pharo.fogbugz.com/default.asp?18804 >>> https://pharo.fogbugz.com/default.asp?18805 >>> >>> cheers -ben >>> >>> P.S.@All curious why "Area=divers" for "Project=Metacello" >>> >>> >> Ben, >> >> Sorry ... I gave you the wrong issue # for this one ... I opened 3 new >> issues for this message and only 2 of them applied directly '#405: Github >> .zip download not downloaded to `/tmp` as expected ... Pharo-5.0' and '#406: >> Github .zip download file should be deleted after archive is extracted' ... >> #404 is not really an issue, since the pid is meant for disambiguation of >> the file name, which is exactly the same thing that is supposed to be done >> by FileReference class>>newTempFilePrefix:suffix: ... >> >> Too many windows floating around:) >> >> Dale >> > @All, btw in the pharo-project swimlane here [1] it would be nice to > have a branch tagged "Pharo5.0" showing the point that was integrated > into Pharo 5. > cheers -ben > Ben ... are you missing an url for [1]? I'm afraid I have no idea what a "pharo-project swimlane" is. As an aside, when these bugs are fixed in Metacello the fixes will apply to Pharo3.0, Pharo4.0, Pharo5.0, and Pharo6.0 ... Dale Dale

July 23, 2016

Re: [Pharo-dev] github-cache organisation

by Ben Coman

On Sat, Jul 23, 2016 at 2:29 AM, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > > > On 07/22/2016 11:19 AM, Ben Coman wrote: >>> >>> On 07/21/2016 08:40 PM, Ben Coman wrote: >>>> >>>> Just a general observation and first impression of installing a github >>>> hosted project. >>>> >>>> After installing OSSubprocess from the Catalog Browser on Pharo 50760, >>>> which uses repository... >>>> github://marianopeck/OSSubProcess:v0.2.4/repository >>>> >>>> ...I see file >>>> "github--marianopeckOSSubprocessv0241266307023333901887488330764830.zip" >>>> sitting next to my .image file. That would seem to dirty up that area >>>> when I start to use git more often. I'd expect that file to be placed >>>> in >>>> one of the cache folders. >>>> >>>> cheers -ben >>> >>> >>> >> On Sat, Jul 23, 2016 at 1:38 AM, Dale Henrichs >> <dale.henrichs(a)gemtalksystems.com> wrote: >>> >>> Ben, >>> >>> I think I've found the bug ... Metacello intends that the zip file be >>> downloaded to /tmp, but the code as implemented 3 years ago for Pharo was >>> not actually downloading the file to /tmp ... thanks for pointing this >>> out, >>> I've created a Metacello issue for this[1] ... I will probably fix this >>> shortly, but I'm not sure when (or if) my fix will be integrated into the >>> Pharo-5.0 release. >> >> Cool. Thanks Dale. I created issues for Pharo 5 & 6 to track this our >> end. >> https://pharo.fogbugz.com/default.asp?18804 >> https://pharo.fogbugz.com/default.asp?18805 >> >> cheers -ben >> >> P.S.@All curious why "Area=divers" for "Project=Metacello" >> >> > Ben, > > Sorry ... I gave you the wrong issue # for this one ... I opened 3 new > issues for this message and only 2 of them applied directly '#405: Github > .zip download not downloaded to `/tmp` as expected ... Pharo-5.0' and '#406: > Github .zip download file should be deleted after archive is extracted' ... > #404 is not really an issue, since the pid is meant for disambiguation of > the file name, which is exactly the same thing that is supposed to be done > by FileReference class>>newTempFilePrefix:suffix: ... > > Too many windows floating around:) > > Dale > @All, btw in the pharo-project swimlane here [1] it would be nice to have a branch tagged "Pharo5.0" showing the point that was integrated into Pharo 5. cheers -ben

July 23, 2016

Re: [Pharo-dev] A taste of bootstrap

by Nicolas Passerini

Hey! This is great news! I am anxious to work with you for integrating git and bootstrap. On Fri, Jul 22, 2016 at 8:57 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > 2016-07-22 16:42 GMT+02:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> >> >> On Fri, Jul 22, 2016 at 11:38 AM, Pavel Krivanek < >> pavel.krivanek(a)gmail.com> wrote: >> >>> >>> >>> 2016-07-22 16:24 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: >>> >>>> >>>> >>>> On Fri, Jul 22, 2016 at 4:12 PM, Mariano Martinez Peck < >>>> marianopeck(a)gmail.com> wrote: >>>> >>>>> Hi Pavel, >>>>> >>>>> Congrats for your hard work! You know me well, so don't take my next >>>>> question as negative. >>>>> You have been working in minimal images since years. Guille has also >>>>> done quite some work, and many other people as well. >>>>> My question is.... have we decreased the effort to keep it working as >>>>> Pharo evolves? Previously, there were always problems with the >>>>> dependencies: a single commit to Pharo would add or break a dependency and >>>>> so we cannot bootstrap anymore. In other words...there was still a lot of >>>>> human action needed to check and fix dependencies. Is this still the case? >>>>> >>>> >>>> Complex questions requires complex answers :). It's not a yes, neither >>>> a no. >>>> >>>> - We have automatized the dependency analyses >>>> - We added Lint rules that ensure that no new dependencies are added to >>>> the kernel because of an integration >>>> - We will be adding soon enough more tools to automatically validate >>>> and ensure the health of the bootstrap, and to detect possible problems. >>>> >>>> Buuut, >>>> >>>> - Lint rules can (and sometimes are) ignored >>>> - Not everybody is aware of how to maintain dependencies or even they >>>> do not know they should care about it >>>> >>>> So the human factor is still of big importance (and risk), and >>>> educating people is harder than machines ^^ >>>> >>> >>> I must say that current need of human work required for proper reloading >>> of all Pharo packages is too high. It can be better only as soon as the >>> bootstrapping will be part of our development/release process. >>> >> >> Exactly!!! Totally agree. And..what are the plans of getting the >> bootstrapping as part of the development and release process? I am sure it >> is on the roadmap. >> > > Simply as soon as possible :-) I will work on preparation of it in the > next weeks. > > -- Pavel > > >> >> >>> >>> On the other hand, dependency problems are now quite rare and are very >>> rare in the kernel packages. >>> >>> >> That's very good to hear! >> >> >>> -- Pavel >>> >>> >>>> >>>> >>>>> Cheers, >>>>> >>>>> >>>>> >>>>> On Fri, Jul 22, 2016 at 10:37 AM, Pavel Krivanek < >>>>> pavel.krivanek(a)gmail.com> wrote: >>>>> >>>>>> >>>>>> >>>>>> 2016-07-22 15:22 GMT+02:00 Ben Coman <btc(a)openinworld.com>: >>>>>> >>>>>>> On Fri, Jul 22, 2016 at 9:12 PM, Pavel Krivanek >>>>>>> <pavel.krivanek(a)gmail.com> wrote: >>>>>>> > Hi, >>>>>>> > >>>>>>> > as you maybe know, we are working on Pharo image bootstrap - the >>>>>>> process >>>>>>> > that can generate an image from source codes and initialize it >>>>>>> correctly. >>>>>>> > Because of practical reasons we do not bootstrap the standard >>>>>>> image at once >>>>>>> > but we are trying to bootstrap a small headless kernel image and >>>>>>> then load >>>>>>> > the rest of the system into it. >>>>>>> > >>>>>>> > The good news is that we are successful in our effor. We are >>>>>>> already able to >>>>>>> > produce well usable images as you can test here: >>>>>>> >>>>>>> Great to hear of your continuing progress. >>>>>>> >>>>>>> > >>>>>>> > https://goo.gl/fn1VbP >>>>>>> > >>>>>>> > From the Pharo/Squeak point of view this image is very special >>>>>>> because it >>>>>>> > doesn't contain any object inherited from 70's. Pharo lost its >>>>>>> umbilical >>>>>>> > cord. >>>>>>> >>>>>>> Does this mean you are starting with a zero byte file and adding nil, >>>>>>> true, false, etc...? >>>>>>> Or what is the size of the image you start with? >>>>>>> >>>>>> >>>>>> No, we are not generating image file directly. We use special VM >>>>>> simulator and then save its object memory. >>>>>> Our bootstrapped image has about 5MB now (in Spur format). >>>>>> >>>>>> >>>>>>> >>>>>>> cheers -ben >>>>>>> >>>>>>> > >>>>>>> > Notice that the initial display width is too narrow and and we >>>>>>> still need a >>>>>>> > lot of work on the building process, but In the next weeks and >>>>>>> months it >>>>>>> > will change a lot the Pharo development - especially as soon as it >>>>>>> will be >>>>>>> > combined with Git support. >>>>>>> > >>>>>>> > Cheers, >>>>>>> > -- Pavel >>>>>>> > >>>>>>> > >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Mariano >>>>> http://marianopeck.wordpress.com >>>>> >>>> >>>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > >

July 22, 2016