July 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Creating the smallest server runtime footprint

by Pavel Krivanek

If you want to stay with Pharo 6 image, you can try the bootstrapped version of the minimal image: https://ci.inria.fr/pharo/view/6.0-SysConf/job/Pharo-6.0-Step-04-01-Configu… -- Pavel 2017-07-15 10:33 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > Try the Pharo 7 metacello image (=Pharo 7 minimal image that the CI is > already converting to 64bit). There should be no problem with STON because > whole Pharo is loaded into it using metacello and filetree. Pharo 6 minimal > image is done differently (by shrinking) and not so well tested. > > For the conversion of 32-bit image to 64-bit image you need a VMMaker > image: > https://ci.inria.fr/pharo/job/Spur-Git-Tracker/ > lastSuccessfulBuild/artifact/vmmaker-image.zip > and then evaluate: > ./pharo generator.image eval "[Spur32to64BitBootstrap new bootstrapImage: > 'conversion.image'] on: AssertionFailure do: [ :fail | fail > resumeUnchecked: nil ]" > > -- Pavel > > > > 2017-07-15 10:19 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > >> Hi Pavel - thanks for getting me to the point where I could even have a >> minimal image. As Iâm on the edge of my Pharo knowledge here, Iâll try and >> run with this as best I can. >> >> Iâd been using the 6.0 image you suggested to me - but maybe I could use >> a 70 image with Pharo 6 for a while (until the VM diverges) right? >> >> The bit I havenât quite understood however, is how the 64bit image is >> created - as your reference is to a 32bit version? Is the 64bit one >> converted from 32 in a later stage? (For AWS Lambda I need 64bit) - am I >> right in thinking the pipeline stage after this one is the one you sent me >> - and the travis.yml file shows me what it does? But I canât see a >> trivis.yml in the conversion stage so Iâm not sure how it does that. >> (Question - how do I see what the pipelines do to answer my own questions?) >> >> I was hoping that there was a basic image that got me up to metacello >> baseline level to load git file tree packages/baselines in my own repo as >> well baselines on the internet. The one you sent me is fairly close to that >> (its just missing STON in the image and seems to have an issue with >> resolving undeclared classes that get loaded in - should do a fogbugz on >> that?) >> >> The follow-on from a metacello image is how we can get people to create >> better baselines that give you more minimal loading options (e.g. >> conditionally leave out the test cases perhaps) >> >> Tim >> >> On 15 Jul 2017, at 08:24, Pavel Krivanek <pavel.krivanek(a)gmail.com> >> wrote: >> >> Hi Tim, >> >> you can base the your work on the bootstrapped image, see >> https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/, file >> Pharo7.0-core-*.zip >> >> This image does not have a lot of basic components like Monticello or >> network but it has a compiler so the code can be imported as *.st files. >> Then we have Pharo7.0-monticello-*.zip which will be easier to use and >> probably can fit your needs. Monticello and network support are included. >> But you cannot use baselines nor configurations to load your code. >> >> -- Pavel >> >> 2017-07-14 9:59 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: >> >>> Hi - buoyed by the success of a minimal image (thanks Pavel), I'm >>> wondering if I can get even smaller. >>> >>> There are lots of .so's in the vm which wouldn't make sense on a server >>> once deployed - sound, maybe libgit ... >>> >>> Is there a list of the essential ones, or tips on what I can strip out >>> of the Linux deployment? I also recall that i can leave out .sources and >>> .changes as well right? >>> >>> Tim >>> >>> Sent from my iPhone >>> >>> >> >> >

July 15, 2017

Re: [Pharo-users] Creating the smallest server runtime footprint

by Pavel Krivanek

