June 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Fuel Error in Latest Launcher

by Sean P. DeNigris

Eliot Miranda-2 wrote > Looks like the bug is that Fuel isâ¦ Ah, glad we identified it! Where should this bug be reported? https://github.com/theseion/Fuel/issues ? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

June 21, 2018

Re: [Pharo-dev] Fuel Error in Latest Launcher

by Eliot Miranda

Hi Sean, > On Jun 21, 2018, at 5:48 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Max Leske wrote >> if you discovered a compiler >> bug it would help to post the information. > > I'm not sure if it's a bug, but here is the info I know: > 1. Serialized a block in #60540 32-bit > 2. Materialized it in same version 64-bit and it was "broken", i.e.: > a. It can't be serialized again as indicated above > b. Strangely, its print string in the GT Inspector is the entire source > code of #outerContext instead of the source code of just the block Looks like the bug is that Fuel is not adjusting the pcs in Contexts and BlockClosures when loading something saved in a different word size. CompiledCode (CompiledMethod & CompiledBlock) is a hybrid object, the first part being object references (the methodâs header followed by its literals), the second part being bytes (the bytecodes for the method and any additional info encoded in trailing bytes). So in 32 bits a pc is (4*numLiterals+1) less than it is in 64 bits, and Fuel and other code must adjust things accordingly. See CompiledCode>>#initialPC > > aBlock: > - The following instVars are the same in both images: startup = 56, numArgs > = 1 > - outerContext also seems the same, with the only obvious exception that the > #method bytecodes are not all the same > - sender = nil > - pc = 45 > - method = (SmallBaselineLoadScript>>#descriptionConflictBlock) > - closureOrNil = nil > - receiver = aSmallBaselineLoadScript > > Let me know if you would like any more infoâ¦ > > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

June 21, 2018

ESUG 2018 Innovation Technology Awards: Call for Submissions

by N. Bouraqadi

Dear fellow Smalltalkers, The 15th edition of the ESUG Innovation Technology Awards is now officially open. As for every year, you can submit software based on any Smalltalk flavor, to attempt to win one of the three prizes. All you have to do is to provide a 3-5min video demo. More info and a link to the submission server is at: https://esug.github.io/2018-Conference/awardsCall2018.html On behalf of the ESUG board, Noury -- http://twitter.com/#!/NouryBouraqadi http://car.imt-lille-douai.fr/noury

June 21, 2018

Re: [Pharo-dev] Fuel Error in Latest Launcher

by Sean P. DeNigris

Max Leske wrote > if you discovered a compiler > bug it would help to post the information. I'm not sure if it's a bug, but here is the info I know: 1. Serialized a block in #60540 32-bit 2. Materialized it in same version 64-bit and it was "broken", i.e.: a. It can't be serialized again as indicated above b. Strangely, its print string in the GT Inspector is the entire source code of #outerContext instead of the source code of just the block aBlock: - The following instVars are the same in both images: startup = 56, numArgs = 1 - outerContext also seems the same, with the only obvious exception that the #method bytecodes are not all the same - sender = nil - pc = 45 - method = (SmallBaselineLoadScript>>#descriptionConflictBlock) - closureOrNil = nil - receiver = aSmallBaselineLoadScript Let me know if you would like any more infoâ¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

June 21, 2018

[Pharo 7.0-dev] Build #1080: 22179-remove-annotateRubricText-

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1080 was: SUCCESS. The Pull Request #1576 was integrated: "22179-remove-annotateRubricText-" Pull request url: https://github.com/pharo-project/pharo/pull/1576 Issue Url: https://pharo.fogbugz.com/f/cases/22179 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 21, 2018

[Pharo 7.0-dev] Build #1079: 22179-remove-annotateRubricText-

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1079 was: FAILURE. The Pull Request #1576 was integrated: "22179-remove-annotateRubricText-" Pull request url: https://github.com/pharo-project/pharo/pull/1576 Issue Url: https://pharo.fogbugz.com/f/cases/22179 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 21, 2018

