November 2018 - Pharo-users

Re: can't debug TinyBlog in the Pharo MOOC

by iu136

EstebanLM wrote > Hi, > > You are missing to initialise the Voyage repository. > I donât know how is explained in the Mooc, but you will probably need to > do something like: > > VOMemoryRepository new enableSingleton. > > Cheers, > Esteban Hi Esteban. actually I'm using an External Mongo database and in the MOOC the initialization of Voyage Mongo repository, is done like: TBBlog class >> initializeLocalhostMongoDB | repository | repository := VOMongoRepository database: 'tinyblog'. repository enableSingleton. TBBlog class >> reset self initializeLocalhostMongoDB and in my code I'm doing exactly like above. but interestingly when I wanted to reset the cache of Voyage by: VORepository current reset again I've got another Error saying: "MessageNotUnderstood: receiver of "reset" is nill". thanks anyway! -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 22, 2018

Re: [Pharo-users] VPS difficulties

by Hans-Martin Mosner

It can't find the display drivers since the appropriate 32 bit libraries are missing. Use the 'ldd' command on the VM binary and on the shared libraries in its directory to find out which ones you're missing. Cheers, Hans-Martin Am 22. November 2018 4:22:19 nachm. schrieb horrido <horrido.hobbies(a)gmail.com>: > I'm running 64-bit Debian in a VirtualBox image on my Mac. > > When I install 64-bit Pharo, it works fine. When I install 32-bit Pharo, I > get the error message below. What's the difference??? Why can one find the > display driver and the other can't? This makes no sense. > > Earlier, people have been telling me to use './pharo-ui Pharo.image &'. Is > this no longer kosher? What am I doing wrong? > > > > Fred Kaiser Borg wrote >> Those errors are not related to a 32 or 64 bits problem. The issue looks >> like you've launched pharo-ui which looks for a physical screen that >> isn't there. Are you trying to run pharo-ui in a debian VPS ? >> >> You should run 'pharo' and 'pharo-ui', something like this: >> >> $ pharo myApplication.image >> >> Search on google for 'pharo headless', you should find plenty of example. >> >> HTH, >> >> Fred >> >> On 22/11/2018 13:31, horrido wrote: >>> I ran 32-bit Pharo under 64-bit Debian and got this error: >>> >>> [1] 8127 >>> richard@debian:~/pharo32$ could not find display driver vm-display-X11; >>> either: >>> - check that >>> /home/richard/pharo32/pharo-vm/lib/pharo/5.0-201806281256//vm-display-X11.so >>> exists, or >>> - use the '-plugins >> <path> >> ' option to tell me where it is, or >>> - remove DISPLAY from your environment. >>> ./pharo-ui: line 11: 8131 Aborted >>> "$DIR"/"pharo-vm/pharo" >>> "$@" >>> >>> ---------- >>> >>> I thought you could always run 32-bit software in a 64-bit OS, but I >>> guess >>> I'm wrong. >>> >>> >>> >>> Sean P. DeNigris wrote >>>> horrido wrote >>>>> it threw up a bunch of errors. >>>> Can you be more specific and did you try Mariano's suggestion about >>>> 32-bit >>>> libs? >>>> >>>> >>>> >>>> ----- >>>> Cheers, >>>> Sean >>>> -- >>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >>> >>> >>> >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 22, 2018

Re: [Pharo-users] VPS difficulties

by horrido

