- Pharo-users - lists.pharo.org

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

by Tim Mackinnon

Ah - I see. Is this where the minimal images would help? As in CI would just take a base image and just load zn and hence run the new initialise anyway and so avoid this? I'm a bit confused how how base images are built to even have this problem In a world of CI? Tim Sent from my iPhone > On 27 Jun 2017, at 17:55, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> 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] PharoJS

by Craig Latta

Hi-- Aik-Siong writes: > Craig Latta is doing something interesting[1] with SqueakJS which is > an optimized Smalltalk VM in JavaScript and HTML5. It is supposedly > able to run Smalltalk fast inside the browser and access the > JavaScript world freely. I think this route will benefit greatly from > WebAssembly. I'm also making it run Pharo. thanks, -C [1] https://caffeine.js.org -- Craig Latta Black Page Digital Amsterdam :: San Francisco craig(a)blackpagedigital.com +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)

June 27, 2017

Re: [Pharo-users] PharoCloud drops VM hosting and focuses on Ephemeric Cloud

by mikefilonov

Hi Yuriy, >So is it for static applications only? Short answer is "no". The ephemeric cloud only restricts saving files to local disk. This means, only Image persistence is not working with Ephemeric cloud. However, any other form of persistence works. You can connect Images in Ephemeric cloud to databases (ex.: http://docs.swarm.pharocloud.com/article/usecase_do_mongo ), file stores, REST API services... Basically, in ephemeric cloud only code is static, but data is not. If you have a concrete use case, contact me at support(a)pharocloud.com (or in pharo discordapp chat) and we can discuss options for you project. -- View this message in context: http://forum.world.st/PharoCloud-drops-VM-hosting-and-focuses-on-Ephemeric-… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 27, 2017

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

by Esteban A. Maringolo

2017-06-27 16:15 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >> On 27 Jun 2017, at 21:00, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> 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: [SNIP] > But it is really hard to find the cause. > > That being said, these lambda servers can only work well if they keep instances alive for longer when there is enough traffic. AFAIU the purpose of AWS Lambda is to have "fire and forget" kind of functions, mainly stateless consumers of single purpose functions, with "infinite" transparent scalability. Like for processing ads clicks/impressions, receiving data from lots of mobile/IoT devices, etc. Regards, Esteban A. Maringolo

June 27, 2017

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

by Sven Van Caekenberghe

> On 27 Jun 2017, at 18:05, Tim Mackinnon <tim(a)testit.works> wrote: > > 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? That is really strange, it should just work (it does for me using the zero config scripts). I would try to use absolute (resolved) paths as much as possible. > 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? Yes, that is ok. > 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] Are we able to run pharo images in a read only environment?

by Sven Van Caekenberghe

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

June 27, 2017

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