Re: [Pharo-dev] Minimal kernel

by Guido Chari

Ok, yes, I was totally confused. Sorry for that, thanks for the explanation. Now, I guess this is more for Guille. I follow the instructions for building the image and I get: ...RETRY->BaselineOfPharoBootstrapProcess ...RETRY->BaselineOfPharoBootstrapProcess ...FAILED->BaselineOfPharoBootstrapProcessCould not resolve: BaselineOfPharoBootstrapProcess [BaselineOfPharoBootstrapProcess] in /Users/guidochari/Documents/Projects/Research/Nopsys/CogNOS/image/pharo-local/package-cache filetree:///Users/guidochari/Documents/Projects/Research/Nopsys/PharoBootstrap I then resort to just execute the command that travis executes ( ./scripts/install-packages.sh) and it works. But when I open the image I can not find PBBootstrapSpur3250. Best, Guido El jue., 21 jun. 2018 a las 10:41, Esteban Lorenzano (<estebanlm(a)gmail.com>) escribiÃ³: > > > On 21 Jun 2018, at 10:28, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > On 21 Jun 2018, at 10:20, Guido Chari <charig(a)gmail.com> wrote: > > Seriously? Are you talking about the README of this repo > https://github.com/pharo-project/pharo-minimal-scripts? > > > yes, seriously. > Iâm talking about the readme of pharo: > Bootstrapping Pharo from sources > > To bootstrap a new Pharo image you need the latest stable version of > Pharo. For more information about bootstrapping, refer to > guillep/PharoBootstrap <https://github.com/guillep/PharoBootstrap>. > > The bootstrapping can be done using the following script: > > BUILD_NUMBER=42 BOOTSTRAP_ARCH=32 sh ./bootstrap/scripts/bootstrap.sh > > > > and btw, just in case this quote of the README on pharo-minimal-scripts is > not clear : > > This repository keeps the files needed to prepare the Pharo-minimal > images, a shrink process that is executed by the CI service, you can find > it here <https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-3-Minimal>. > > that means is not a bootstrap process, is a *shrink* process (which is > what we had before having a real bootstrap). > now, I agree people who didnât read the pharo README first can be > miss-leaded, so I will add a note to clarify this is obsolete. > > cheers, > Esteban > > > > > > El jue., 21 jun. 2018 a las 10:02, Esteban Lorenzano (<estebanlm(a)gmail.com>) > escribiÃ³: > >> >> >> On 21 Jun 2018, at 09:18, Guido Chari <charig(a)gmail.com> wrote: >> >> >> >> El lun., 11 jun. 2018 a las 21:25, HernÃ¡n Morales Durand (< >> hernan.morales(a)gmail.com>) escribiÃ³: >> >>> Hi Pablo, >>> >>> 2018-06-11 6:06 GMT-03:00 tesonep(a)gmail.com <tesonep(a)gmail.com>: >>> > You can execute the bootstrap process. >>> >>> How you do that? >>> >> >> Yes, I am wondering the same. >> >> >> guys, is written in the README (I donât want to be rude, but that would >> be RTFM ;) ) >> now *after* that, there can be problems. We will be pleased to hear about >> them and help :) >> >> cheers! >> Esteban >> >> >> Is it any documentation on how to run the bootstrap process? In my case I >> need an image that is functional, but as small as possible. >> >> >>> >>> > However, maybe that is not required, as the bootstrapped images for >>> Pharo7 >>> > are stored. >>> > >>> > >>> > These are the latest (always): >>> > >>> > Compiler: >>> > >>> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… >>> > Compiler + Traits: >>> > >>> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… >>> > >>> >>> Both links return a: >>> >>> Problem accessing >>> >>> /pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/lastSuccessfulBuild/artifact/bootstrap-cache/Pharo-core-7.0.0-alpha.build.1037.sha.7fc6bdf.arch.32bit.zip. >>> Reason: >>> >>> Not Found >>> >> >> Btw, aren't the miniaml images in http://files.pharo.org/image/60/ >> usable? Is there any 64bit compatible minimal image available? >> >> >>> >>> Cheers, >>> >>> Hernan >>> >>> > These are the first images that are usable, the first one has a >>> compiler and >>> > the second adds the traits implementation. >>> > As Esteban said, you can modify the process to bootstrap whatever you >>> want. >>> > However, having an image that does not have compiler it is more >>> difficult to >>> > use. >>> > >>> > If you define better what do you call a minimal image we can help you >>> more. >>> > >>> > Cheers, >>> > Pablo >>> > >>> > >>> > On Mon, Jun 11, 2018 at 10:30 AM, Guido Chari <charig(a)gmail.com> >>> wrote: >>> >> >>> >> Hi, >>> >> >>> >> Is there any way to build a minimal (kernel) pharo image or at least >>> some >>> >> kind of small image without the whole default packages? >>> >> >>> >> Best regards, >>> >> Guido. >>> > >>> > >>> > >>> > >>> > -- >>> > Pablo Tesone. >>> > tesonep(a)gmail.com >>> >>> >> > >

