December 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Pharo Lambda Runtime

by Tim Mackinnon

Cool - I was using a JS shim and had asked AWS many times why they couldnât open it up wider... Now Iâm back from my travels Iâll reincarnate my previous work and see how it works with this. I was looking forward to doing more with Lambda, so this is great timing. Tim Sent from my iPhone > On 27 Dec 2018, at 10:32, Jan van de Sandt <jvdsandt(a)gmail.com> wrote: > > Hi, > > Last month Amazon extended their serverless runtime platform AWS Lambda with support for custom runtimes. I created a Pharo Lambda Runtime so now we can implement Lambda functions in Smalltalk and easily deploy them on the Lambda platform. Lamba has quite a large "free-tier", more than enough to do some experiments and to host small applications for free. > > See the GitHub project for more details https://github.com/jvdsandt/pharo-aws-toolbox > > Cheers, > Jan.

Dec. 27, 2018

Re: [Pharo-dev] [ANN] Pharo Lambda Runtime

by Sven Van Caekenberghe

Nice job. Well documented. Thank you. > On 27 Dec 2018, at 10:32, Jan van de Sandt <jvdsandt(a)gmail.com> wrote: > > Hi, > > Last month Amazon extended their serverless runtime platform AWS Lambda with support for custom runtimes. I created a Pharo Lambda Runtime so now we can implement Lambda functions in Smalltalk and easily deploy them on the Lambda platform. Lamba has quite a large "free-tier", more than enough to do some experiments and to host small applications for free. > > See the GitHub project for more details https://github.com/jvdsandt/pharo-aws-toolbox > > Cheers, > Jan.

Dec. 27, 2018

Re: [Pharo-dev] [ANN] Pharo Lambda Runtime

by Ben Coman

This sounds really great. Something I'd like to experiment with. Thanks. cheers -ben On Thu, 27 Dec 2018 at 17:32, Jan van de Sandt <jvdsandt(a)gmail.com> wrote: > Hi, > > Last month Amazon extended their serverless runtime platform AWS Lambda > with support for custom runtimes. I created a Pharo Lambda Runtime so now > we can implement Lambda functions in Smalltalk and easily deploy them on > the Lambda platform. Lamba has quite a large "free-tier", more than enough > to do some experiments and to host small applications for free. > > See the GitHub project for more details > https://github.com/jvdsandt/pharo-aws-toolbox > > Cheers, > Jan. >

Dec. 27, 2018

Re: [Pharo-dev] [ANN][IMPORTANT] Pharo 8.0 issue tracker is MOVED to GitHub

by Ben Coman

On Thu, 27 Dec 2018 at 17:04, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > As part of our constant try to enhance process, we are moving the issue > tracker to GitHub. > You can now declare issues here: > > https://github.com/pharo-project/pharo/issues > > FAQ: > > Q: Why we do this? > A: > - Because reuniting all development process in just one point will enhance > traceability > - â¦ and communication (there are a lot of conversations that now happens > in different places (list, issue, PR). With this move we put issue and PR > discussion in same place. > - â¦ and people historically has complained that âthey need to log to > fogbugz to just see the issuesâ > - â¦ and this allows us to decommission one server we have now just to get > the issues names when creating branches (and before slides). > > Q: Does that means fogbugz is bad? > A: Not at all! It is a great tool and we are very grateful of it. Is just > that we want to reunite our communication into a single point. > > Q: What will happen with issues reported in FogBugz? > A: Pharo 7.0 issues will be taken as before. Pharo 8.0 issues need to be > re-opened in GitHub. There are less than 25 right now and we ask people > reporting it to move them again (maybe we would do it, but better is owners > do). > That all sounds fair and reasonable. I just want to clarify if there was going to be any issue migration of old/closed issues (after Pharo 7 release). I understand its a big effort and the value might not be worth it - but just curious what are the constraints and plans. cheers -ben

Dec. 27, 2018

[Pharo 7.0] Build #81: 22802-ZipArchive-should-throw-specific-Error

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #81 was: FAILURE. The Pull Request #2119 was integrated: "22802-ZipArchive-should-throw-specific-Error" Pull request url: https://github.com/pharo-project/pharo/pull/2119 Issue Url: https://pharo.fogbugz.com/f/cases/22802 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 27, 2018

[Pharo 8.0] Build #2: Removed obsolete Fuel package

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #2 was: FAILURE. The Pull Request #2122 was integrated: "Removed obsolete Fuel package" Pull request url: https://github.com/pharo-project/pharo/pull/2122 Issue Url: https://pharo.fogbugz.com/f/cases/22834 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 27, 2018

[Pharo 7.0] Build #80: SUCCESS

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #80 was: SUCCESS. Could not extract further issue information from commit message: references to fogbugz moved to GitHub tracker Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 27, 2018

Re: [Pharo-dev] [ANN] Pharo Lambda Runtime

by Guillermo Polito

Cool! thanks! On Thu, Dec 27, 2018 at 10:32 AM Jan van de Sandt <jvdsandt(a)gmail.com> wrote: > Hi, > > Last month Amazon extended their serverless runtime platform AWS Lambda > with support for custom runtimes. I created a Pharo Lambda Runtime so now > we can implement Lambda functions in Smalltalk and easily deploy them on > the Lambda platform. Lamba has quite a large "free-tier", more than enough > to do some experiments and to host small applications for free. > > See the GitHub project for more details > https://github.com/jvdsandt/pharo-aws-toolbox > > Cheers, > Jan. > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 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

Dec. 27, 2018

[ANN] Pharo Lambda Runtime

by Jan van de Sandt

Hi, Last month Amazon extended their serverless runtime platform AWS Lambda with support for custom runtimes. I created a Pharo Lambda Runtime so now we can implement Lambda functions in Smalltalk and easily deploy them on the Lambda platform. Lamba has quite a large "free-tier", more than enough to do some experiments and to host small applications for free. See the GitHub project for more details https://github.com/jvdsandt/pharo-aws-toolbox Cheers, Jan.

Dec. 27, 2018

[ANN][IMPORTANT] Pharo 8.0 issue tracker is MOVED to GitHub

by Esteban Lorenzano

Hi, As part of our constant try to enhance process, we are moving the issue tracker to GitHub. You can now declare issues here: https://github.com/pharo-project/pharo/issues <https://github.com/pharo-project/pharo/issues> FAQ: Q: Why we do this? A: - Because reuniting all development process in just one point will enhance traceability - â¦ and communication (there are a lot of conversations that now happens in different places (list, issue, PR). With this move we put issue and PR discussion in same place. - â¦ and people historically has complained that âthey need to log to fogbugz to just see the issuesâ - â¦ and this allows us to decommission one server we have now just to get the issues names when creating branches (and before slides). Q: Does that means fogbugz is bad? A: Not at all! It is a great tool and we are very grateful of it. Is just that we want to reunite our communication into a single point. Q: What will happen with issues reported in FogBugz? A: Pharo 7.0 issues will be taken as before. Pharo 8.0 issues need to be re-opened in GitHub. There are less than 25 right now and we ask people reporting it to move them again (maybe we would do it, but better is owners do). Q: How can we âbranch from issueâ now if we do not have FogBugz? A: We already added a tool âbranch from issueâ that uses GitHub issue tracker. This will be the same as before. And for the same price, we add that option to other projects: All GitHub projects now can benefit from âbranch from issueâ functionality. Cheers! Esteban

Dec. 27, 2018