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

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

by Stephane Ducasse

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 <tim(a)testit.works> wrote: > 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 satisfying as at a recent serverless > conference (JeffConf) there was a panel where poor development tools on > serverless platforms was highlighted as a real problem. > > In our community weâve had these kinds of tools at our fingertips for ages - > but I donât think the wider development community has really noticed. > Debugging something short lived like a Lambda execution is quite startling, > as the current answer is âadd more loggingâ, and we all know that sucks. To > this end, Iâve created a little screencast showing this in action - and it > was pretty cool because it was a real example I encountered when I got > everything working and was trying my test application out. > > Iâve also put a bit of work into tuning the excellent GitLab CI tools, so > that I can cache many of the artefacts used between different build runs > (this might also be of interest to others using CI systems). > > The Gitlab project is on: https://gitlab.com/macta/PharoLambda > And the screencast: https://www.youtube.com/watch?v=bNNCT1hLA3E > > 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 > >

Aug. 10, 2017

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

by Mariano Martinez Peck

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 times in the mailing list, but if you want, let me know, and I can remind them again (there we workarounds or help with the limits). Cheers, On Thu, Aug 10, 2017 at 5:57 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Impressive stuff!! > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Aug 10, 2017, at 9:47 AM, Tim Mackinnon <tim(a)testit.works> wrote: > > 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 satisfying as at a recent serverless > conference (JeffConf) there was a panel where poor development tools on > serverless platforms was highlighted as a real problem. > > In our community weâve had these kinds of tools at our fingertips for ages > - but I donât think the wider development community has really noticed. > Debugging something short lived like a Lambda execution is quite startling, > as the current answer is âadd more loggingâ, and we all know that sucks. To > this end, Iâve created a little screencast showing this in action - and it > was pretty cool because it was a real example I encountered when I got > everything working and was trying my test application out. > > Iâve also put a bit of work into tuning the excellent GitLab CI tools, so > that I can cache many of the artefacts used between different build runs > (this might also be of interest to others using CI systems). > > The Gitlab project is on: https://gitlab.com/macta/PharoLambda > And the screencast: https://www.youtube.com/watch?v=bNNCT1hLA3E > > 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 > > > > -- Mariano http://marianopeck.wordpress.com

Aug. 10, 2017

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

by Alexandre Bergel

Impressive stuff!! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Aug 10, 2017, at 9:47 AM, Tim Mackinnon <tim(a)testit.works> wrote: > > 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 satisfying as at a recent serverless conference (JeffConf) there was a panel where poor development tools on serverless platforms was highlighted as a real problem. > > In our community weâve had these kinds of tools at our fingertips for ages - but I donât think the wider development community has really noticed. Debugging something short lived like a Lambda execution is quite startling, as the current answer is âadd more loggingâ, and we all know that sucks. To this end, Iâve created a little screencast showing this in action - and it was pretty cool because it was a real example I encountered when I got everything working and was trying my test application out. > > Iâve also put a bit of work into tuning the excellent GitLab CI tools, so that I can cache many of the artefacts used between different build runs (this might also be of interest to others using CI systems). > > The Gitlab project is on: https://gitlab.com/macta/PharoLambda <https://gitlab.com/macta/PharoLambda> > And the screencast: https://www.youtube.com/watch?v=bNNCT1hLA3E <https://www.youtube.com/watch?v=bNNCT1hLA3E> > > Tim > > >> On 15 Jul 2017, at 00:39, Tim Mackinnon <tim(a)testit.works <mailto:tim@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 <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 >

Aug. 10, 2017

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

by Esteban A. Maringolo

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 like this from you. Regards! Esteban A. Maringolo 2017-08-10 10:47 GMT-03:00 Tim Mackinnon <tim(a)testit.works>: > 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 satisfying as at a recent serverless > conference (JeffConf) there was a panel where poor development tools on > serverless platforms was highlighted as a real problem. > > In our community weâve had these kinds of tools at our fingertips for ages - > but I donât think the wider development community has really noticed. > Debugging something short lived like a Lambda execution is quite startling, > as the current answer is âadd more loggingâ, and we all know that sucks. To > this end, Iâve created a little screencast showing this in action - and it > was pretty cool because it was a real example I encountered when I got > everything working and was trying my test application out. > > Iâve also put a bit of work into tuning the excellent GitLab CI tools, so > that I can cache many of the artefacts used between different build runs > (this might also be of interest to others using CI systems). > > The Gitlab project is on: https://gitlab.com/macta/PharoLambda > And the screencast: https://www.youtube.com/watch?v=bNNCT1hLA3E > > 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 > >

