- Pharo-users - lists.pharo.org

VoyageMongo with Metacello project spec in Pharo 6 on MacOS Sierra

by Guillaume Giraud

Hello, I placed this code in a baseline of my package: spec project: 'VoyageMongo' with: [ spec className: #ConfigurationOfVoyageMongo; version: #stable; repository: 'github://pharo-nosql/voyage/mc'; loads: #('mongo tests') ]. Unfortunately, when I load my Package from Pharo6 on MacOS Sierra I get the following error: Error: Unsupported OS platform The first lines of the stack are: BaselineOfPunQLite(Object) error: BaselineOfPunQLite platformLibraryName BaselineOfPunQLite preLoad MetacelloMCVersionpec(MetacelloSpec) doItBlock: In detail: platformLibraryName " Answer a name for the compiled version of the library " Smalltalk os isUnix ifTrue: [ ^ 'unqlite.so' ]. Smalltalk os isWin32 ifTrue: [ ^ 'unqlite.dll' ]. Smalltalk os isMacOSX ifTrue: [ ^ 'unqlite.dylib' ]. self error: 'Unsupported OS platformâ With Pharo6 on MacOsSierra, Â« Smalltalk os isMacOSX Â» return Â« false Â». But Â« Smalltalk os isMacOS Â» return Â« true Â». What can I do? I just need to load Voyage with the configuration of my package ? Thanks.

July 15, 2017

Mysterious problem in loading Pharo

by PBKResearch

Hello I have a problem in loading Pharo images which, until yesterday, loaded without difficulty. All the images showing the problem are Pharo 6 with the Cog VM; older images do not seem to be affected. The first sign of a problem is that, as soon as I start the image, the debug console appears, with several repeats of the message: LoadLibrary(FT2Plugin.dll) (998: Invalid access to memory location.) The other strange thing is that the appearance of some opened windows has changed. Most obviously, the three icons at the top left (close, minimise, expand) are very close together. Also, I think the print size has got a bit smaller, though this is not obvious. I have recently reinstalled some components of Pharo and Moose, trying to solve my problems with PunQLite, so I wondered if I had fouled something up. To check, I made a completely new install of Pharo 6 (#60508) from the Pharo download page in a separate folder. When I start the image, both the strange things above are present, plus a debug window with the message; 'FT2 Error: Freetype2 primitive failed'. So it looks as though something has happened to my system which means that any Pharo 6 image will show these oddities. The images I have tried seem able to run some of my functions correctly, so it's all to do with appearance. I am running on Windows 10 with all recent updates. There was a major update of Windows late yesterday, so it may be that the problems appeared then. Does anyone have any suggestions? Many thanks Peter Kenny

July 15, 2017

Re: [Pharo-users] Fwd: How does instant update work in Pharo?

by Offray Vladimir Luna CÃ¡rdenas

Thanks a lot Ben. I'll share this thread, now that have your answers in the Leo list. Cheers, Offray On 15/07/17 04:40, Ben Coman wrote: > > > On Fri, Jul 7, 2017 at 10:50 PM, Offray Vladimir Luna CÃ¡rdenas > <offray.luna(a)mutabit.com <mailto:offray.luna@mutabit.com>> wrote: > > Hi, > > Grafoscopio brings inspiration from IPython/Jupyter[1][2], Leo > and, of course, Pharo/Smalltalk (among others). Recently Edward > Ream, the main force behind Leo, asked my about the internals of > Pharo and I would like to give him a better answer that the one I > gave[4] with pointers to detailed literature. > > [1] http://ipython.org/ > [2] http://jupyter.org/ > [3] http://leoeditor.com/ > [4] https://groups.google.com/forum/#!topic/leo-editor/rYF21GxraT4 > <https://groups.google.com/forum/#%21topic/leo-editor/rYF21GxraT4> > > So, any details on the following question will be appreciated. > > Cheers, > > Offray > > -------- Forwarded Message -------- > Subject: How does instant update work in Pharo? > Date: Fri, 7 Jul 2017 03:23:21 -0700 (PDT) > From: Edward K. Ream <edreamleo(a)gmail.com> > <mailto:edreamleo@gmail.com> > Reply-To: leo-editor(a)googlegroups.com > <mailto:leo-editor@googlegroups.com> > To: leo-editor <leo-editor(a)googlegroups.com> > <mailto:leo-editor@googlegroups.com> > > > > I'm beginning to wonder what the difference is between the Pharo > way and #511: reload-leo command. > <https://github.com/leo-editor/leo-editor/issues/511> > > How does Pharo handle changes in object format? > > > https://gbracha.blogspot.com.au/2009/07/miracle-of-become.html > http://www.mirandabanda.org/cogblog/2013/09/13/lazy-become-and-a-partial-re… > http://fast.org.ar/live/wp-content/uploads/2015/10/ClementBera-Efficient-su… > https://hal.inria.fr/hal-01152610/document > > > > or methods? > > > https://clementbera.wordpress.com/2013/08/09/the-cog-vm-lookup/ > > > > How does Pharo recover from crashes due to changed method signatures > > > "crash" is quite a loaded term. We "never" ;) crash due to > application code changes. We only get "crashes" from defects in the > VM. What we do get are lockups from damaging the UI loop with never > completing loops or a swarm of debuggers appearing across the screen > each UI cycle. > > You would need to clarify what is meant by "method signature". It > sounds like he may be referring to argument typing. Our method > arguments are not typed, so there are no method signature changes, > thus its NotAProblem(tm). Now to be clear, this doesn't mean > Smalltalk is weakly-typed. Smalltalk is strong-typed. Each object > absolutely knows its type and what message it can respond to. We just > don't type variables. i.e. we have late-bound dynamic type checking > rather than compile time static type checking, which works well for us. > > > , invalid calls, etc? > > > Search for "doesNotUnderstand" in these references... > https://marianopeck.wordpress.com/2011/04/30/smalltalk-reflective-model/ > http://www.mirandabanda.org/bluebook/bluebook_chapter27.html > https://stackoverflow.com/questions/3102695/what-are-the-key-differences-be… > http://wiki.c2.com/?DoesNotUnderstand > > But the best way to understand how it works is to observe it. In a > playground, select the following... > 1 xxxxx > and choose [debug It] from the context men, then <Step Into> every > line of code until the debugger window "Instance of nil did not > understand #xxxxx" appears. Although the first time through you may > want to <Step Over> #findContextSuchThat: and #printString. > > Although I'm curious why it says "Instance of nil did not...." rather > than "Instance of SmallInteger did not..." > > cheers -ben > >

July 15, 2017

Re: [Pharo-users] Fwd: How does instant update work in Pharo?

by Ben Coman

On Fri, Jul 7, 2017 at 10:50 PM, Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com> wrote: > Hi, > > Grafoscopio brings inspiration from IPython/Jupyter[1][2], Leo and, of > course, Pharo/Smalltalk (among others). Recently Edward Ream, the main > force behind Leo, asked my about the internals of Pharo and I would like to > give him a better answer that the one I gave[4] with pointers to detailed > literature. > [1] http://ipython.org/ > [2] http://jupyter.org/ > [3] http://leoeditor.com/ > [4] https://groups.google.com/forum/#!topic/leo-editor/rYF21GxraT4 > > So, any details on the following question will be appreciated. > > Cheers, > > Offray > > -------- Forwarded Message -------- > Subject: How does instant update work in Pharo? > Date: Fri, 7 Jul 2017 03:23:21 -0700 (PDT) > From: Edward K. Ream <edreamleo(a)gmail.com> <edreamleo(a)gmail.com> > Reply-To: leo-editor(a)googlegroups.com > To: leo-editor <leo-editor(a)googlegroups.com> <leo-editor(a)googlegroups.com> > > I'm beginning to wonder what the difference is between the Pharo way and #511: > reload-leo command. <https://github.com/leo-editor/leo-editor/issues/511> > > How does Pharo handle changes in object format? > https://gbracha.blogspot.com.au/2009/07/miracle-of-become.html http://www.mirandabanda.org/cogblog/2013/09/13/lazy-become-and-a-partial-re… http://fast.org.ar/live/wp-content/uploads/2015/10/ClementBera-Efficient-su… https://hal.inria.fr/hal-01152610/document > or methods? > https://clementbera.wordpress.com/2013/08/09/the-cog-vm-lookup/ > How does Pharo recover from crashes due to changed method signatures > "crash" is quite a loaded term. We "never" ;) crash due to application code changes. We only get "crashes" from defects in the VM. What we do get are lockups from damaging the UI loop with never completing loops or a swarm of debuggers appearing across the screen each UI cycle. You would need to clarify what is meant by "method signature". It sounds like he may be referring to argument typing. Our method arguments are not typed, so there are no method signature changes, thus its NotAProblem(tm). Now to be clear, this doesn't mean Smalltalk is weakly-typed. Smalltalk is strong-typed. Each object absolutely knows its type and what message it can respond to. We just don't type variables. i.e. we have late-bound dynamic type checking rather than compile time static type checking, which works well for us. > , invalid calls, etc? > Search for "doesNotUnderstand" in these references... https://marianopeck.wordpress.com/2011/04/30/smalltalk-reflective-model/ http://www.mirandabanda.org/bluebook/bluebook_chapter27.html https://stackoverflow.com/questions/3102695/what-are-the-key-differences-be… http://wiki.c2.com/?DoesNotUnderstand But the best way to understand how it works is to observe it. In a playground, select the following... 1 xxxxx and choose [debug It] from the context men, then <Step Into> every line of code until the debugger window "Instance of nil did not understand #xxxxx" appears. Although the first time through you may want to <Step Over> #findContextSuchThat: and #printString. Although I'm curious why it says "Instance of nil did not...." rather than "Instance of SmallInteger did not..." cheers -ben

July 15, 2017

Re: [Pharo-users] Glamour: update presenter with new text

by Hilaire

Thanks for the updates on both the internal dependencies and the ListPresentation. >From this browser, I deduced a second simpler browser for only one script. It was easy to do so thanks to your tips (attached pic). With this simpler script editor, when I open a script, I like it opens on the compute method, because it is a mandatory method in a script. I was doing it like browser := Nautilus openOnClass: scriptClass selector: #compute. I guess, there is a way to do so with the Glamour browser ? Thanks Hilaire -- Dr. Geo http://drgeo.eu

July 15, 2017

Re: [Pharo-users] Creating the smallest server runtime footprint

by Pavel Krivanek

If you want to stay with Pharo 6 image, you can try the bootstrapped version of the minimal image: https://ci.inria.fr/pharo/view/6.0-SysConf/job/Pharo-6.0-Step-04-01-Configu… -- Pavel 2017-07-15 10:33 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > Try the Pharo 7 metacello image (=Pharo 7 minimal image that the CI is > already converting to 64bit). There should be no problem with STON because > whole Pharo is loaded into it using metacello and filetree. Pharo 6 minimal > image is done differently (by shrinking) and not so well tested. > > For the conversion of 32-bit image to 64-bit image you need a VMMaker > image: > https://ci.inria.fr/pharo/job/Spur-Git-Tracker/ > lastSuccessfulBuild/artifact/vmmaker-image.zip > and then evaluate: > ./pharo generator.image eval "[Spur32to64BitBootstrap new bootstrapImage: > 'conversion.image'] on: AssertionFailure do: [ :fail | fail > resumeUnchecked: nil ]" > > -- Pavel > > > > 2017-07-15 10:19 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > >> Hi Pavel - thanks for getting me to the point where I could even have a >> minimal image. As Iâm on the edge of my Pharo knowledge here, Iâll try and >> run with this as best I can. >> >> Iâd been using the 6.0 image you suggested to me - but maybe I could use >> a 70 image with Pharo 6 for a while (until the VM diverges) right? >> >> The bit I havenât quite understood however, is how the 64bit image is >> created - as your reference is to a 32bit version? Is the 64bit one >> converted from 32 in a later stage? (For AWS Lambda I need 64bit) - am I >> right in thinking the pipeline stage after this one is the one you sent me >> - and the travis.yml file shows me what it does? But I canât see a >> trivis.yml in the conversion stage so Iâm not sure how it does that. >> (Question - how do I see what the pipelines do to answer my own questions?) >> >> I was hoping that there was a basic image that got me up to metacello >> baseline level to load git file tree packages/baselines in my own repo as >> well baselines on the internet. The one you sent me is fairly close to that >> (its just missing STON in the image and seems to have an issue with >> resolving undeclared classes that get loaded in - should do a fogbugz on >> that?) >> >> The follow-on from a metacello image is how we can get people to create >> better baselines that give you more minimal loading options (e.g. >> conditionally leave out the test cases perhaps) >> >> Tim >> >> On 15 Jul 2017, at 08:24, Pavel Krivanek <pavel.krivanek(a)gmail.com> >> wrote: >> >> Hi Tim, >> >> you can base the your work on the bootstrapped image, see >> https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/, file >> Pharo7.0-core-*.zip >> >> This image does not have a lot of basic components like Monticello or >> network but it has a compiler so the code can be imported as *.st files. >> Then we have Pharo7.0-monticello-*.zip which will be easier to use and >> probably can fit your needs. Monticello and network support are included. >> But you cannot use baselines nor configurations to load your code. >> >> -- Pavel >> >> 2017-07-14 9:59 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: >> >>> Hi - buoyed by the success of a minimal image (thanks Pavel), I'm >>> wondering if I can get even smaller. >>> >>> There are lots of .so's in the vm which wouldn't make sense on a server >>> once deployed - sound, maybe libgit ... >>> >>> Is there a list of the essential ones, or tips on what I can strip out >>> of the Linux deployment? I also recall that i can leave out .sources and >>> .changes as well right? >>> >>> Tim >>> >>> Sent from my iPhone >>> >>> >> >> >

July 15, 2017

Re: [Pharo-users] Creating the smallest server runtime footprint

by Pavel Krivanek

Try the Pharo 7 metacello image (=Pharo 7 minimal image that the CI is already converting to 64bit). There should be no problem with STON because whole Pharo is loaded into it using metacello and filetree. Pharo 6 minimal image is done differently (by shrinking) and not so well tested. For the conversion of 32-bit image to 64-bit image you need a VMMaker image: https://ci.inria.fr/pharo/job/Spur-Git-Tracker/lastSuccessfulBuild/artifact… and then evaluate: ./pharo generator.image eval "[Spur32to64BitBootstrap new bootstrapImage: 'conversion.image'] on: AssertionFailure do: [ :fail | fail resumeUnchecked: nil ]" -- Pavel 2017-07-15 10:19 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > Hi Pavel - thanks for getting me to the point where I could even have a > minimal image. As Iâm on the edge of my Pharo knowledge here, Iâll try and > run with this as best I can. > > Iâd been using the 6.0 image you suggested to me - but maybe I could use a > 70 image with Pharo 6 for a while (until the VM diverges) right? > > The bit I havenât quite understood however, is how the 64bit image is > created - as your reference is to a 32bit version? Is the 64bit one > converted from 32 in a later stage? (For AWS Lambda I need 64bit) - am I > right in thinking the pipeline stage after this one is the one you sent me > - and the travis.yml file shows me what it does? But I canât see a > trivis.yml in the conversion stage so Iâm not sure how it does that. > (Question - how do I see what the pipelines do to answer my own questions?) > > I was hoping that there was a basic image that got me up to metacello > baseline level to load git file tree packages/baselines in my own repo as > well baselines on the internet. The one you sent me is fairly close to that > (its just missing STON in the image and seems to have an issue with > resolving undeclared classes that get loaded in - should do a fogbugz on > that?) > > The follow-on from a metacello image is how we can get people to create > better baselines that give you more minimal loading options (e.g. > conditionally leave out the test cases perhaps) > > Tim > > On 15 Jul 2017, at 08:24, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Hi Tim, > > you can base the your work on the bootstrapped image, see > https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/, file > Pharo7.0-core-*.zip > > This image does not have a lot of basic components like Monticello or > network but it has a compiler so the code can be imported as *.st files. > Then we have Pharo7.0-monticello-*.zip which will be easier to use and > probably can fit your needs. Monticello and network support are included. > But you cannot use baselines nor configurations to load your code. > > -- Pavel > > 2017-07-14 9:59 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > >> Hi - buoyed by the success of a minimal image (thanks Pavel), I'm >> wondering if I can get even smaller. >> >> There are lots of .so's in the vm which wouldn't make sense on a server >> once deployed - sound, maybe libgit ... >> >> Is there a list of the essential ones, or tips on what I can strip out of >> the Linux deployment? I also recall that i can leave out .sources and >> .changes as well right? >> >> Tim >> >> Sent from my iPhone >> >> > >

July 15, 2017

Re: [Pharo-users] Creating the smallest server runtime footprint

by Tim Mackinnon

Hi Pavel - thanks for getting me to the point where I could even have a minimal image. As Iâm on the edge of my Pharo knowledge here, Iâll try and run with this as best I can. Iâd been using the 6.0 image you suggested to me - but maybe I could use a 70 image with Pharo 6 for a while (until the VM diverges) right? The bit I havenât quite understood however, is how the 64bit image is created - as your reference is to a 32bit version? Is the 64bit one converted from 32 in a later stage? (For AWS Lambda I need 64bit) - am I right in thinking the pipeline stage after this one is the one you sent me - and the travis.yml file shows me what it does? But I canât see a trivis.yml in the conversion stage so Iâm not sure how it does that. (Question - how do I see what the pipelines do to answer my own questions?) I was hoping that there was a basic image that got me up to metacello baseline level to load git file tree packages/baselines in my own repo as well baselines on the internet. The one you sent me is fairly close to that (its just missing STON in the image and seems to have an issue with resolving undeclared classes that get loaded in - should do a fogbugz on that?) The follow-on from a metacello image is how we can get people to create better baselines that give you more minimal loading options (e.g. conditionally leave out the test cases perhaps) Tim > On 15 Jul 2017, at 08:24, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Hi Tim, > > you can base the your work on the bootstrapped image, see https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/ <https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/>, file Pharo7.0-core-*.zip > > This image does not have a lot of basic components like Monticello or network but it has a compiler so the code can be imported as *.st files. > Then we have Pharo7.0-monticello-*.zip which will be easier to use and probably can fit your needs. Monticello and network support are included. But you cannot use baselines nor configurations to load your code. > > -- Pavel > > 2017-07-14 9:59 GMT+02:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: > Hi - buoyed by the success of a minimal image (thanks Pavel), I'm wondering if I can get even smaller. > > There are lots of .so's in the vm which wouldn't make sense on a server once deployed - sound, maybe libgit ... > > Is there a list of the essential ones, or tips on what I can strip out of the Linux deployment? I also recall that i can leave out .sources and .changes as well right? > > Tim > > Sent from my iPhone > >

July 15, 2017

Re: [Pharo-users] Creating the smallest server runtime footprint

by Pavel Krivanek

Hi Tim, you can base the your work on the bootstrapped image, see https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/, file Pharo7.0-core-*.zip This image does not have a lot of basic components like Monticello or network but it has a compiler so the code can be imported as *.st files. Then we have Pharo7.0-monticello-*.zip which will be easier to use and probably can fit your needs. Monticello and network support are included. But you cannot use baselines nor configurations to load your code. -- Pavel 2017-07-14 9:59 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > Hi - buoyed by the success of a minimal image (thanks Pavel), I'm > wondering if I can get even smaller. > > There are lots of .so's in the vm which wouldn't make sense on a server > once deployed - sound, maybe libgit ... > > Is there a list of the essential ones, or tips on what I can strip out of > the Linux deployment? I also recall that i can leave out .sources and > .changes as well right? > > Tim > > Sent from my iPhone > >

July 15, 2017

Re: [Pharo-users] Creating the smallest server runtime footprint

by Tim Mackinnon

Hi - the script I'm using is in https://gitlab.com/macta/PharoLambda - it's nothing fancy, look at the Gitlab .yml file. This is all Linux running in an ubuntu docker image on Gitlab CI. Tim Sent from my iPhone Sent from my iPhone > On 15 Jul 2017, at 06:27, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Hi Tim, > > 2017-07-14 4:59 GMT-03:00 Tim Mackinnon <tim(a)testit.works>: >> Hi - buoyed by the success of a minimal image (thanks Pavel), I'm wondering if I can get even smaller. > > Can you share a script to reproduce the steps to build a minimal image? > > Is it reproducible under Windows? > > Cheers, > > HernÃ¡n >

July 15, 2017