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

Re: [Pharo-users] Are we able to run pharo images in a read only environment?

by Tim Mackinnon

I went to try this to see how it might perform on AWS Lambda but Iâm guessing there isnât a minimal 64 bit image right? Sven - was this a 32bit image from get.pharo.org/70-minimal? <http://get.pharo.org/70-minimal?> Tim > On 30 Jun 2017, at 14:43, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> On 27 Jun 2017, at 21:15, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >>> On 27 Jun 2017, at 21:00, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>> >>> Interesting experiment. >>> >>> It would be good to know how fast does the image boot and start >>> execution in the context of a service billed at the sub second scale. >> >> Sadly I have the impression we lost some speed: >> >> ~/pharo64$ ./pharo Pharo.image printVersion >> [version] 6.0 #60499 >> >> ~/pharo64$ time ./pharo Pharo.image eval '42 factorial' >> 1405006117752879898543142606244511569936384000000000 >> >> real 0m1.276s >> user 0m0.985s >> sys 0m0.171s >> >> while before >> >> ~/pharo/build$ ../bin/pharo Pharo.image printVersion >> [version] 4.0 #40620 >> >> $ time ../bin/pharo Pharo.image eval '42 factorial' >> 1405006117752879898543142606244511569936384000000000 >> >> real 0m0.526s >> user 0m0.434s >> sys 0m0.045s >> >> But it is really hard to find the cause. > > The good news is that the Pharo 7 minimal core is way faster > > $ time ./pharo ~/Downloads/Pharo7.0-core-32bit-b649ac6.image eval "42 factorial" > 1405006117752879898543142606244511569936384000000000 > > real 0m0.262s > user 0m0.132s > sys 0m0.062s > > Which is good of course ! > >> That being said, these lambda servers can only work well if they keep instances alive for longer when there is enough traffic. >> >>> Esteban A. Maringolo >>> >>> >>> 2017-06-27 13:05 GMT-03:00 Tim Mackinnon <tim(a)testit.works>: >>>> Hi - I am trying to run a pharo image in lambda (as an experiment) - however >>>> I get an error from Pharo about not being able to write to the changes file? >>>> >>>> As I am just evaluating some code - Iâm not really coding, so donât need a >>>> changes file - is there a command line option to not require it? >>>> >>>> Also, am I running pharo the most efficient way - Iâm using eval on the >>>> command line and referencing a class with a class method - but is this the >>>> best way? >>>> >>>> Thanks, >>>> >>>> Tim >>>> >>>> "errorMessage": "Command failed: ./pharo Pharo.image eval \"Lambda >>>> processJSON: >>>> '{\"key3\":\"value3\",\"key2\":\"value2\",\"key1\":\"value1\"}'\"\n'Pharo >>>> cannot write to the changes file named /var/task/Pharo.changes.\n\nPlease >>>> check that you have write permission for this file.\n\nYou won''t be able to >>>> save this image correctly until you fix this.'\n\u001b[31mError: Can't find >>>> the requested >>>> origin\n\u001b[0mUnixResolver(PlatformResolver)>>cantFindOriginError\n[ self >>>> cantFindOriginError ] in >>>> UnixResolver(PlatformResolver)>>directoryFromEnvVariableNamed: in Block: [ >>>> self cantFindOriginError >>>> ]\nUnixResolver(PlatformResolver)>>directoryFromEnvVariableNamed:or:\nUnixResolver(PlatformResolver)>>directoryFromEnvVariableNamed:\nUnixResolver>>home\n[ >>>> self home / '.config' ] in UnixResolver>>preferences in Block: [ self home / >>>> '.config' >>>> ]\nUnixResolver(PlatformResolver)>>directoryFromEnvVariableNamed:or:\nUnixResolver>>preferences\nUnixResolver(FileSystemResolver)>>resolve:\nSystemResolver(FileSystemResolver)>>unknownOrigin:\nSystemResolver(FileSystemResolver)>>resolve:\nInteractiveResolver>>unknownOrigin:\n[ >>>> self unknownOrigin: origin ] in InteractiveResolver>>resolve: in Block: [ >>>> self unknownOrigin: origin >>>> ]\nIdentityDictionary(Dictionary)>>at:ifAbsent:\nInteractiveResolver>>resolve:\nFileLocator>>resolve\nFileLocator(AbstractFileReference)>>exists\nGlobalIdentifierStonPersistence(GlobalIdentifierPersistence)>>shouldCallPreviousPersistence\nGlobalIdentifierStonPersistence(GlobalIdentifierPersistence)>>ensure:\nGlobalIdentifier>>ensure\nGlobalIdentifier >>>> class>>initializeUniqueInstance\nGlobalIdentifier >>>> class>>uniqueInstance\nSystemSettingsPersistence >>>> class>>resumeSystemSettings\n[ :persistence | persistence >>>> resumeSystemSettings ] in PharoCommandLineHandler>>runPreferences in Block: >>>> [ :persistence | persistence resumeSystemSettings >>>> ...etc...\nBlockClosure>>cull:\nSystemDictionary(Dictionary)>>at:ifPresent:\nSmalltalkImage>>at:ifPresent:\nPharoCommandLineHandler>>runPreferences\nPharoCommandLineHandler>>activate\nPharoCommandLineHandler >>>> class(CommandLineHandler class)>>activateWith:\n\u001b[0m", >>>> "errorType": "Error", >>>> "stackTrace": [ >>>> "'Pharo cannot write to the changes file named >>>> /var/task/Pharo.changes.", >>>> "", >>>> "Please check that you have write permission for this file.", >>>> "", >>>> "You won''t be able to save this image correctly until you fix this.'", >>>> "\u001b[31mError: Can't find the requested origin", >>>> "\u001b[0mUnixResolver(PlatformResolver)>>cantFindOriginError", >>>> "[ self cantFindOriginError ] in >>>> UnixResolver(PlatformResolver)>>directoryFromEnvVariableNamed: in Block: [ >>>> self cantFindOriginError ]", >>>> "UnixResolver(PlatformResolver)>>directoryFromEnvVariableNamed:or:", >>>> "UnixResolver(PlatformResolver)>>directoryFromEnvVariableNamed:", >>>> "UnixResolver>>home", >>>> "[ self home / '.config' ] in UnixResolver>>preferences in Block: [ self >>>> home / '.config' ]", >>>> "UnixResolver(PlatformResolver)>>directoryFromEnvVariableNamed:or:", >>>> "UnixResolver>>preferences", >>>> "UnixResolver(FileSystemResolver)>>resolve:", >>>> "SystemResolver(FileSystemResolver)>>unknownOrigin:", >>>> "SystemResolver(FileSystemResolver)>>resolve:", >>>> "InteractiveResolver>>unknownOrigin:", >>>> "[ self unknownOrigin: origin ] in InteractiveResolver>>resolve: in >>>> Block: [ self unknownOrigin: origin ]", >>>> "IdentityDictionary(Dictionary)>>at:ifAbsent:", >>>> "InteractiveResolver>>resolve:", >>>> "FileLocator>>resolve", >>>> "FileLocator(AbstractFileReference)>>exists", >>>> >>>> "GlobalIdentifierStonPersistence(GlobalIdentifierPersistence)>>shouldCallPreviousPersistence", >>>> "GlobalIdentifierStonPersistence(GlobalIdentifierPersistence)>>ensure:", >>>> "GlobalIdentifier>>ensure", >>>> "GlobalIdentifier class>>initializeUniqueInstance", >>>> "GlobalIdentifier class>>uniqueInstance", >>>> "SystemSettingsPersistence class>>resumeSystemSettings", >>>> "[ :persistence | persistence resumeSystemSettings ] in >>>> PharoCommandLineHandler>>runPreferences in Block: [ :persistence | >>>> persistence resumeSystemSettings ...etc...", >>>> "BlockClosure>>cull:", >>>> "SystemDictionary(Dictionary)>>at:ifPresent:", >>>> "SmalltalkImage>>at:ifPresent:", >>>> "PharoCommandLineHandler>>runPreferences", >>>> "PharoCommandLineHandler>>activate", >>>> "PharoCommandLineHandler class(CommandLineHandler >>>> class)>>activateWith:", >>>> "\u001b[0m", >>>> "ChildProcess.exithandler (child_process.js:204:12)", >>>> "emitTwo (events.js:106:13)", >>>> "ChildProcess.emit (events.js:191:7)", >>>> "maybeClose (internal/child_process.js:886:16)", >>>> "Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)" >>>> ] >>>> }

