- Pharo-users - lists.pharo.org

Re: [Pharo-users] including Pillar in Pharo image by default

by Guillermo Polito

Esteban, I think that when Stef says "a mini version of pillar" he does not mean a mini version of the parser or the AST, but a version that does not have the exporting to html/latex/... On Sat, Aug 12, 2017 at 4:37 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > and btw, this kind of threads belongs to pharo-dev, not to pharo-users :) > > Esteban > > > On 12 Aug 2017, at 16:35, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > > >> On 12 Aug 2017, at 12:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> > >> Hi, > >> > >> I would very much like this path. What would constitute tiny? > > > > no idea, we need to think on it :) > > but I see no point in create a new (even small) parser/scanner each time > we need one. At the end you have several small parsers that repeat always > same process when PetitParser is good for most of our problems (and if you > need to improve it. you can always load PP compiler, etc.). > > > > Esteban > > > >> > >> Cheers, > >> Doru > >> > >> > >>> On Aug 11, 2017, at 9:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >>> > >>> hi, > >>> > >>>> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> > wrote: > >>>> > >>>> Another step would be to get a minimal parser not relying on > >>>> PetitParser. > >>> > >>> Letâs think differently: why not to include a tiny PetitParser? > >>> Then we can think on: > >>> > >>> - pillar sintax (better than just a restricted version) > >>> - simplify other âsmall parsersâ that are already on the image. > >>> - we provide a tool to o cool stuff (instead relying as always in > regexp, etc.) > >>> > >>> cheers, > >>> Esteban > >> > >> -- > >> www.tudorgirba.com > >> www.feenk.com > >> > >> "Beauty is where we see it." > >> > >> > >> > >> > >> > > > > > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 12, 2017

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

by Ben Coman

Thanks Esteban. @everyone, please vote & share. cheers -ben On Sat, Aug 12, 2017 at 11:35 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > done: > > https://www.reddit.com/r/programming/comments/6t9242/debugging_lambdas_by_ > rematerializing_saved/ > https://news.ycombinator.com/item?id=14998234 > > Esteban > > On 12 Aug 2017, at 17:26, Ben Coman <btc(a)openinworld.com> wrote: > > 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 a debugger [on > that context]." > > There is a clarity in your video presentation that really may intrigue > outsiders. As a community we should push this on the usual hacker forums - > ycombinator could be a good starting point (but I'm locked out of my > account there). > An enticing title could be... > "Debugging Lambdas by re-materializing saved execution contexts on your > local machine." > > cheers -ben > > On Fri, Aug 11, 2017 at 3:37 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> This is cool Tim. >> >> So what image size you deployed at the end? >> >> 2017-08-10 15:47 GMT+02: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. 12, 2017

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

by Esteban Lorenzano

done: https://www.reddit.com/r/programming/comments/6t9242/debugging_lambdas_by_r… <https://www.reddit.com/r/programming/comments/6t9242/debugging_lambdas_by_r…> https://news.ycombinator.com/item?id=14998234 <https://news.ycombinator.com/item?id=14998234> Esteban > On 12 Aug 2017, at 17:26, Ben Coman <btc(a)openinworld.com> wrote: > > 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 a debugger [on that context]." > > There is a clarity in your video presentation that really may intrigue outsiders. As a community we should push this on the usual hacker forums - ycombinator could be a good starting point (but I'm locked out of my account there). > An enticing title could be... > "Debugging Lambdas by re-materializing saved execution contexts on your local machine." > > cheers -ben > > On Fri, Aug 11, 2017 at 3:37 PM, Denis Kudriashov <dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>> wrote: > This is cool Tim. > > So what image size you deployed at the end? > > 2017-08-10 15:47 GMT+02:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@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 <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. 12, 2017

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

by Ben Coman

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 a debugger [on that context]." There is a clarity in your video presentation that really may intrigue outsiders. As a community we should push this on the usual hacker forums - ycombinator could be a good starting point (but I'm locked out of my account there). An enticing title could be... "Debugging Lambdas by re-materializing saved execution contexts on your local machine." cheers -ben On Fri, Aug 11, 2017 at 3:37 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > This is cool Tim. > > So what image size you deployed at the end? > > 2017-08-10 15:47 GMT+02: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. 12, 2017

Re: [Pharo-users] including Pillar in Pharo image by default

by Esteban Lorenzano