Aug. 10, 2017

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

by 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 image and also supports post mortem debugging by saving a zipped fuel context onto S3. This latter item is particularly satisfying as at a recent serverless conference (JeffConf) there was a panel where poor development tools on serverless platforms was highlighted as a real problem. In our community weâve had these kinds of tools at our fingertips for ages - but I donât think the wider development community has really noticed. Debugging something short lived like a Lambda execution is quite startling, as the current answer is âadd more loggingâ, and we all know that sucks. To this end, Iâve created a little screencast showing this in action - and it was pretty cool because it was a real example I encountered when I got everything working and was trying my test application out. Iâve also put a bit of work into tuning the excellent GitLab CI tools, so that I can cache many of the artefacts used between different build runs (this might also be of interest to others using CI systems). The Gitlab project is on: https://gitlab.com/macta/PharoLambda <https://gitlab.com/macta/PharoLambda> And the screencast: https://www.youtube.com/watch?v=bNNCT1hLA3E <https://www.youtube.com/watch?v=bNNCT1hLA3E> 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 <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

Aug. 10, 2017

Re: [Pharo-users] [ann] moldable brick editor - alpha

by stephan

On 10-08-17 13:09, stephan wrote: > On 05-08-17 00:19, Tudor Girba wrote: > >Iceberg enableMetacelloIntegration: true. > > That doesn't work. It hangs the image, keeping one CPU > busy. With 60510 that is non-interruptable, b.t.w. Stephan

Aug. 10, 2017

Re: [Pharo-users] [ann] moldable brick editor - alpha

by stephan

On 05-08-17 00:19, Tudor Girba wrote: >Iceberg enableMetacelloIntegration: true. That doesn't work. It hangs the image, keeping one CPU busy. (latest 32 bit vm, ubuntu 16.04LTS) Also the Moz2D is not correctly installed/deinstalled. After warning that the library is not correctly installed, the start/stop script needs to be cleanly removed. Stephan

Aug. 10, 2017

UK Smalltalk User Group Meeting - Monday 21st August

by Giovanni Corriga

The next meeting of the UK Smalltalk User Group Meeting will be on Monday, 21st August. We'll meet at a new venue The City Pride ( http://www. cityprideclerkenwell.co.uk/ ) at 7pm. If you'd like to join us, you can just show up at the pub. You can also sign up in advance at the meeting's Meetup page: *https://www.meetup.com/UKSTUG/events/242432390/ <https://www.meetup.com/UKSTUG/events/242432390/> *. See you there!

Aug. 10, 2017

Re: [Pharo-users] PetitParser: Parse X as long as it's not Y

by Sean P. DeNigris

Peter Kenny wrote > You may need to post-process the parse to get what you > want. Good point. I omitted several ` ==> #second` in several places for readability on the list, but we should mention that for posterity. Also, duh `gen negate and` should be `gen not`! ----- Cheers, Sean -- View this message in context: http://forum.world.st/PetitParser-Parse-X-as-long-as-it-s-not-Y-tp4958895p4… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 10, 2017

Re: [Pharo-users] about a pillar based output format for Epicea

by Stephane Ducasse

Hi for the menu I did a really ugly copy and paste and hack inside and versioned in my package. I did not find the time to think about menu building for Spec. Stef On Wed, Aug 9, 2017 at 6:09 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > > > On Wed, Aug 2, 2017 at 12:55 PM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: >> >> Hi martin >> >> I would like to wlak over epicea objects and save the changed methods >> to be able to write booklets faster. >> What advices can you give me? >> Create a special visitor? > > > For the record, I copy this small explanation from a private email: > > --------- > Epicea models: > - IDE events (refactorings, monticello) -> EpEvent > - code changes (class addition, method modification) -> EpCodeChange > > where EpCodeChange is subclass of EpEvent. > > To create visitors you have EpTEventVisitor and EpTCodeChangeVisitor, that > provide default visitXX: implementations. > ---------- > > Stef, any update on the menu extension? > > indeed I'm not proud of that method you included in another email. I didn't > consider the need to extend such menu (besides it's ugly code, anyway). > > MartÃn > >> >> Stef >> >

Aug. 9, 2017