July 5, 2017

Re: [Pharo-users] super simple programming intro with Pharo 6?

by Offray Vladimir Luna CÃ¡rdenas

Hi, I would try Squeak, Learning Programming with Robots [1]. It's what I used with my freshmen students at the University. Most of them have no previous experience with programming. That, combined with Etoys and Scratch worked pretty well. I don't know if there is some image that can be run these days thought. [1] https://duckduckgo.com/?q=Squeak%2C+Learning+Programming+with+Robots&t=ffsb… Cheers, Offray On 05/07/17 08:19, Christian Haider wrote: > > Hi, > > > > is there some basic intro to programming (for a 10 year old without > prior experience) ideally with Pharo 6? > > Is Prof Stef suitable? > > > > Thanks, > > Christian >

July 5, 2017

Re: [Pharo-users] PharoCloud Ephemeric Cloud updates

by Marcus Denker

> > 2) Added support for Pharo 6 (32 bits only for now). Pharo 6 is particularly > slow in read-only environments, so... now environment is writable. All > changes are written to memory and reset on restart. Kind of works, Pharo 6 > images are starting in 1-2 seconds (after initial load which may take for > like 10 seconds). I migrated all my apps to the Pharo 6 and seems to work > fine now. > We should really fix thatâ¦ do you know if there is already an issue tracker entry? > > 4) As result now you can remotely connect, debug and control Images running > at PharoCloud using PharmIDE: > http://docs.swarm.pharocloud.com/article/remote_debug > This is so awesome! Thank you to Denis for his great work on PharmIDE: > http://dionisiydk.blogspot.com/2017/01/pharmide-pharo-remote-ide-to-develop… > Please try it and tell me if it works for you. Nice! Marcus

