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

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

by Esteban A. Maringolo

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. 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)" > ] > } > >

June 27, 2017

Re: [Pharo-users] Pharo6 bootstrap how to

by Hilaire

It will be helpfull, because from here I don't understand not much how I should get started. But I guess it is too early in the process as things may still be moving. Le 27/06/2017 Ã 13:02, Pavel Krivanek a Ã©crit : > Right now we do not have such source. > > -- Pavel -- Dr. Geo http://drgeo.eu

June 27, 2017

Re: [Pharo-users] ZnConstants missing 511 in default Pharo 6.0 32 image?

by Sven Van Caekenberghe

> On 27 Jun 2017, at 18:30, Tim Mackinnon <tim(a)testit.works> wrote: > > Yes ZnConstants initialize > Works, > > When I inspected the constants before this, it seemed to have everything except 511 (the last one). > > Is there a load error in Pharo - as if the initialise code is correct, and the images are built with a CI process - Iâm wondering how it gets into that state? When a class is loaded, class side #initialize methods are run (so classes are re-initialized) if their source code changed (compared to what is already in the image). When 511 was added, the #initialize did not change, hence it was not run. That is why I currently add a comment like "Forced source code change for automatic initialization: 20170510" where I change the date when needed. > Tim > >> On 27 Jun 2017, at 15:02, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi Tim, >> >>> On 27 Jun 2017, at 15:50, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>> Hi - I have been slowly working my way through some of the pharo components and tutorials and when trying out ZnEasy with a password protected api, I got a talkback when I mistyped a password. >>> It looks like ZnConstants in a fresh Pharo 6.0 32 image excludes 511 from its constants. The code looks correct (and its defined in the initialize method - ) but when I tried a ZnEasy call which returned 511 I got a walkback showing it as an unrecognized code? (The walkback is looking for 511 in ZnConstants httpStatusCodes). >>> >>> Is there some problem in the build process, or is this some type of user error? >>> >>> Tim >> >> You should get >> >> ZnStatusLine code: 511. "a ZnStatusLine(511 Network Authentication Required)" >> >> If that is not the case, do >> >> ZnConstants initialize. >> >> What does ZnConstants class>>#initialize look like for you ? >> >> The latest version should read like >> >> initialize >> "Forced source code change for automatic initialization: 20170510" >> >> self initializeHTTPStatusCodes >> >> Sven > >

June 27, 2017

Re: [Pharo-users] ZnConstants missing 511 in default Pharo 6.0 32 image?

by Tim Mackinnon

Yes ZnConstants initialize Works, When I inspected the constants before this, it seemed to have everything except 511 (the last one). Is there a load error in Pharo - as if the initialise code is correct, and the images are built with a CI process - Iâm wondering how it gets into that state? Tim > On 27 Jun 2017, at 15:02, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Tim, > >> On 27 Jun 2017, at 15:50, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi - I have been slowly working my way through some of the pharo components and tutorials and when trying out ZnEasy with a password protected api, I got a talkback when I mistyped a password. >> It looks like ZnConstants in a fresh Pharo 6.0 32 image excludes 511 from its constants. The code looks correct (and its defined in the initialize method - ) but when I tried a ZnEasy call which returned 511 I got a walkback showing it as an unrecognized code? (The walkback is looking for 511 in ZnConstants httpStatusCodes). >> >> Is there some problem in the build process, or is this some type of user error? >> >> Tim > > You should get > > ZnStatusLine code: 511. "a ZnStatusLine(511 Network Authentication Required)" > > If that is not the case, do > > ZnConstants initialize. > > What does ZnConstants class>>#initialize look like for you ? > > The latest version should read like > > initialize > "Forced source code change for automatic initialization: 20170510" > > self initializeHTTPStatusCodes > > Sven

June 27, 2017

Are we able to run pharo images in a read only environment?

by Tim Mackinnon

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)" ] }

June 27, 2017

Re: [Pharo-users] Using Iceberg to edit regular text files ?

by Esteban Lorenzano

> On 27 Jun 2017, at 16:11, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 27 Jun 2017, at 16:05, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> Hi, >> >>> On 27 Jun 2017, at 15:55, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> Is it possible to use Iceberg to edit regular text files directly in Pharo ? >>> >>> Specifically I would like to be able to edit README.md and similar files. Especially when using a all-in-one, the repo on file becomes quite hidden, and the whole idea is to hide the command line anyway, so it feels as if that should have to be possible. >>> >>> Maybe just open a File Browser on the right directory ? >> >> right now, yes. > > But is that an action you can do from Iceberg, like click a button or some menu item ? Did I miss it ? no, I meant: right now yes, it is not possible :) > >> I want to add the possibility to edit/commit regular files from image but is not my priority now (it will arrive, one moment of this year). > > Will Iceberg just pick the repo source files and skip the other resources when committing ? so far, it foes a âfull repository commitâ. > > It does pull all files in, and I lost one commit because it got overwritten (I edited the README.md in the web browser and it got lost after I committed some code). yep. because is like a file export. of course, all that can be improved :) Esteban > >>> Sven >>> >>> PS: I also had the impression that class comment changes did not show up in the diff browser. >> >> iceberg uses old diff mechanism from monticello. >> it *should* be there, but there may be a bug aroundâ¦ >> >> Esteban >> >>> >>> >> >> > >

