Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

On Thu, Aug 17, 2017 at 8:51 PM, Alistair Grant wrote: > Hi Tim, > > On Thu, Aug 17, 2017 at 01:07:06PM +0100, Tim Mackinnon wrote: > > Just thought I would report back a bit more on this - > > > > The Unicode change doesn?t work in my case (possibly not for command > line

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Hi Tim, On Thu, Aug 17, 2017 at 01:07:06PM +0100, Tim Mackinnon wrote: > Just thought I would report back a bit more on this - > > The Unicode change doesn?t work in my case (possibly not for command line > Pharo > as well) as I get an error where OS filename?s need unicode support (actually

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Actually it looks like that extra 1.5mb is not worth having as It seems that something does end up using the class organisation and so it must recompute when the image is launched. Tim > On 17 Aug 2017, at 13:07, Tim Mackinnon wrote: > > Just thought I would report back a

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Just thought I would report back a bit more on this - The Unicode change doesn’t work in my case (possibly not for command line Pharo as well) as I get an error where OS filename’s need unicode support (actually I think this is where its trying to write to stdout, but I didn’t dig more into

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

On Wed, Aug 16, 2017 at 11:46 AM, Tim Mackinnon wrote: > Hi, tracing through your changes - it looks like: > > Smalltalk cleanUp: true except: #() confirming: false. > > Takes care of all the non-unicode changes you proposed (and it seems like > its a known cleanup protocol). >

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Hi, tracing through your changes - it looks like: Smalltalk cleanUp: true except: #() confirming: false. Takes care of all the non-unicode changes you proposed (and it seems like its a known cleanup protocol). I wonder if the Unicode change is worth it/risky as many web based services I might

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Yes - that is a fair warning - I guess I’m looking for ways to reset Monticello/metocello artefacts and caching (maybe I should ask Dale for some tips - as I find the Monticello/metacello packages quite big and difficult to follow, and there are no class comments to give you any pointers). I’m

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Be careful because some of those aggressive cleanups may turn some parts of your image unstable. For example: This is dangerous: MCMethodDefinition allInstances do: [:each | each become: String new ]. MCClassDefinition allInstances do: [:each | each become: String new ]. MCVersionInfo

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

This is very encouraging, and also very instructive (your post on snapshot is also one in this area too. I have a queue of things to try for you on Friday). I'll try adding your ideas to my script and see if it squeezes some more. And then I guess we need to to decide which parts go into your

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

This means it would be healthy to do a cleanup (at least the non aggressive one, ChangeSets and MC stuff) on each of the images we produce and not just the latest one. On Wed, Aug 16, 2017 at 8:35 AM, Tim Mackinnon wrote: > Yes you were on to something there (and at the same

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Yes you were on to something there (and at the same time, by poking around with #pointersTo I noticed some chains of objects too). So I ran the following script (partially borrowed from ImageCleaner) and this has got me down to a 14mb image (instance sizes listed below, which is looking much

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Actually it happens first that monticello is "nicely" coupled with the changeset system and logs all the source code loaded in change sets :D :/ ¬¬. Also, the first two strings in terms of size are related to unicode tables (we should put them in files instead of in the image and load them on

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

On Tue, Aug 15, 2017 at 11:26 PM, Tim Mackinnon wrote: > Hi Guille/Ben - I got a quick moment to try the SpaceTally (aside: it > seems very convoluted to load a single package into the image, I was trying > to avoid having to create a baselineOf for something so simple - I

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Just a hunch: could you inspect ur MethodChangeRecord instances ? Le mar. 15 août 2017 à 23:55, Tim Mackinnon a écrit : > A weird observation - is it possible that source code is being stored in > the image as strings somehow? When I do > > ./pharo PharoLambda.image eval

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

A weird observation - is it possible that source code is being stored in the image as strings somehow? When I do ./pharo PharoLambda.image eval "ByteString allInstances inject: (OrderedCollection new) into: [:r :i | i size > 500 ifTrue: [r add: i]. r]" I see to see reams of what looks like

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Hi Guille/Ben - I got a quick moment to try the SpaceTally (aside: it seems very convoluted to load a single package into the image, I was trying to avoid having to create a baselineOf for something so simple - I ended up with: repo := MCFileTreeRepository new directory: './bootstrap'

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

On Mon, Aug 14, 2017 at 5:55 PM, Guillermo Polito wrote: > In a full image (just bootstrapped) we have: > > 7.7 MB of arrays (probably in collections, we should check usages) > 6.3 MB of methods > 5.3 MB of ByteArrays > 3.3 MB of ByteStrings > What size do you

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

On Mon, Aug 14, 2017 at 4:42 PM, Tim Mackinnon wrote: > Hi Guille - just running SpaceTally on my dev image to get a feel for it. > It turns out that in the minimal images you’ve been creating, its not > loaded (makes sense). > Yup, it's loaded afterwards. All packages are

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Tim could you send me a "sexy" screen capture for a success story half september? I will take you text as an input and come back to you. Stef On Thu, Aug 10, 2017 at 3:47 PM, Tim Mackinnon wrote: > I just wanted to thank everyone for their help in getting my pet project >

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Hi Guille - just running SpaceTally on my dev image to get a feel for it. It turns out that in the minimal images you’ve been creating, its not loaded (makes sense). I’m wondering if there is an easy way to import it in (I guess that package should be in the Pharo git tree I cloned to get Fuel

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

In a full image (just bootstrapped) we have: 7.7 MB of arrays (probably in collections, we should check usages) 6.3 MB of methods 5.3 MB of ByteArrays 3.3 MB of ByteStrings 2.7 MB of Bitmaps 1.8 MB of ByteSymbols That sumps up aready ~27 MB On Mon, Aug 14, 2017 at 11:49 AM, Guillermo

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Hi Tim, On Mon, Aug 14, 2017 at 11:41 AM, Tim Mackinnon wrote: > Hey guys, thanks for your enthusiasm around this - and I cannot stress > enough how this was only possible because of the work that has gone into > making Pharo (in particular the 64bit image, as well as having a

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Hey guys, thanks for your enthusiasm around this - and I cannot stress enough how this was only possible because of the work that has gone into making Pharo (in particular the 64bit image, as well as having a minimal image, and some great blog posts on serialising contexts) as well as the

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Thanks Esteban. @everyone, please vote & share. cheers -ben On Sat, Aug 12, 2017 at 11:35 PM, Esteban Lorenzano wrote: > done: > > https://www.reddit.com/r/programming/comments/6t9242/debugging_lambdas_by_ > rematerializing_saved/ >

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

done: https://www.reddit.com/r/programming/comments/6t9242/debugging_lambdas_by_rematerializing_saved/ https://news.ycombinator.com/item?id=14998234

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

hi Tim, That is. AWESOME! Very nice delivery - it flowed well with great narration. I loved @2:17 "this is the interesting piece, because PharoLambda has serialized the execution context of its application and saved it into [my S3 bucket] ... [then on the local machine] rematerializes

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

This is cool Tim. So what image size you deployed at the end? 2017-08-10 15:47 GMT+02:00 Tim Mackinnon : > I just wanted to thank everyone for their help in getting my pet project > further along, so that now I can announce that PharoLambda is now working > with the V7 minimal

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

+1 Doru > On Aug 10, 2017, at 11:34 PM, Stephane Ducasse > wrote: > > Tim > > I definitively think that we could turn it into a Pharo success story > or something that we can keep on the web site > because it is really nice. > > Stef > > On Thu, Aug 10, 2017 at

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Very nice work, Tim! It is quite impressive what you could do within a short amount of time (essentially since PharoDays). Please do keep this up. Cheers, Doru > On Aug 10, 2017, at 3:47 PM, Tim Mackinnon wrote: > > I just wanted to thank everyone for their help in getting

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Tim I definitively think that we could turn it into a Pharo success story or something that we can keep on the web site because it is really nice. Stef On Thu, Aug 10, 2017 at 3:47 PM, Tim Mackinnon wrote: > I just wanted to thank everyone for their help in getting my pet

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Yeah, very nice. I just watched it all and looks cool. I am happy that the debugger/stack/context serialization is still breaking other people's mind :) There are a few limitations and problems with the serialization of debugger and materialization in another image. I think I listed those several

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Impressive stuff!! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Aug 10, 2017, at 9:47 AM, Tim Mackinnon wrote: > > I just wanted to thank everyone for their

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

Hi Tim, Impressive pet project you have. And what a way to deliver! Not only with fun features never built before, but also with a documented repo and a detailed screencast. Congratulations. In my self interest, and indirectly for the Pharo community, I look forward to see more contributions

[Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

I just wanted to thank everyone for their help in getting my pet project further along, so that now I can announce that PharoLambda is now working with the V7 minimal image and also supports post mortem debugging by saving a zipped fuel context onto S3. This latter item is particularly