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

Hi Guillermo - its 64bit I’m after for running AWS Lambda - the metacello version at 10mb looks very interesting (as the one I’m using from build #27 is 15mb). However, given I’m trying to find a stable place where I can develop on Pharo 6.1 and get a bit more experience - it looks like the

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

Hi Tim, in the file server: http://files.pharo.org/image/70/ You can get now latest 32 bit builds in many flavours: - compiler (basic pharo image with just a compiler) - core (compiler + package initialization) - monticello bootstrap (core + basic monticello packages -- no network here!) -

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

Hey thanks again - it looks like that file is from Build #25 (I think Jenkins might cache the last 5 builds from the looks of it). Interestingly that image is 2mb smaller than the later ones (which is helpful) - however when I try to use it, I get a walkback because Metacello wasn’t available

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

Unfortunately we store minimal versions only for the latest build and you should use older build with hash b1625bf32c6b2b6c6f8babb789e377af5132d740. You can download this image here (I have found a random copy of it): https://drive.google.com/open?id=0BzSsmZhqtUTeclFEbDhtd0JvdEk Copy it to some

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

Thanks Pavel - as I’m downloading: curl -L -o min.zip https://ci.inria.fr/pharo/job/70-Bootstrap-32bit-Conversion/lastSuccessfulBuild/artifact/latest-minimal-64.zip I noted that

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

2017-08-07 12:56 GMT+02:00 Tim Mackinnon : > I’ve just switched branches and diffed - and yep, those methods were the > difference. Sorry about the extra noise on that - I should have read your > instructions a bit better - still I’ve learned a lot doing this, and am > really

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

I’ve just switched branches and diffed - and yep, those methods were the difference. Sorry about the extra noise on that - I should have read your instructions a bit better - still I’ve learned a lot doing this, and am really chuffed that I’ve managed to get something working. I’m looking at

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

yes, because master branch contains code of Pharo 6. For Pharo 7 we have flattened the traits in the kernel, but this is probably the only difference that affects Fuel packages -- Pavel 2017-08-04 20:32 GMT+02:00 Tim Mackinnon : > Ah - I checked out master. So should I have

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

Ah - I checked out master. So should I have checked out dev? Would this explain it? I've appreciated the help a lot by the way. Tim Sent from my iPhone > On 4 Aug 2017, at 17:28, Pavel Krivanek wrote: > > It it were packages from the development branch then you do

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

It it were packages from the development branch then you do not need to flatten them. -- Pavel 2017-08-04 15:52 GMT+02:00 Tim Mackinnon : > Hi Pavel - When you say “packages from the Pharo repo” - I think I’m doing > that - yesterday I cloned the Pharo repo and then I copied

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

Hi Pavel - When you say “packages from the Pharo repo” - I think I’m doing that - yesterday I cloned the Pharo repo and then I copied the Fuel packages you guys suggested over into my branch (not elegant, but simple). So I should have the flattened versions then? (I have now managed to get the

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

Hi - I was actually reading those slides the other day, but hadn’t fully appreciated the consequences… that is very cool - and definitely something for me to put on the stack of things to try out I was going to say I could put the Fuel and S3 access into such a library - but then I would need

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

On Fri, Aug 4, 2017 at 9:51 AM, Tim Mackinnon wrote: > HURRAH - I got it to work, and Fuel out an error to S3 and read it back > into a fat 6.1 image with a debug stack (which is so cool!). > > COOOL!!! I want to see your blogpost once you make it!!! Congratulations, this was

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

HURRAH - I got it to work, and Fuel out an error to S3 and read it back into a fat 6.1 image with a debug stack (which is so cool!). My footprint size is still a bit larger than I would like (31mb - image of 22.7mb - of which 1mb if fuel and 7mb is S3 and XMLParser support) - so I guess I need

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

Hmm, Pharo 7 has flattened traits in the kernel, but it still supports them. So probably because you are using vanilla Fuel packages, they extend traits that are not used for real. You should use packages from the Pharo repository. -- Pavel 2017-08-04 13:42 GMT+02:00 Tim Mackinnon

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

On Fri, Aug 4, 2017 at 8:42 AM, Tim Mackinnon wrote: > Sadly - false call, that was my logging message - so I’m stumped why these > traits aren’t being compiled when I load in Fuel? > > However I have figured out why I get the BigEndian error - this is because > the platform is

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

Sadly - false call, that was my logging message - so I’m stumped why these traits aren’t being compiled when I load in Fuel? However I have figured out why I get the BigEndian error - this is because the platform is now 7 and so the FlPharo06Platform is not being identified and the more

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

I’ve spotted something interesting in my logs - when I added one of the missing methods to ClassDescription - I see in the log the message: Loaded -> Fuel-cypress.1 --- filetree:///builds/macta/PharoLambda/bootstrap --- cache ...finished baseline Compiling missing traits... Evaluating post load

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

Actually there is something weird going on - as now I’m getting a complaint about "FLPharoPlatform had the subclass responsibility to implement #isBigEndian”, and that’s in the FuelPlatform-Pharo-06 which you said to include (and it looks like I am). I need to double check this - as I must be

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

Hi Mariano - I’ve looked at this again, and it was my fault - I was compiling in : fuelAccept: aGeneralMapper ^self explicitRequirement. Because when I looked at the Traits for fuel - this is what it had for TClass? - as I’m not so clear on traits, what does this mean - as I had just

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

If Traits are supported then I must be doing something else wrong - maybe load order? (To be honest, I don’t fully understand how traits work - but I will keep digging). It could be that my latest error (having just done Class compile: ‘…. Missing method code … ‘) is something deeper related

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

2017-08-03 18:17 GMT+02:00 Tim Mackinnon : > Hi guys - I think I’m getting close - I’m able to load remote packages, > and I’ve added fuel to my repo and its loading - however I am getting an > error when I run and test writing out a context - *MessageNotUnderstood: > Context

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

On Thu, Aug 3, 2017 at 2:14 PM, Tim Mackinnon wrote: > Hi Mariano - I compiled in the trait methods manually and it got further - > but now I’m seeing another error - Error: Explicitly required method", > "\u001b[0mLambda class(Object)>>error:", > "explicitRequirement”,

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

Hi Mariano - I compiled in the trait methods manually and it got further - but now I’m seeing another error - Error: Explicitly required method", "\u001b[0mLambda class(Object)>>error:", "explicitRequirement”, Any ideas? Tim "--- RUNNING ERROR HANDLER ---", "Error: Explicitly

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

On Thu, Aug 3, 2017 at 1:17 PM, Tim Mackinnon wrote: > Hi guys - I think I’m getting close - I’m able to load remote packages, > and I’ve added fuel to my repo and its loading - however I am getting an > error when I run and test writing out a context - *MessageNotUnderstood: >

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

Hi guys - I think I’m getting close - I’m able to load remote packages, and I’ve added fuel to my repo and its loading - however I am getting an error when I run and test writing out a context - MessageNotUnderstood: Context class>>fuelIgnoredInstanceVariableNames I can see that this is a

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

On Thu, Aug 3, 2017 at 8:58 AM, Tim Mackinnon wrote: > I’m so close now (bit of a diversion with gitlab yml not liking the eval > string) - that did load and it got me really close - I’m just missing > FlSerializer now (I have progressed my work to fuel out the context for >

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

2017-08-03 13:58 GMT+02:00 Tim Mackinnon : > I’m so close now (bit of a diversion with gitlab yml not liking the eval > string) - that did load and it got me really close - I’m just missing > FlSerializer now (I have progressed my work to fuel out the context for > debugging to

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

I’m so close now (bit of a diversion with gitlab yml not liking the eval string) - that did load and it got me really close - I’m just missing FlSerializer now (I have progressed my work to fuel out the context for debugging to S3)… so looking at the repo, there are quite a few fuel packages -

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

2017-08-03 13:02 GMT+02:00 Tim Mackinnon : > I really appreciate your patience and help on this - it looks very > promising and I am giving it a spin now… > > When you say the pharo repository - are you referring to this: > https://github.com/pharo-project/pharo/tree/master/src.

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

I really appreciate your patience and help on this - it looks very promising and I am giving it a spin now… When you say the pharo repository - are you referring to this: https://github.com/pharo-project/pharo/tree/master/src . ? Just so

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

2017-08-03 10:14 GMT+02:00 Pavel Krivanek : > The easiest think you can do is to copy to your repository (or some other) > related packages from the Pharo repository (to do not have to clone it all): > > Metacello-GitBasedRepository.package > Metacello-GitHub.package >

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

The easiest think you can do is to copy to your repository (or some other) related packages from the Pharo repository (to do not have to clone it all): Metacello-GitBasedRepository.package Metacello-GitHub.package SUnit-Core.package and create baseline to load them. I already tried it so you can

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

As an aside, I’ve just noticed that I get the same error in a normal 6.1 image when you try to load a baselineof package in Iceberg using the install menu option. So I wonder if this might actually be a bug in the image that the minimal version is getting as well? Tim > On 1 Aug 2017, at

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

Ah, I think I’m starting to get closer to what I need… So if I want to load in that last piece to enable more general remote loading - how do I figure out how to do that? I’m trying to work out where the build steps for building up the image (can I see them in Jenkins? It wasn’t clear to me if

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

Yes, you should be able to load an mcz in that image by doing: (MCDirectoryRepository new directory: 'where-your-mcz-is') loadVersionFromFileNamed: 'Metacello-GitBasedRepository-Author.1.mcz') load. Guille On Wed, Aug 2, 2017 at 7:57 AM, Pavel Krivanek wrote: > >

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

2017-08-01 23:13 GMT+02:00 Tim Mackinnon : > Hi Pavel - I tried it again and the problem is do with Metacello > dependencies in your baseline. > > The SUnit baseline doesn’t specify any additional dependencies to load (it > just loads local packages), whereas my baseline that

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

Hi Pavel - I tried it again and the problem is do with Metacello dependencies in your baseline. The SUnit baseline doesn’t specify any additional dependencies to load (it just loads local packages), whereas my baseline that fails looks like this: baseline: spec spec for:

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

2017-07-31 22:51 GMT+02:00 Tim Mackinnon : > I wasn’t clear on which image to retry - the https://ci.inria.fr/pharo/ > job/Pharo-6.0-Update-Step-3.2-Minimal/lastSuccessfulBuild/ > artifact/Pharo-minimal-64.zip one still shows as being last updated 7 > days ago. > > The