July 5, 2017

Re: [Pharo-users] RFBSever not surviving disconnection

by sergio ruiz

Oooh! this looks interesting! On July 4, 2017 at 11:40:24 AM, Denis Kudriashov (dionisiydk(a)gmail.com) wrote: As alternative to RFB try remote dev toolsÂ http://dionisiydk.blogspot.fr/2017/01/pharmide-pharo-remote-ide-to-develop.…. You can play with it in PharoCloudÂ http://docs.swarm.pharocloud.com/article/remote_debugÂ . (you need Pharo 6 for this) ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com http://www.ThoseOptimizeGuys.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

July 5, 2017

super simple programming intro with Pharo 6?

by Christian Haider

Hi, is there some basic intro to programming (for a 10 year old without prior experience) ideally with Pharo 6? Is Prof Stef suitable? Thanks, Christian

July 5, 2017

Ideas wanted: "Patterns to sustain feedback loops"

by Marcus Denker

Hi, I want to do a third talk at ESUG as the âpart 3â of the feedback loop series.. The first parts where: 1. Nomads do not build Cathedrals: https://www.slideshare.net/MarcusDenker/2014-esugcathedral 2. Perfection and Feedback Loops: Why worse is better. https://www.slideshare.net/MarcusDenker/perfection-feedback-loops-or-why-wo… The idea for part 3 is to do something along the lines of âpatterns to enable feedback loopsâ, a more practical view on what one should be doing (or not be doing) to enable and sustain a project as a feedback loop. - both things we do and those we should - things that we do wrong / anti patterns - technical as well as social (communityâ¦) - examples you have seen in the real world The idea is not to follow a formal patterns language, it will be informalâ¦ so if you have any ideas, please send a private mail to me. Marcus

July 5, 2017

Re: [Pharo-users] [ANN] association.pharo.org now on AWS

by john pfersich

Wow, it's a lot quicker from the western US than the old site! Thanks. Sent from my iPhone > On Jul 5, 2017, at 00:10, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > I just changed the DNS entry for > > https://association.pharo.org > > It now runs on Amazon AWS, this should make it faster and more reliable than > in the past. > > Marcus >

July 5, 2017

[ANN] association.pharo.org now on AWS

by Marcus Denker

Hi, I just changed the DNS entry for https://association.pharo.org It now runs on Amazon AWS, this should make it faster and more reliable than in the past. Marcus

July 5, 2017