June 27, 2017

Re: [Pharo-users] Using Iceberg to edit regular text files ?

by Sven Van Caekenberghe

> On 27 Jun 2017, at 16:05, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > >> On 27 Jun 2017, at 15:55, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Is it possible to use Iceberg to edit regular text files directly in Pharo ? >> >> Specifically I would like to be able to edit README.md and similar files. Especially when using a all-in-one, the repo on file becomes quite hidden, and the whole idea is to hide the command line anyway, so it feels as if that should have to be possible. >> >> Maybe just open a File Browser on the right directory ? > > right now, yes. But is that an action you can do from Iceberg, like click a button or some menu item ? Did I miss it ? > I want to add the possibility to edit/commit regular files from image but is not my priority now (it will arrive, one moment of this year). Will Iceberg just pick the repo source files and skip the other resources when committing ? It does pull all files in, and I lost one commit because it got overwritten (I edited the README.md in the web browser and it got lost after I committed some code). >> Sven >> >> PS: I also had the impression that class comment changes did not show up in the diff browser. > > iceberg uses old diff mechanism from monticello. > it *should* be there, but there may be a bug aroundâ¦ > > Esteban > >> >> > >

June 27, 2017

Re: [Pharo-users] ZnConstants missing 511 in default Pharo 6.0 32 image?

by Sven Van Caekenberghe

> On 27 Jun 2017, at 16:02, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > > Hi, > > I remember that Sven did some changes related to the constants in about month or two months ago. But, I do not think that it was integrated to the Pharo 6 release. Yeah, we forgot to put that in, it (the changed #initialize) is only in Zn #bleedingEdge. The simplest patch for Pharo 6 would be to execute ZnConstants initialize. A full Zn sync would be too much I think. > Juraj > >> El 27-06-2017, a las 15:50, Tim Mackinnon <tim(a)testit.works> escribiÃ³: >> >> Hi - I have been slowly working my way through some of the pharo components and tutorials and when trying out ZnEasy with a password protected api, I got a talkback when I mistyped a password. >> It looks like ZnConstants in a fresh Pharo 6.0 32 image excludes 511 from its constants. The code looks correct (and its defined in the initialize method - ) but when I tried a ZnEasy call which returned 511 I got a walkback showing it as an unrecognized code? (The walkback is looking for 511 in ZnConstants httpStatusCodes). >> >> Is there some problem in the build process, or is this some type of user error? >> >> Tim > >

June 27, 2017

Re: [Pharo-users] Using Iceberg to edit regular text files ?

by Esteban Lorenzano

Hi, > On 27 Jun 2017, at 15:55, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Is it possible to use Iceberg to edit regular text files directly in Pharo ? > > Specifically I would like to be able to edit README.md and similar files. Especially when using a all-in-one, the repo on file becomes quite hidden, and the whole idea is to hide the command line anyway, so it feels as if that should have to be possible. > > Maybe just open a File Browser on the right directory ? right now, yes. I want to add the possibility to edit/commit regular files from image but is not my priority now (it will arrive, one moment of this year). > > Sven > > PS: I also had the impression that class comment changes did not show up in the diff browser. iceberg uses old diff mechanism from monticello. it *should* be there, but there may be a bug aroundâ¦ Esteban > >

June 27, 2017

Re: [Pharo-users] ZnConstants missing 511 in default Pharo 6.0 32 image?

by Sven Van Caekenberghe

Hi Tim, > On 27 Jun 2017, at 15:50, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - I have been slowly working my way through some of the pharo components and tutorials and when trying out ZnEasy with a password protected api, I got a talkback when I mistyped a password. > It looks like ZnConstants in a fresh Pharo 6.0 32 image excludes 511 from its constants. The code looks correct (and its defined in the initialize method - ) but when I tried a ZnEasy call which returned 511 I got a walkback showing it as an unrecognized code? (The walkback is looking for 511 in ZnConstants httpStatusCodes). > > Is there some problem in the build process, or is this some type of user error? > > Tim You should get ZnStatusLine code: 511. "a ZnStatusLine(511 Network Authentication Required)" If that is not the case, do ZnConstants initialize. What does ZnConstants class>>#initialize look like for you ? The latest version should read like initialize "Forced source code change for automatic initialization: 20170510" self initializeHTTPStatusCodes Sven

June 27, 2017