and btw, this kind of threads belongs to pharo-dev, not to pharo-users :) Esteban > On 12 Aug 2017, at 16:35, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 12 Aug 2017, at 12:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> I would very much like this path. What would constitute tiny? > > no idea, we need to think on it :) > but I see no point in create a new (even small) parser/scanner each time we need one. At the end you have several small parsers that repeat always same process when PetitParser is good for most of our problems (and if you need to improve it. you can always load PP compiler, etc.). > > Esteban > >> >> Cheers, >> Doru >> >> >>> On Aug 11, 2017, at 9:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> hi, >>> >>>> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: >>>> >>>> Another step would be to get a minimal parser not relying on >>>> PetitParser. >>> >>> Letâs think differently: why not to include a tiny PetitParser? >>> Then we can think on: >>> >>> - pillar sintax (better than just a restricted version) >>> - simplify other âsmall parsersâ that are already on the image. >>> - we provide a tool to o cool stuff (instead relying as always in regexp, etc.) >>> >>> cheers, >>> Esteban >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Beauty is where we see it." >> >> >> >> >> >

Aug. 12, 2017

Re: [Pharo-users] including Pillar in Pharo image by default

by Esteban Lorenzano

> On 12 Aug 2017, at 12:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > I would very much like this path. What would constitute tiny? no idea, we need to think on it :) but I see no point in create a new (even small) parser/scanner each time we need one. At the end you have several small parsers that repeat always same process when PetitParser is good for most of our problems (and if you need to improve it. you can always load PP compiler, etc.). Esteban > > Cheers, > Doru > > >> On Aug 11, 2017, at 9:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> hi, >> >>> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: >>> >>> Another step would be to get a minimal parser not relying on >>> PetitParser. >> >> Letâs think differently: why not to include a tiny PetitParser? >> Then we can think on: >> >> - pillar sintax (better than just a restricted version) >> - simplify other âsmall parsersâ that are already on the image. >> - we provide a tool to o cool stuff (instead relying as always in regexp, etc.) >> >> cheers, >> Esteban > > -- > www.tudorgirba.com > www.feenk.com > > "Beauty is where we see it." > > > > >

Aug. 12, 2017

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

by Tudor Girba

Hi, As Jan pointed out, you should use ânotâ instead of ânegate andâ. Cheers, Doru > On Aug 10, 2017, at 5:22 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > 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. > -- www.tudorgirba.com www.feenk.com "Speaking louder won't make the point worthier."

Aug. 12, 2017

Re: [Pharo-users] Checking in on source/dependency management

by Ben Coman

On Thu, Aug 10, 2017 at 2:30 AM, sergio ruiz <sergio.rrd(a)gmail.com> wrote: > Hi, all.. > > I am just checking in on source and dependency management. > > I have been using Pharo 6 for a bit now, and i know that there has been a > lot of talk about going to bit for source code management. > > I am wondering how far along that is, and if there is a package we can > start using to work through that. > > I am also wondering if metacello is still the dependency management system > of choice. I > I believe it is. The GUI tool (btw, can you clarify which one) was just a layer over Metacello. Metacello has two sub-parts: Configurations for traditional HTTP repositories like Smalltalkhub; and Baselines for use with git. Baselines are a subset of Configurations because git picks up some of that functionality. cheers -ben

Aug. 12, 2017

Re: [Pharo-users] including Pillar in Pharo image by default

by Tudor Girba

Hi, I would very much like this path. What would constitute tiny? Cheers, Doru > On Aug 11, 2017, at 9:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > hi, > >> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: >> >> Another step would be to get a minimal parser not relying on >> PetitParser. > > Letâs think differently: why not to include a tiny PetitParser? > Then we can think on: > > - pillar sintax (better than just a restricted version) > - simplify other âsmall parsersâ that are already on the image. > - we provide a tool to o cool stuff (instead relying as always in regexp, etc.) > > cheers, > Esteban -- www.tudorgirba.com www.feenk.com "Beauty is where we see it."

Aug. 12, 2017

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

by Tudor Girba

Is this still an issue? Could you also try on another OS (just to make sure)? Cheers, Doru > On Aug 10, 2017, at 2:12 PM, stephan <stephan(a)stack.nl> wrote: > > 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 > > > > -- www.tudorgirba.com www.feenk.com "Problem solving efficiency grows with the abstractness level of problem understanding."

Aug. 12, 2017