June 21, 2018

Re: [Pharo-dev] Minimal kernel

by Esteban Lorenzano

> On 21 Jun 2018, at 10:28, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > >> On 21 Jun 2018, at 10:20, Guido Chari <charig(a)gmail.com <mailto:charig@gmail.com>> wrote: >> >> Seriously? Are you talking about the README of this repo https://github.com/pharo-project/pharo-minimal-scripts? <https://github.com/pharo-project/pharo-minimal-scripts?> > yes, seriously. > Iâm talking about the readme of pharo: > Bootstrapping Pharo from sources > > To bootstrap a new Pharo image you need the latest stable version of Pharo. For more information about bootstrapping, refer to guillep/PharoBootstrap <https://github.com/guillep/PharoBootstrap>. > > The bootstrapping can be done using the following script: > > BUILD_NUMBER=42 BOOTSTRAP_ARCH=32 sh ./bootstrap/scripts/bootstrap.sh > and btw, just in case this quote of the README on pharo-minimal-scripts is not clear : This repository keeps the files needed to prepare the Pharo-minimal images, a shrink process that is executed by the CI service, you can find it here <https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-3-Minimal>. that means is not a bootstrap process, is a *shrink* process (which is what we had before having a real bootstrap). now, I agree people who didnât read the pharo README first can be miss-leaded, so I will add a note to clarify this is obsolete. cheers, Esteban > >> >> El jue., 21 jun. 2018 a las 10:02, Esteban Lorenzano (<estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>) escribiÃ³: >> >> >>> On 21 Jun 2018, at 09:18, Guido Chari <charig(a)gmail.com <mailto:charig@gmail.com>> wrote: >>> >>> >>> >>> El lun., 11 jun. 2018 a las 21:25, HernÃ¡n Morales Durand (<hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>>) escribiÃ³: >>> Hi Pablo, >>> >>> 2018-06-11 6:06 GMT-03:00 tesonep(a)gmail.com <mailto:tesonep@gmail.com> <tesonep(a)gmail.com <mailto:tesonep@gmail.com>>: >>> > You can execute the bootstrap process. >>> >>> How you do that? >>> >>> Yes, I am wondering the same. >> >> guys, is written in the README (I donât want to be rude, but that would be RTFM ;) ) >> now *after* that, there can be problems. We will be pleased to hear about them and help :) >> >> cheers! >> Esteban >> >> >>> Is it any documentation on how to run the bootstrap process? In my case I need an image that is functional, but as small as possible. >>> >>> >>> > However, maybe that is not required, as the bootstrapped images for Pharo7 >>> > are stored. >>> > >>> > >>> > These are the latest (always): >>> > >>> > Compiler: >>> > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> >>> > Compiler + Traits: >>> > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> >>> > >>> >>> Both links return a: >>> >>> Problem accessing >>> /pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/lastSuccessfulBuild/artifact/bootstrap-cache/Pharo-core-7.0.0-alpha.build.1037.sha.7fc6bdf.arch.32bit.zip. >>> Reason: >>> >>> Not Found >>> >>> Btw, aren't the miniaml images in http://files.pharo.org/image/60/ <http://files.pharo.org/image/60/> usable? Is there any 64bit compatible minimal image available? >>> >>> >>> Cheers, >>> >>> Hernan >>> >>> > These are the first images that are usable, the first one has a compiler and >>> > the second adds the traits implementation. >>> > As Esteban said, you can modify the process to bootstrap whatever you want. >>> > However, having an image that does not have compiler it is more difficult to >>> > use. >>> > >>> > If you define better what do you call a minimal image we can help you more. >>> > >>> > Cheers, >>> > Pablo >>> > >>> > >>> > On Mon, Jun 11, 2018 at 10:30 AM, Guido Chari <charig(a)gmail.com <mailto:charig@gmail.com>> wrote: >>> >> >>> >> Hi, >>> >> >>> >> Is there any way to build a minimal (kernel) pharo image or at least some >>> >> kind of small image without the whole default packages? >>> >> >>> >> Best regards, >>> >> Guido. >>> > >>> > >>> > >>> > >>> > -- >>> > Pablo Tesone. >>> > tesonep(a)gmail.com <mailto:tesonep@gmail.com> >>> >> >