Try the Pharo 7 metacello image (=Pharo 7 minimal image that the CI is already converting to 64bit). There should be no problem with STON because whole Pharo is loaded into it using metacello and filetree. Pharo 6 minimal image is done differently (by shrinking) and not so well tested. For the conversion of 32-bit image to 64-bit image you need a VMMaker image: https://ci.inria.fr/pharo/job/Spur-Git-Tracker/lastSuccessfulBuild/artifact… and then evaluate: ./pharo generator.image eval "[Spur32to64BitBootstrap new bootstrapImage: 'conversion.image'] on: AssertionFailure do: [ :fail | fail resumeUnchecked: nil ]" -- Pavel 2017-07-15 10:19 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > Hi Pavel - thanks for getting me to the point where I could even have a > minimal image. As Iâm on the edge of my Pharo knowledge here, Iâll try and > run with this as best I can. > > Iâd been using the 6.0 image you suggested to me - but maybe I could use a > 70 image with Pharo 6 for a while (until the VM diverges) right? > > The bit I havenât quite understood however, is how the 64bit image is > created - as your reference is to a 32bit version? Is the 64bit one > converted from 32 in a later stage? (For AWS Lambda I need 64bit) - am I > right in thinking the pipeline stage after this one is the one you sent me > - and the travis.yml file shows me what it does? But I canât see a > trivis.yml in the conversion stage so Iâm not sure how it does that. > (Question - how do I see what the pipelines do to answer my own questions?) > > I was hoping that there was a basic image that got me up to metacello > baseline level to load git file tree packages/baselines in my own repo as > well baselines on the internet. The one you sent me is fairly close to that > (its just missing STON in the image and seems to have an issue with > resolving undeclared classes that get loaded in - should do a fogbugz on > that?) > > The follow-on from a metacello image is how we can get people to create > better baselines that give you more minimal loading options (e.g. > conditionally leave out the test cases perhaps) > > Tim > > On 15 Jul 2017, at 08:24, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Hi Tim, > > you can base the your work on the bootstrapped image, see > https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/, file > Pharo7.0-core-*.zip > > This image does not have a lot of basic components like Monticello or > network but it has a compiler so the code can be imported as *.st files. > Then we have Pharo7.0-monticello-*.zip which will be easier to use and > probably can fit your needs. Monticello and network support are included. > But you cannot use baselines nor configurations to load your code. > > -- Pavel > > 2017-07-14 9:59 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > >> Hi - buoyed by the success of a minimal image (thanks Pavel), I'm >> wondering if I can get even smaller. >> >> There are lots of .so's in the vm which wouldn't make sense on a server >> once deployed - sound, maybe libgit ... >> >> Is there a list of the essential ones, or tips on what I can strip out of >> the Linux deployment? I also recall that i can leave out .sources and >> .changes as well right? >> >> Tim >> >> Sent from my iPhone >> >> > >

July 15, 2017

Re: [Pharo-users] Creating the smallest server runtime footprint

by Tim Mackinnon

Hi Pavel - thanks for getting me to the point where I could even have a minimal image. As Iâm on the edge of my Pharo knowledge here, Iâll try and run with this as best I can. Iâd been using the 6.0 image you suggested to me - but maybe I could use a 70 image with Pharo 6 for a while (until the VM diverges) right? The bit I havenât quite understood however, is how the 64bit image is created - as your reference is to a 32bit version? Is the 64bit one converted from 32 in a later stage? (For AWS Lambda I need 64bit) - am I right in thinking the pipeline stage after this one is the one you sent me - and the travis.yml file shows me what it does? But I canât see a trivis.yml in the conversion stage so Iâm not sure how it does that. (Question - how do I see what the pipelines do to answer my own questions?) I was hoping that there was a basic image that got me up to metacello baseline level to load git file tree packages/baselines in my own repo as well baselines on the internet. The one you sent me is fairly close to that (its just missing STON in the image and seems to have an issue with resolving undeclared classes that get loaded in - should do a fogbugz on that?) The follow-on from a metacello image is how we can get people to create better baselines that give you more minimal loading options (e.g. conditionally leave out the test cases perhaps) Tim > On 15 Jul 2017, at 08:24, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Hi Tim, > > you can base the your work on the bootstrapped image, see https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/ <https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/>, file Pharo7.0-core-*.zip > > This image does not have a lot of basic components like Monticello or network but it has a compiler so the code can be imported as *.st files. > Then we have Pharo7.0-monticello-*.zip which will be easier to use and probably can fit your needs. Monticello and network support are included. But you cannot use baselines nor configurations to load your code. > > -- Pavel > > 2017-07-14 9:59 GMT+02:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: > Hi - buoyed by the success of a minimal image (thanks Pavel), I'm wondering if I can get even smaller. > > There are lots of .so's in the vm which wouldn't make sense on a server once deployed - sound, maybe libgit ... > > Is there a list of the essential ones, or tips on what I can strip out of the Linux deployment? I also recall that i can leave out .sources and .changes as well right? > > Tim > > Sent from my iPhone > >