Re: [Pharo-users] Pharo6.0 for linux and PharoV60.sources location

by Marc Hanisch

Hi Stephane, thanks for that kind reply! No problem! I'm unfortunately not too deep into Pharo, but maybe I can help with the packaging / build process for the Linux downloads (at least my Linux knowledge is far better than my Pharo knowledge ;-))? Best regards, Marc 2017-07-05 8:00 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Hi marc > > We are a bit under water in this moment making sure that we can handle > pull requests for Pharo 70. > I'm sure that it will get better in the future. > Esteban is moving, we got many articles to send, clement hand it in its phd :). > And many more. > > So we are sorry about the support. > > Stef > > On Mon, Jul 3, 2017 at 1:14 PM, Marc Hanisch via Pharo-users > <pharo-users(a)lists.pharo.org> wrote: >> >> >> ---------- Forwarded message ---------- >> From: Marc Hanisch <marc.hanisch(a)googlemail.com> >> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >> Cc: >> Bcc: >> Date: Mon, 3 Jul 2017 13:14:52 +0200 >> Subject: Re: [Pharo-users] Pharo6.0 for linux and PharoV60.sources location >> Hi Andreas, >> >> Yes, that was me. Unfortunately I did not get an answer. I solved this by copying the sources file into the location where Pharo is looking for it. >> >> Due to the missing sources file, variables and arguments got renamed automatically... >> >> I still don't understand why the sources file is spread 3 or 4 times across the directory structure... >> >> Best regards, >> Marc >> >> Am 03.07.2017 12:16 schrieb "Andreas Sunardi" <a.sunardi(a)gmail.com>: >>> >>> Pardon me if this has been discussed before. I seem to recall somebody ran into this issue or related to this, but I don't remember what the solution was, if there was any. >>> >>> The linux Pharo 6 download package from Pharo web site has different VM directory structure than Pharo 5. The PharoV60.sources file is not located in the same directory as the VM binary. As a result, if user has image + changes files in another directory, Pharo always gives notification that the sources file is not found. This is not so with the Pharo 5. >>> >>> In most cases, it's just a notification, but in the past I've run into an error in debugging session when I tried to look into a method because of missing sources file. >>> >>> Can this be corrected or is it expected for the user to manage sources file where about? I'm hoping a correction or clarification would at least benefit new comers. >>> >>> -- >>> Andreas >>> >>> >> >

July 5, 2017

Re: [Pharo-users] Pharo6.0 for linux and PharoV60.sources location

by Stephane Ducasse

Hi marc We are a bit under water in this moment making sure that we can handle pull requests for Pharo 70. I'm sure that it will get better in the future. Esteban is moving, we got many articles to send, clement hand it in its phd :). And many more. So we are sorry about the support. Stef On Mon, Jul 3, 2017 at 1:14 PM, Marc Hanisch via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: Marc Hanisch <marc.hanisch(a)googlemail.com> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Cc: > Bcc: > Date: Mon, 3 Jul 2017 13:14:52 +0200 > Subject: Re: [Pharo-users] Pharo6.0 for linux and PharoV60.sources location > Hi Andreas, > > Yes, that was me. Unfortunately I did not get an answer. I solved this by copying the sources file into the location where Pharo is looking for it. > > Due to the missing sources file, variables and arguments got renamed automatically... > > I still don't understand why the sources file is spread 3 or 4 times across the directory structure... > > Best regards, > Marc > > Am 03.07.2017 12:16 schrieb "Andreas Sunardi" <a.sunardi(a)gmail.com>: >> >> Pardon me if this has been discussed before. I seem to recall somebody ran into this issue or related to this, but I don't remember what the solution was, if there was any. >> >> The linux Pharo 6 download package from Pharo web site has different VM directory structure than Pharo 5. The PharoV60.sources file is not located in the same directory as the VM binary. As a result, if user has image + changes files in another directory, Pharo always gives notification that the sources file is not found. This is not so with the Pharo 5. >> >> In most cases, it's just a notification, but in the past I've run into an error in debugging session when I tried to look into a method because of missing sources file. >> >> Can this be corrected or is it expected for the user to manage sources file where about? I'm hoping a correction or clarification would at least benefit new comers. >> >> -- >> Andreas >> >> >

July 5, 2017