June 21, 2018

Re: [Pharo-dev] Minimal kernel

by Esteban Lorenzano

> On 21 Jun 2018, at 10:20, Guido Chari <charig(a)gmail.com> wrote: > > Seriously? Are you talking about the README of this repo https://github.com/pharo-project/pharo-minimal-scripts? <https://github.com/pharo-project/pharo-minimal-scripts?> yes, seriously. Iâm talking about the readme of pharo: Bootstrapping Pharo from sources To bootstrap a new Pharo image you need the latest stable version of Pharo. For more information about bootstrapping, refer to guillep/PharoBootstrap <https://github.com/guillep/PharoBootstrap>. The bootstrapping can be done using the following script: BUILD_NUMBER=42 BOOTSTRAP_ARCH=32 sh ./bootstrap/scripts/bootstrap.sh > > El jue., 21 jun. 2018 a las 10:02, Esteban Lorenzano (<estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>) escribiÃ³: > > >> On 21 Jun 2018, at 09:18, Guido Chari <charig(a)gmail.com <mailto:charig@gmail.com>> wrote: >> >> >> >> El lun., 11 jun. 2018 a las 21:25, HernÃ¡n Morales Durand (<hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>>) escribiÃ³: >> Hi Pablo, >> >> 2018-06-11 6:06 GMT-03:00 tesonep(a)gmail.com <mailto:tesonep@gmail.com> <tesonep(a)gmail.com <mailto:tesonep@gmail.com>>: >> > You can execute the bootstrap process. >> >> How you do that? >> >> Yes, I am wondering the same. > > guys, is written in the README (I donât want to be rude, but that would be RTFM ;) ) > now *after* that, there can be problems. We will be pleased to hear about them and help :) > > cheers! > Esteban > > >> Is it any documentation on how to run the bootstrap process? In my case I need an image that is functional, but as small as possible. >> >> >> > However, maybe that is not required, as the bootstrapped images for Pharo7 >> > are stored. >> > >> > >> > These are the latest (always): >> > >> > Compiler: >> > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> >> > Compiler + Traits: >> > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> >> > >> >> Both links return a: >> >> Problem accessing >> /pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/lastSuccessfulBuild/artifact/bootstrap-cache/Pharo-core-7.0.0-alpha.build.1037.sha.7fc6bdf.arch.32bit.zip. >> Reason: >> >> Not Found >> >> Btw, aren't the miniaml images in http://files.pharo.org/image/60/ <http://files.pharo.org/image/60/> usable? Is there any 64bit compatible minimal image available? >> >> >> Cheers, >> >> Hernan >> >> > These are the first images that are usable, the first one has a compiler and >> > the second adds the traits implementation. >> > As Esteban said, you can modify the process to bootstrap whatever you want. >> > However, having an image that does not have compiler it is more difficult to >> > use. >> > >> > If you define better what do you call a minimal image we can help you more. >> > >> > Cheers, >> > Pablo >> > >> > >> > On Mon, Jun 11, 2018 at 10:30 AM, Guido Chari <charig(a)gmail.com <mailto:charig@gmail.com>> wrote: >> >> >> >> Hi, >> >> >> >> Is there any way to build a minimal (kernel) pharo image or at least some >> >> kind of small image without the whole default packages? >> >> >> >> Best regards, >> >> Guido. >> > >> > >> > >> > >> > -- >> > Pablo Tesone. >> > tesonep(a)gmail.com <mailto:tesonep@gmail.com> >> >