July 15, 2017

Re: [Pharo-users] Creating the smallest server runtime footprint

by Pavel Krivanek

Hi Tim, you can base the your work on the bootstrapped image, see https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/, file Pharo7.0-core-*.zip This image does not have a lot of basic components like Monticello or network but it has a compiler so the code can be imported as *.st files. Then we have Pharo7.0-monticello-*.zip which will be easier to use and probably can fit your needs. Monticello and network support are included. But you cannot use baselines nor configurations to load your code. -- Pavel 2017-07-14 9:59 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > Hi - buoyed by the success of a minimal image (thanks Pavel), I'm > wondering if I can get even smaller. > > There are lots of .so's in the vm which wouldn't make sense on a server > once deployed - sound, maybe libgit ... > > Is there a list of the essential ones, or tips on what I can strip out of > the Linux deployment? I also recall that i can leave out .sources and > .changes as well right? > > Tim > > Sent from my iPhone > >

July 15, 2017

Re: [Pharo-users] Creating the smallest server runtime footprint

by Tim Mackinnon

Hi - the script I'm using is in https://gitlab.com/macta/PharoLambda - it's nothing fancy, look at the Gitlab .yml file. This is all Linux running in an ubuntu docker image on Gitlab CI. Tim Sent from my iPhone Sent from my iPhone > On 15 Jul 2017, at 06:27, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Hi Tim, > > 2017-07-14 4:59 GMT-03:00 Tim Mackinnon <tim(a)testit.works>: >> Hi - buoyed by the success of a minimal image (thanks Pavel), I'm wondering if I can get even smaller. > > Can you share a script to reproduce the steps to build a minimal image? > > Is it reproducible under Windows? > > Cheers, > > HernÃ¡n >

July 15, 2017

Re: [Pharo-users] Understanding DateTime and Locale and formatting times in a locale?

by Sven Van Caekenberghe

Hi Tim, Great that you found this out. You can also use the 'by-example formatter/parser'. ZTimestampFormat verbose timezone: (ZTimezone id: 'America/Halifax'); format: ZTimestamp now. => 'Saturday, 15-July-2017 04:04:12 AM (-03:00)' (ZTimestampFormat fromString: 'Sat, 03 February 2001 04:05:06 PM') timezone: (ZTimezone id: 'America/Halifax'); format: ZTimestamp now. => 'Sat, 15 July 2017 04:04:18 AM' The idea is that you create a format instance once and keep using it. Sven PS: Check the class comment! > On 15 Jul 2017, at 01:57, Tim Mackinnon <tim(a)testit.works> wrote: > > Classic - the moment you write something, it suddenly dawns on youâ¦ its the other way around. > > (ZTimezone id: 'America/Halifaxâ) gmtToLocal: ZTimestamp nowâ¦ > > Tim > >> On 15 Jul 2017, at 00:34, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Thanks for chipping in - but its the other way around that Iâm after. >> >> I am looking at ZTimestamp now -but again I donât quite get it? >> >> ZTimestamp now gives me a timestamp in UTC (great) but how do I format it to show it in say Canadian time? >> >> I thought it would be something like: >> >> ZTimestamp now printOn: stream timezone: (ZTimezone id: 'America/Halifaxâ) but it doesnât seem to be that? >> >> I must be missing something. >> >> Tim >> >>> On 14 Jul 2017, at 23:28, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> Have a look at #asLocal >>> >>> Norbert >>> >>>> Am 14.07.2017 um 23:04 schrieb Tim Mackinnon <tim(a)testit.works>: >>>> >>>> Hi - Iâm really confused about DateAndTime support in Pharo? >>>> >>>> If I have a server app running in the EU, and a user makes a request from Canada, and I want to format the time they see to be in their timezone - how do I do that with the classes in Pharo? >>>> >>>> I can ask for a DataAndTime nowUTC, and if I know the user is in en-CA, I can create a Locale for them - but then how do I get the correct time offset, or how to I format that UTC date in their locale? >>>> >>>> Tim >>> >> >> > >