Okay, I've resolved everything. First, the reason why I'm getting the 'pthread_setschedparam failed' error when I run Pharo under Debian is because it must be run as 'root'! Don't ask me why, but that's the reason why Pharo can't set thread priorities. (This wasn't an issue under Ubuntu Server â go figure.) Second, I am now using Pharo's own SHA256 class. It's probably not as secure (because it doesn't use a salt value) and not as quick to execute (not being C code), but for my purpose, it doesn't really matter. So I can use DigitalOcean or OVH to run my web server in a VPS. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 22, 2018

Re: [Pharo-users] can't debug TinyBlog in the Pharo MOOC

by Esteban Lorenzano

Hi, You are missing to initialise the Voyage repository. I donât know how is explained in the Mooc, but you will probably need to do something like: VOMemoryRepository new enableSingleton. Cheers, Esteban > On 22 Nov 2018, at 17:51, iu136 via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: iu136 <iu136(a)yahoo.com> > Subject: can't debug TinyBlog in the Pharo MOOC > Date: 22 November 2018 at 17:51:12 CET > To: pharo-users(a)lists.pharo.org > > > hi guys > I'm following the Pharo MOOC and I'm at Week 4. the other day, I was trying > to implement TinyBlog: Data Persistency using Voyage and Mongo, when I tried > to compile the code, I've got an Error. the title of Error says: > "MessageNotUnderstood: receiver of "save:" is nil", and it refers to > TBMBlog>>writeBlogPost. > > TBMBlog>>writeBlogPost: aTBMPost > posts add: aTBMPost. > aTBMPost save. > self save . > > thanks for your answers! > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > >

Nov. 22, 2018

[ANN] JSON schema implementation

by Norbert Hartl

JSONSchema =========== This is an implementation of JSON Schema for the pharo language. It is used to define the structure and values of a JSON string and to validate it. The schema itself can be externalized for being consumed by a third party. I like to announce the availability of a JSON schema implementation for pharo. As part of my implementation of OpenAPI (which is to be released a bit later) I factored out the JSON schema part into its own repository because I think it is useful. I release it even it is not really finished. Code is mostly undocumented and a lot of features are missing from the full spec. I will improve it slowly and add features as I need them or they being requested Hope you like it! Norbert ==== The documentation so far (from https://github.com/zweidenker/JSONSchema <https://github.com/zweidenker/JSONSchema>) It can be loaded by downloading it in pharo via Metacello new repository: 'github://zweidenker/JSONSchema'; baseline: #JSONSchema; load Defining a schema ------------------------- These are the expression to create a schema model inside pharo. schema := { #name -> JSONSchema string. #dateAndTime -> (JSONSchema stringWithFormat: 'date-time'). #numberOfPets -> JSONSchema number } asJSONSchema. defines as schema that can parse the following JSON: jsonString := '{ "name" : "John Doe", "dateAndTime" : "1970-01-01T14:00:00", "numberOfPets" : 3 }'. Reading/Writing a value using a schema ------------------------------------------------------ To parse the value from JSON we only need to invoke: value := schema read: jsonString The object in value will have name as a string, dateAndTime as a DateAndTime object and numberOfPets as a SmallInteger object. The schema can also be used to write out the value as JSON. This is especially useful if we want to ensure that only valid JSON is written. For this invoke jsonString := schema write: value. Serialize/Materialize a schema ---------------------------------------- Addtionally to reading and writing objects a schema can be serialized to string. schemaString := NeoJSONWriter toStringPretty: schema. gives { "type" : "object", "properties" : { "name" : { "type" : "string" }, "numberOfPets" : { "type" : "number" }, "dateAndTime" : { "type" : "string", "format" : "date-time" } } } If we would get a schema as string we can instantiate by invoking schema := JSONSchema fromString: schemaString. Nested schemas ----------------------- Schemas can be nested in any depth. And it can be specified by using the literal Array syntax. schema := { #name -> JSONSchema string. #address -> { #street -> JSONSchema string. #number -> JSONSchema number } } asJSONSchema Constraints --------------- JSON Schema has a defined set of constraints that can be specified. E.g. for a number the inerval of the value can be specified by numberSchema := JSONSchema number. numberSchema interval minimum: 1; exclusiveMaximum: 100 constraining the number value to be greater or equal to 1 and smaller than 100.

Nov. 22, 2018

can't debug TinyBlog in the Pharo MOOC

by iu136

hi guys I'm following the Pharo MOOC and I'm at Week 4. the other day, I was trying to implement TinyBlog: Data Persistency using Voyage and Mongo, when I tried to compile the code, I've got an Error. the title of Error says: "MessageNotUnderstood: receiver of "save:" is nil", and it refers to TBMBlog>>writeBlogPost. TBMBlog>>writeBlogPost: aTBMPost posts add: aTBMPost. aTBMPost save. self save . thanks for your answers! -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 22, 2018

Re: [Pharo-users] VPS difficulties

by Ben Coman

On Thu, 22 Nov 2018 at 23:22, horrido <horrido.hobbies(a)gmail.com> wrote: > I'm running 64-bit Debian in a VirtualBox image on my Mac. > > When I install 64-bit Pharo, it works fine. When I install 32-bit Pharo, I > get the error message below. What's the difference??? Why can one find the > display driver and the other can't? This makes no sense. > Apart from the much larger images possible, a big driver to produce 64-bit Pharo is that Linux installations were becoming predominantly 64-bit and by default don't pre-install all the 32 bit libraries. e.g... https://www.maketecheasier.com/run-32-bit-apps-in-64-bit-linux/ When Pharo was *only* 32-bit, there were instructions on which 32-libs were required. I'm not sure were they are now. (Maybe its worth keeping them around for such cases, although it seems a backward step.) You might find something at forum.world.st. Ah, I see Sven has some good info. > > Earlier, people have been telling me to use './pharo-ui Pharo.image &'. Is > this no longer kosher? What am I doing wrong? > It depends on whether you download the standalone or using zero-conf. This inconsistency has bitten me a few times, but I was familiar enough to quickly determine what was going. Consistency would be good, but we'd need to break the long standing pattern of one or the other. cheers -ben

Nov. 22, 2018

Re: [Pharo-users] VPS difficulties

by Sven Van Caekenberghe

Using Linux requires certain skills/knowledge, this has nothing to do with Pharo or Smalltalk. To run 32-bit binaries on a 64-bit system you need 32-bit libraries. This might help (although maybe it is not totally up to date for Pharo 7) https://github.com/svenvc/pharo-server-tools/blob/master/ubuntu-32bit-suppo… You can check the dependencies of binaries and dynamic libraries with ldd. They have to be resolved correctly. $ uname -a Linux sigfox-1 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ file bin/pharo-vm/pharo bin/pharo-vm/pharo: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=dcf3b690e793d6960e1dbccd36bd0b3938019471, not stripped $ ldd bin/pharo-vm/pharo linux-gate.so.1 => (0xf7730000) libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf76d2000) libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf76cd000) libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf76b0000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf74fa000) /lib/ld-linux.so.2 (0x565fe000) pharo and pharo-ui are just scripts I would also strongly recommend not using native (FFI) libraries (at first). You must also understand the difference between a UI based and headless system. > On 22 Nov 2018, at 16:21, horrido <horrido.hobbies(a)gmail.com> wrote: > > I'm running 64-bit Debian in a VirtualBox image on my Mac. > > When I install 64-bit Pharo, it works fine. When I install 32-bit Pharo, I > get the error message below. What's the difference??? Why can one find the > display driver and the other can't? This makes no sense. > > Earlier, people have been telling me to use './pharo-ui Pharo.image &'. Is > this no longer kosher? What am I doing wrong? > > > > Fred Kaiser Borg wrote >> Those errors are not related to a 32 or 64 bits problem. The issue looks >> like you've launched pharo-ui which looks for a physical screen that >> isn't there. Are you trying to run pharo-ui in a debian VPS ? >> >> You should run 'pharo' and 'pharo-ui', something like this: >> >> $ pharo myApplication.image >> >> Search on google for 'pharo headless', you should find plenty of example. >> >> HTH, >> >> Fred >> >> On 22/11/2018 13:31, horrido wrote: >>> I ran 32-bit Pharo under 64-bit Debian and got this error: >>> >>> [1] 8127 >>> richard@debian:~/pharo32$ could not find display driver vm-display-X11; >>> either: >>> - check that >>> /home/richard/pharo32/pharo-vm/lib/pharo/5.0-201806281256//vm-display-X11.so >>> exists, or >>> - use the '-plugins >> <path> >> ' option to tell me where it is, or >>> - remove DISPLAY from your environment. >>> ./pharo-ui: line 11: 8131 Aborted >>> "$DIR"/"pharo-vm/pharo" >>> "$@" >>> >>> ---------- >>> >>> I thought you could always run 32-bit software in a 64-bit OS, but I >>> guess >>> I'm wrong. >>> >>> >>> >>> Sean P. DeNigris wrote >>>> horrido wrote >>>>> it threw up a bunch of errors. >>>> Can you be more specific and did you try Mariano's suggestion about >>>> 32-bit >>>> libs? >>>> >>>> >>>> >>>> ----- >>>> Cheers, >>>> Sean >>>> -- >>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >>> >>> >>> >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Nov. 22, 2018

Re: [Pharo-users] VPS difficulties

by horrido

I'm running 64-bit Debian in a VirtualBox image on my Mac. When I install 64-bit Pharo, it works fine. When I install 32-bit Pharo, I get the error message below. What's the difference??? Why can one find the display driver and the other can't? This makes no sense. Earlier, people have been telling me to use './pharo-ui Pharo.image &'. Is this no longer kosher? What am I doing wrong? Fred Kaiser Borg wrote > Those errors are not related to a 32 or 64 bits problem. The issue looks > like you've launched pharo-ui which looks for a physical screen that > isn't there. Are you trying to run pharo-ui in a debian VPS ? > > You should run 'pharo' and 'pharo-ui', something like this: > > $ pharo myApplication.image > > Search on google for 'pharo headless', you should find plenty of example. > > HTH, > > Fred > > On 22/11/2018 13:31, horrido wrote: >> I ran 32-bit Pharo under 64-bit Debian and got this error: >> >> [1] 8127 >> richard@debian:~/pharo32$ could not find display driver vm-display-X11; >> either: >> - check that >> /home/richard/pharo32/pharo-vm/lib/pharo/5.0-201806281256//vm-display-X11.so >> exists, or >> - use the '-plugins > <path> > ' option to tell me where it is, or >> - remove DISPLAY from your environment. >> ./pharo-ui: line 11: 8131 Aborted >> "$DIR"/"pharo-vm/pharo" >> "$@" >> >> ---------- >> >> I thought you could always run 32-bit software in a 64-bit OS, but I >> guess >> I'm wrong. >> >> >> >> Sean P. DeNigris wrote >>> horrido wrote >>>> it threw up a bunch of errors. >>> Can you be more specific and did you try Mariano's suggestion about >>> 32-bit >>> libs? >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 22, 2018

Re: [Pharo-users] MetaLink>>level: failing?

by Vitor Medina Cruz

It works like a charm now!!! Thanks! On Tue, Nov 13, 2018 at 11:23 AM Marcus Denker <marcus.denker(a)inria.fr> wrote: > More progressâ¦ in the latest Pharo7 this is now working... (#operation > reifies the original operation): > > | link choice | > > choice := true. > link := MetaLink new metaObject: [ :operation | > UIManager default alert: > 'Linked Version'. > choice ifTrue: [operation > value ]. > ]; > selector: #value:; > arguments: #(#operation); > control: #instead. > > > (TestMetaLink >> #execute) ast link: link. > TestMetaLink new execute. > link uninstall. > > No need for using #level: as #operation for method execution is reifying > the *original* method that would have been executed without the link. > > (this then is, too, what will be used to make finally âturning offâ > instead links work correctly: if the instead link is not active (due to a > condition or level), it will > instead execute âoperation valueâ, that is, what would have been done > without the #instead link present. > > Marcus > > On 7 Nov 2018, at 15:47, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > I added > > > https://pharo.fogbugz.com/f/cases/22642/instead-links-and-meta-level-origin… > > as a workaround, you can use a #before link with an explicit return: > > > choice := true. > link := MetaLink new metaObject: [ :object :selector :arguments :context | > UIManager default alert: > 'Linked Version'. > choice ifTrue: [ context > sender sender sender sender return: (object perform: selector > withArguments: arguments)]. > ]; > selector: #value:value:value:value:; > arguments: #(#object #selector #arguments #context); > control: #before; > level: 0. > > (TestMetaLink >> #execute) ast link: link. > TestMetaLink new execute. > link uninstall. > > (yes, the context sender sender sender shows that #context needs to do > the right thing when using level: 0. or notâ¦ another thing to fix) > > Marcus > > On 7 Nov 2018, at 15:08, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hello, > > I added a fist issue (and fix) for parts of the problem > > > https://pharo.fogbugz.com/f/cases/22641/Semantic-analysis-needs-to-take-ins… > https://github.com/pharo-project/pharo/pull/1960 > > But after this, it does not work as the level just turns off calling the > meta level code, but does not execute the > original code where the #instead is put. > (#instead in general needs more work in this implementation). > > I will open another issue for that. > > Marcus > > On 31 Oct 2018, at 18:03, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > > Thanks! Is there an issue on fogbuzz where I can be notified of > resolution? Do you need me to create it? > > After that how can update the code? Software update is safe or should I > create a new image? > > regards, > Vitor > > On Mon, Oct 29, 2018 at 12:08 PM Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> >> >> On 25 Oct 2018, at 01:33, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: >> >> Hello, >> >> I am playing with MetaLink, really cool!, but I am having issues that I >> am unsure if it's some erro or if I am doing something wrong (I am using >> Pharo 6.1 32 bits in windows.). Consider: >> >> TestMetaLink>>execute >> UIManager default alert: 'Actual Version'. >> >> And in Playground: >> >> | link | >> >> link := MetaLink new metaObject: [ :object | UIManager default alert: >> 'Linked Version' ]; >> selector: #value:; >> arguments: #(#object); >> control: #instead. >> >> >> (TestMetaLink >> #execute) ast link: link. >> TestMetaLink new execute. >> link uninstall. >> >> This works as expected, an alert with 'Linked Version' is promped. But >> then suppose I want to execute the actual node alongside with the linked >> one considering some condition: >> >> | link choice | >> >> choice := true. >> link := MetaLink new metaObject: [ :object :selector :arguments | >> UIManager default alert: >> 'Linked Version'. >> choice ifTrue: [ object >> perform: selector withArguments: arguments]. >> ]; >> selector: #value:value:value:; >> arguments: #(#object #selector #arguments); >> control: #instead; >> * level: 0*. >> >> >> (TestMetaLink >> #execute) ast link: link. >> TestMetaLink new execute. >> link uninstall. >> >> As I understand, level:0 is necessary in order to avoid an infinite loop, >> but then I get an error: >> >> KeyNotFound: key #RFArgumentsReificationVar not found in Dictionary >> >> Am I doing something wrong? Is that an error? >> >> Hello, >> >> Yes, this looks like a bug. I will fix it over the next days. >> >> Marcus >> >> >> >> >> >> >> >> > > >

Nov. 22, 2018