June 21, 2018

Re: [Pharo-dev] Minimal kernel

by Guido Chari

Seriously? Are you talking about the README of this repo https://github.com/pharo-project/pharo-minimal-scripts? El jue., 21 jun. 2018 a las 10:02, Esteban Lorenzano (<estebanlm(a)gmail.com>) escribiÃ³: > > > On 21 Jun 2018, at 09:18, Guido Chari <charig(a)gmail.com> wrote: > > > > El lun., 11 jun. 2018 a las 21:25, HernÃ¡n Morales Durand (< > hernan.morales(a)gmail.com>) escribiÃ³: > >> Hi Pablo, >> >> 2018-06-11 6:06 GMT-03:00 tesonep(a)gmail.com <tesonep(a)gmail.com>: >> > You can execute the bootstrap process. >> >> How you do that? >> > > Yes, I am wondering the same. > > > guys, is written in the README (I donât want to be rude, but that would be > RTFM ;) ) > now *after* that, there can be problems. We will be pleased to hear about > them and help :) > > cheers! > Esteban > > > Is it any documentation on how to run the bootstrap process? In my case I > need an image that is functional, but as small as possible. > > >> >> > However, maybe that is not required, as the bootstrapped images for >> Pharo7 >> > are stored. >> > >> > >> > These are the latest (always): >> > >> > Compiler: >> > >> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… >> > Compiler + Traits: >> > >> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… >> > >> >> Both links return a: >> >> Problem accessing >> >> /pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/lastSuccessfulBuild/artifact/bootstrap-cache/Pharo-core-7.0.0-alpha.build.1037.sha.7fc6bdf.arch.32bit.zip. >> Reason: >> >> Not Found >> > > Btw, aren't the miniaml images in http://files.pharo.org/image/60/ > usable? Is there any 64bit compatible minimal image available? > > >> >> Cheers, >> >> Hernan >> >> > These are the first images that are usable, the first one has a >> compiler and >> > the second adds the traits implementation. >> > As Esteban said, you can modify the process to bootstrap whatever you >> want. >> > However, having an image that does not have compiler it is more >> difficult to >> > use. >> > >> > If you define better what do you call a minimal image we can help you >> more. >> > >> > Cheers, >> > Pablo >> > >> > >> > On Mon, Jun 11, 2018 at 10:30 AM, Guido Chari <charig(a)gmail.com> wrote: >> >> >> >> Hi, >> >> >> >> Is there any way to build a minimal (kernel) pharo image or at least >> some >> >> kind of small image without the whole default packages? >> >> >> >> Best regards, >> >> Guido. >> > >> > >> > >> > >> > -- >> > Pablo Tesone. >> > tesonep(a)gmail.com >> >> >

June 21, 2018