July 15, 2017

Re: [Pharo-users] [ANN] PharoLambda a demo of Pharo running on AWS Lambda

by Tudor Girba

Nice job! Doru > On Jul 15, 2017, at 1:43 AM, Tim Mackinnon <tim(a)testit.works> wrote: > > Things move fast, I already got a shout out from an AWS advocate - https://twitter.com/chrismunns/status/885959425860808704 > > Tim > >> On 15 Jul 2017, at 00:39, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi - Iâve been playing around with getting Pharo to run well on AWS Lambda. Itâs early days, but I though it might be interesting to share what Iâve learned so far. >> >> Usage examples and code at https://gitlab.com/macta/PharoLambda >> >> With help from many of the folks here, Iâve been able to get a simple example to run in 500ms-1200ms with a minimal Pharo 6 image. You can easily try it out yourself. This seems slightly better than what the GoLang folks have been able to do. >> >> Tim > -- www.tudorgirba.com www.feenk.com "Every thing has its own flow."

July 15, 2017

Re: [Pharo-users] Creating the smallest server runtime footprint

by HernÃ¡n Morales Durand

Hi Tim, 2017-07-14 4:59 GMT-03:00 Tim Mackinnon <tim(a)testit.works>: > Hi - buoyed by the success of a minimal image (thanks Pavel), I'm > wondering if I can get even smaller. > > Can you share a script to reproduce the steps to build a minimal image? Is it reproducible under Windows? Cheers, HernÃ¡n

July 15, 2017

Re: [Pharo-users] Creating the smallest server runtime footprint

by Pierce Ng

On Fri, Jul 14, 2017 at 09:06:44AM +0100, Tim Mackinnon wrote: > Related to this question - in the Linux vm there are several .so files that > have numerical extensions as well as the same named .so file. Are these merge > conflicts or platform variations of the same files? > > libSDL2-2.0.so.0.4.1 & libSDL2-2.0.so & libSDL2.so They are the same files, typically sym-links. Pierce

July 15, 2017

Re: [Pharo-users] Understanding DateTime and Locale and formatting times in a locale?

by Tim Mackinnon

Classic - the moment you write something, it suddenly dawns on youâ¦ its the other way around. (ZTimezone id: 'America/Halifaxâ) gmtToLocal: ZTimestamp nowâ¦ Tim > On 15 Jul 2017, at 00:34, Tim Mackinnon <tim(a)testit.works> wrote: > > Thanks for chipping in - but its the other way around that Iâm after. > > I am looking at ZTimestamp now -but again I donât quite get it? > > ZTimestamp now gives me a timestamp in UTC (great) but how do I format it to show it in say Canadian time? > > I thought it would be something like: > > ZTimestamp now printOn: stream timezone: (ZTimezone id: 'America/Halifaxâ) but it doesnât seem to be that? > > I must be missing something. > > Tim > >> On 14 Jul 2017, at 23:28, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> Have a look at #asLocal >> >> Norbert >> >>> Am 14.07.2017 um 23:04 schrieb Tim Mackinnon <tim(a)testit.works>: >>> >>> Hi - Iâm really confused about DateAndTime support in Pharo? >>> >>> If I have a server app running in the EU, and a user makes a request from Canada, and I want to format the time they see to be in their timezone - how do I do that with the classes in Pharo? >>> >>> I can ask for a DataAndTime nowUTC, and if I know the user is in en-CA, I can create a Locale for them - but then how do I get the correct time offset, or how to I format that UTC date in their locale? >>> >>> Tim >> > >

July 14, 2017