February 2019 - Pharo-users

Re: [Pharo-users] About Iceberg

by Tim Mackinnon

Yes I agree - when there is so much discussion and debate going on, its easy to lose sight of the hard work and determination that went into getting us to this brave new world. I too want to shout a big thank you for the tooling and also the support that goes along with that. I love been able to think a bit more polyglot, and use tools/languages more easily side by side - although of course I want to hold on to what makes Smalltalk special (which is tons of stuff). I particularly love being able to feel like its easier to contribute - updating readmeâs and docs is trivial in a web browser now - just correct them and submit a PR. And on the receiving side - GitHub makes it easy to discuss the fix, alter it, or simply approve it. Equally - modern build tools easily detect the change, pull the code and rebuild and package it (and cheap scalable infrastructure). Its also getting easier and easier to submit code fixes too - and the VCS skills you learn doing this are transferable beyond Smalltalk - so its a big win win. So yes guys - thanks for hanging in for us! Tim > On 19 Feb 2019, at 08:50, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > This is a thank you note about Iceberg. > > I have been moving all my external and internal Pharo code to git/tonel/7 and on multiple occasions I have been pleasantly surprised about the functionality and performance of Iceberg. Basically, it just works. > > Finally, Pharo code lives in standard open source and commercial repositories (git, GitHub, Bitbucket, ...), without losing anything. > > I know that it took years to get here and that lots of code and community battles had to be fought. So thank you, to the whole team, you did a great job ! > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

Feb. 19, 2019

Re: [Pharo-users] Pier3 & content management

by Albrecht Baur

thanks for the info - I will give it a try next weeks. On 19.02.19 12:41, Esteban Lorenzano wrote: > Hello, > > Not many people are using it, but it should be not much problem make > it run in Pharo 7 (and with current version of Seaside). > > Esteban > >> On 19 Feb 2019, at 12:03, Albrecht Baur via Pharo-users >> <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> wrote: >> >> >> *From: *Albrecht Baur <baur.albrecht(a)googlemail.com >> <mailto:baur.albrecht@googlemail.com>> >> *Subject: **Pier3 & content management* >> *Date: *19 February 2019 at 12:03:27 CET >> *To: *Any question about pharo is welcome >> <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> >> >> >> Hey, >> >> what is the status of Pier3 + Pier3AddOns ? >> >> -> Seems to me that it is discontinued since Pharo 5, right ? >> >> I'm asking because I look around to see if there is a project usable >> as a starting point of a small web content management module for >> seaside (nothing too complicated / fancy). >> >> Is there something besides Pier that goes into this direction ? >> >> Thanks for hints, >> Albrecht >> >> >

Feb. 19, 2019

Re: [Pharo-users] How do you avoid loading master code which is indirectly referenced by a version in the baseline?

by phil＠highoctane.be

Same boat here. Phil On Tue, Feb 19, 2019, 13:05 Tim Mackinnon <tim(a)testit.works wrote: > Hi Sabine - you raise an important point, and I am interested in us > getting better answers to this too. Hopefully Dale seeâs this and is > thinking about this in Rowen. Repeatable loading is an important enterprise > feature. > > Tim > > > On 18 Feb 2019, at 15:46, Sabine Manaa <manaa.sabine(a)gmail.com> wrote: > > > > For test and deployment, I have to be sure that I know exactly which > versions > > I load and I have to be sure to be able to load exactly the same code > again. > > I do not speak from my projects but from the projects I use. > > > > I found myself asking people again and again to set tags in their > projects > > and being surprised again and again by changed code even though I am > trying > > to load versions (with versions I mean NOT #stable or #master but like > > v2.2.2). > > > > The reason for this problem I then have, is that often in baselines with > > version numbers (e.g. v2.2.2) other projects are referenced but as > master. > > So in consequence, I load version but get master from another project > which > > is referenced indirectly. > > > > For me, that this is not good at all. I was wondering that this seems > not to > > be a problem for others. > > > > I found out that I can put a lock in my baselines preLoadDoIt for those > > indirectly referenced projects. > > > > Examlpe Artefact v1.0.1 > > > > > https://github.com/pharo-contributions/Artefact/blob/v1.0.1/src/BaselineOfA… > > > > loads github://zweidenker/Units/src (which is master). > > > > I found a solution for this: > > > > In the preLoadDoIt of my baseline I lock Units to a certain commit. > > > > preLoadDoIt > > Metacello new > > baseline: 'Units'; > > repository: 'github://zweidenker/Units:98d5a3d/src'; > > lock. > > > > This solves my problem in this example. > > > > Disadvantage is that I have to analyze everything which is loaded from > the > > projects I use and create a lock for it. > > > > Questions: > > 1.) Wouldn't it make sense to have some mechanism, perhaps in Rowan then, > > where I can say that a project which has a number can only reference > other > > projects with numbers? This would avoid the whole problem > > 2.) How do others solve this problem? > > > > addendum: I do not speak about project versions which are in development, > > here #stable or master are great features. But sometime when a project > has a > > certain state, and it gets a version, then it should not change..imho > > > > > > > > -- > > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > > > > >

Feb. 19, 2019

Re: [Pharo-users] How do you avoid loading master code which is indirectly referenced by a version in the baseline?

by Tim Mackinnon

Hi Sabine - you raise an important point, and I am interested in us getting better answers to this too. Hopefully Dale seeâs this and is thinking about this in Rowen. Repeatable loading is an important enterprise feature. Tim > On 18 Feb 2019, at 15:46, Sabine Manaa <manaa.sabine(a)gmail.com> wrote: > > For test and deployment, I have to be sure that I know exactly which versions > I load and I have to be sure to be able to load exactly the same code again. > I do not speak from my projects but from the projects I use. > > I found myself asking people again and again to set tags in their projects > and being surprised again and again by changed code even though I am trying > to load versions (with versions I mean NOT #stable or #master but like > v2.2.2). > > The reason for this problem I then have, is that often in baselines with > version numbers (e.g. v2.2.2) other projects are referenced but as master. > So in consequence, I load version but get master from another project which > is referenced indirectly. > > For me, that this is not good at all. I was wondering that this seems not to > be a problem for others. > > I found out that I can put a lock in my baselines preLoadDoIt for those > indirectly referenced projects. > > Examlpe Artefact v1.0.1 > > https://github.com/pharo-contributions/Artefact/blob/v1.0.1/src/BaselineOfA… > > loads github://zweidenker/Units/src (which is master). > > I found a solution for this: > > In the preLoadDoIt of my baseline I lock Units to a certain commit. > > preLoadDoIt > Metacello new > baseline: 'Units'; > repository: 'github://zweidenker/Units:98d5a3d/src'; > lock. > > This solves my problem in this example. > > Disadvantage is that I have to analyze everything which is loaded from the > projects I use and create a lock for it. > > Questions: > 1.) Wouldn't it make sense to have some mechanism, perhaps in Rowan then, > where I can say that a project which has a number can only reference other > projects with numbers? This would avoid the whole problem > 2.) How do others solve this problem? > > addendum: I do not speak about project versions which are in development, > here #stable or master are great features. But sometime when a project has a > certain state, and it gets a version, then it should not change..imho > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Feb. 19, 2019

Re: [Pharo-users] OSProcess / OSSubprocess / LibC uniqueInstance

by Serge Stinckwich

Thank you Thierry. On Tue, Feb 19, 2019 at 12:48 PM Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Hi Serge, Albrecht, > > loading OSProcess directly with the following expression works: > > Metacello new > configuration: 'OSProcess'; > repository: 'http://www.squeaksource.com/MetacelloRepository'; > load > > There is still some work to be done on OSProcess adaptation to Pharo > 7, but they are in rarely used parts. > > Regards, > > Thierry > > Le mar. 19 fÃ©vr. 2019 Ã 12:19, Albrecht Baur via Pharo-users > <pharo-users(a)lists.pharo.org> a Ã©crit : > > > > I need to execute OS commands from within a x64 pharo 7.01 image on > centos7 (for example: 'zip -r 123.zip zipme/'). > > > > I found these 3 tools: OSProcess, OSSubprocess, LibC uniqueInstance > > > > But I did not find any docu on which one to use for which use case. > > > > OSProcess is in the catalog browser but fails loading because of > ByteArray>>ifNotNilDo: > > -> So OSProcess is not to be used with p7 ? > > > > OSSubprocess loads via catalog browser and the following snippet works > (even though 64 bit): > > > > OSSUnixSubprocess new > > command: 'zip'; > > arguments: #('-r' '123.zip' 'zipme'); > > redirectStdout; > > runAndWaitOnExitDo: [ :process :outString | > > outString inspect > > ] > > > > So is it ok to use OSSubprocess with 64 bit even though documented as 32 > bit only ? (here: > https://github.com/pharo-contributions/OSSubprocess#installation) > > > > LibC uniqueInstance system: 'zip -r 123.zip zipme/' > > ... works, but I don't know if its the right tool for this. > > > > Is there somewhere more info on which tool to use for which use case ? > > > > Thanks in advance! > > > > Albrecht > > > > PS.: I need to use zip as os process only because of this issue: > https://github.com/pharo-project/pharo/issues/2584 > > -- Serge Stinckwic âhâ Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) âSorbonne University (SU) French National Research Institute for Sustainable Development (IRD)â U âniversity of YaoundÃ© Iâ, Cameroun "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich â

Feb. 19, 2019

Re: [Pharo-users] How to load a single package in a Metacello baseline

by Tim Mackinnon

Yeah - I have a similar issue with ExternalWebBrowser, which I load as: spec baseline: 'ExternalWebBrowser' with: [ spec repository: 'github://seandenigris/Pharo-Web-Browser:master/repository' ]; import: 'ExternalWebBrowser'. That drags in BabyMock and huge raft of tests (which Iâm grateful were written), but Iâd prefer not to muddy the waters when presenting Exercism. I think what we have to do is submit pull requests to these projects such that they create better baselines with Groups. Eg. The Exercism baseline does this so that students load core, but developers get extra tools to generate exercises - eg. spec package: 'Exercism' with: [ ]; package: 'ExercismDev' with: [ spec requires: #('Exercism' 'ExercismTools')]; package: 'ExercismTools' with: [ spec requires: #('OSProcess' 'ExternalWebBrowser') ]; group: 'default' with: #('ExercismTools'); group: 'dev' with: #('ExercismDevâ)] Then you can specify in your load request which group to use (I donât have the syntax handy for baselines, but when you load via iceberg, the Metacelle menu has a second option where you specify the group to use, so Iâm sure it can be done in code too). Iâd be interested if there is some way to do it without groups though, so that you donât have to rely on the package authors to do this (similar in thought to what Sabine is complaining about by not being able to better control version dependencies). This whole area is becoming more and more important as we grow up and what to have more controllable load characteristics. Tim > On 19 Feb 2019, at 11:13, N. Bouraqadi <bouraqadi(a)gmail.com> wrote: > > Hi, > > I'm updating the the baseline of PharoJS to use the zinc websockets from the github repo https://github.com/svenvc/zinc <https://github.com/svenvc/zinc>. I want to load package Zinc-WebSocket-Core. So, in BaselineOfPharoJS>>#baseline: I've defined > spec baseline: 'ZincHTTPComponents' with: [ > spec > loads: #('Zinc-WebSocket-Core'); > repository: 'github://svenvc/zinc <github://svenvc/zinc>' ]. > > However, for some reason I get Zinc-WebSocket-Tests loaded. Any hint how to avoid it?(edited) > Looking at BaselineOfZincHTTPComponents>>#baseline:, package WebSocket-Core does not seem to depend on tests > spec package: 'Zinc-WebSocket-Core' with: [ spec requires: 'Zinc-HTTP' ] > > Thanks, > Noury

Feb. 19, 2019

Re: [Pharo-users] OSProcess / OSSubprocess / LibC uniqueInstance

by Thierry Goubier

Hi Serge, Albrecht, loading OSProcess directly with the following expression works: Metacello new configuration: 'OSProcess'; repository: 'http://www.squeaksource.com/MetacelloRepository'; load There is still some work to be done on OSProcess adaptation to Pharo 7, but they are in rarely used parts. Regards, Thierry Le mar. 19 fÃ©vr. 2019 Ã 12:19, Albrecht Baur via Pharo-users <pharo-users(a)lists.pharo.org> a Ã©crit : > > I need to execute OS commands from within a x64 pharo 7.01 image on centos7 (for example: 'zip -r 123.zip zipme/'). > > I found these 3 tools: OSProcess, OSSubprocess, LibC uniqueInstance > > But I did not find any docu on which one to use for which use case. > > OSProcess is in the catalog browser but fails loading because of ByteArray>>ifNotNilDo: > -> So OSProcess is not to be used with p7 ? > > OSSubprocess loads via catalog browser and the following snippet works (even though 64 bit): > > OSSUnixSubprocess new > command: 'zip'; > arguments: #('-r' '123.zip' 'zipme'); > redirectStdout; > runAndWaitOnExitDo: [ :process :outString | > outString inspect > ] > > So is it ok to use OSSubprocess with 64 bit even though documented as 32 bit only ? (here: https://github.com/pharo-contributions/OSSubprocess#installation) > > LibC uniqueInstance system: 'zip -r 123.zip zipme/' > ... works, but I don't know if its the right tool for this. > > Is there somewhere more info on which tool to use for which use case ? > > Thanks in advance! > > Albrecht > > PS.: I need to use zip as os process only because of this issue: https://github.com/pharo-project/pharo/issues/2584

Feb. 19, 2019

Re: [Pharo-users] Pier3 & content management

by Esteban Lorenzano

Hello, Not many people are using it, but it should be not much problem make it run in Pharo 7 (and with current version of Seaside). Esteban > On 19 Feb 2019, at 12:03, Albrecht Baur via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Albrecht Baur <baur.albrecht(a)googlemail.com> > Subject: Pier3 & content management > Date: 19 February 2019 at 12:03:27 CET > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > Hey, > > what is the status of Pier3 + Pier3AddOns ? > > -> Seems to me that it is discontinued since Pharo 5, right ? > > I'm asking because I look around to see if there is a project usable as a starting point of a small web content management module for seaside (nothing too complicated / fancy). > > Is there something besides Pier that goes into this direction ? > > Thanks for hints, > Albrecht > >

Feb. 19, 2019

How to load a single package in a Metacello baseline

by N. Bouraqadi

Hi, I'm updating the the baseline of PharoJS to use the zinc websockets from the github repo https://github.com/svenvc/zinc. I want to load package Zinc-WebSocket-Core. So, in BaselineOfPharoJS>>#baseline: I've defined spec baseline: 'ZincHTTPComponents' with: [ spec loads: #('Zinc-WebSocket-Core'); repository: 'github://svenvc/zinc' ]. However, for some reason I get Zinc-WebSocket-Tests loaded. Any hint how to avoid it?(edited) Looking at BaselineOfZincHTTPComponents>>#baseline:, package WebSocket-Core does not seem to depend on tests spec package: 'Zinc-WebSocket-Core' with: [ spec requires: 'Zinc-HTTP' ] Thanks, Noury

Feb. 19, 2019

Re: [Pharo-users] OSProcess / OSSubprocess / LibC uniqueInstance

by Albrecht Baur

I just tried the easy way via catalog browser. I think it is OSProcess 4.6.9 from http://www.squeaksource.com/OSProcess On 19.02.19 12:01, Serge Stinckwich wrote: > > > On Tue, Feb 19, 2019 at 11:56 AM David T. Lewis <lewis(a)mail.msen.com > <mailto:lewis@mail.msen.com>> wrote: > > On Tue, Feb 19, 2019 at 11:37:38AM +0100, Albrecht Baur via > Pharo-users wrote: > > From: Albrecht Baur <baur.albrecht(a)googlemail.com > <mailto:baur.albrecht@googlemail.com>> > > Subject: OSProcess / OSSubprocess / LibC uniqueInstance > > To: pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> > > Date: Tue, 19 Feb 2019 11:37:38 +0100 > > > > I need to execute OS commands from within a x64 pharo 7.01 image on > > centos7 (for example: 'zip -r 123.zip zipme/'). > > > > I found these 3 tools: OSProcess, OSSubprocess, LibC uniqueInstance > > > > But I did not find any docu on which one to use for which use case. > > > >Â * OSProcess is in the catalog browser but fails loading because of > >Â Â ByteArray>>ifNotNilDo: > >Â Â -> So OSProcess is not to be used with p7 ? > > Hi Albrecht, > > I am sorry that I cannot check it right now, but it may be that > ConfigurationOfOSProcess needs to be updated. The #ifNotNilDo: problem > was fixed by Thierry Goubier in July 2017, so perhaps you are using > an out of date version. > > Hopefully someone else can give you a better answer, otherwise I will > try to follow up in a day or two. > > > I have the same problem of ifNotNilDo: when I load OSProcess in Pharo 7. > What version do you use ? > Regards, > > -- > Serge Stinckwic > h > > Int. Research Unit > Â on Modelling/Simulation of Complex Systems (UMMISCO) > Sorbonne University > Â (SU) > French National Research Institute for Sustainable Development (IRD) > U > niversity of YaoundÃ© I, Cameroun > "Programs must be written for people to read, and only incidentally > for machines to execute." > https://twitter.com/SergeStinckwich >

Feb. 19, 2019

Pier3 & content management

by Albrecht Baur

Hey, what is the status of Pier3 + Pier3AddOns ? -> Seems to me that it is discontinued since Pharo 5, right ? I'm asking because I look around to see if there is a project usable as a starting point of a small web content management module for seaside (nothing too complicated / fancy). Is there something besides Pier that goes into this direction ? Thanks for hints, Albrecht

Feb. 19, 2019

Re: [Pharo-users] OSProcess / OSSubprocess / LibC uniqueInstance

by Serge Stinckwich

On Tue, Feb 19, 2019 at 11:56 AM David T. Lewis <lewis(a)mail.msen.com> wrote: > On Tue, Feb 19, 2019 at 11:37:38AM +0100, Albrecht Baur via Pharo-users > wrote: > > From: Albrecht Baur <baur.albrecht(a)googlemail.com> > > Subject: OSProcess / OSSubprocess / LibC uniqueInstance > > To: pharo-users(a)lists.pharo.org > > Date: Tue, 19 Feb 2019 11:37:38 +0100 > > > > I need to execute OS commands from within a x64 pharo 7.01 image on > > centos7 (for example: 'zip -r 123.zip zipme/'). > > > > I found these 3 tools: OSProcess, OSSubprocess, LibC uniqueInstance > > > > But I did not find any docu on which one to use for which use case. > > > > * OSProcess is in the catalog browser but fails loading because of > > ByteArray>>ifNotNilDo: > > -> So OSProcess is not to be used with p7 ? > > Hi Albrecht, > > I am sorry that I cannot check it right now, but it may be that > ConfigurationOfOSProcess needs to be updated. The #ifNotNilDo: problem > was fixed by Thierry Goubier in July 2017, so perhaps you are using > an out of date version. > > Hopefully someone else can give you a better answer, otherwise I will > try to follow up in a day or two. > > I have the same problem of ifNotNilDo: when I load OSProcess in Pharo 7. What version do you use ? Regards, -- Serge Stinckwic h Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) Sorbonne University (SU) French National Research Institute for Sustainable Development (IRD) U niversity of YaoundÃ© I, Cameroun "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich

Feb. 19, 2019

Re: [Pharo-users] OSProcess / OSSubprocess / LibC uniqueInstance

by David T. Lewis

On Tue, Feb 19, 2019 at 11:37:38AM +0100, Albrecht Baur via Pharo-users wrote: > From: Albrecht Baur <baur.albrecht(a)googlemail.com> > Subject: OSProcess / OSSubprocess / LibC uniqueInstance > To: pharo-users(a)lists.pharo.org > Date: Tue, 19 Feb 2019 11:37:38 +0100 > > I need to execute OS commands from within a x64 pharo 7.01 image on > centos7 (for example: 'zip -r 123.zip zipme/'). > > I found these 3 tools: OSProcess, OSSubprocess, LibC uniqueInstance > > But I did not find any docu on which one to use for which use case. > > * OSProcess is in the catalog browser but fails loading because of > ByteArray>>ifNotNilDo: > -> So OSProcess is not to be used with p7 ? Hi Albrecht, I am sorry that I cannot check it right now, but it may be that ConfigurationOfOSProcess needs to be updated. The #ifNotNilDo: problem was fixed by Thierry Goubier in July 2017, so perhaps you are using an out of date version. Hopefully someone else can give you a better answer, otherwise I will try to follow up in a day or two. Dave > > * OSSubprocess loads via catalog browser and the following snippet > works (even though 64 bit): > > OSSUnixSubprocess new > ?????? command: 'zip'; > ?????? arguments: #('-r' '123.zip' 'zipme'); > ?????? redirectStdout; > ?????? runAndWaitOnExitDo: [ :process :outString?? | > ?????? ?????? outString inspect > ?????? ] > > So is it ok to use OSSubprocess with 64 bit even though documented as 32 > bit only ? (here: > https://github.com/pharo-contributions/OSSubprocess#installation) > > * LibC uniqueInstance system: 'zip -r 123.zip zipme/' > ... works, but I don't know if its the right tool for this. > > Is there somewhere more info on which tool to use for which use case ? > > Thanks in advance! > > Albrecht > > PS.: I need to use zip as os process only because of this issue: > https://github.com/pharo-project/pharo/issues/2584 >

Feb. 19, 2019

OSProcess / OSSubprocess / LibC uniqueInstance

by Albrecht Baur

I need to execute OS commands from within a x64 pharo 7.01 image on centos7 (for example: 'zip -r 123.zip zipme/'). I found these 3 tools: OSProcess, OSSubprocess, LibC uniqueInstance But I did not find any docu on which one to use for which use case. * OSProcess is in the catalog browser but fails loading because of ByteArray>>ifNotNilDo: -> So OSProcess is not to be used with p7 ? * OSSubprocess loads via catalog browser and the following snippet works (even though 64 bit): OSSUnixSubprocess new Â Â Â command: 'zip'; Â Â Â arguments: #('-r' '123.zip' 'zipme'); Â Â Â redirectStdout; Â Â Â runAndWaitOnExitDo: [ :process :outStringÂ | Â Â Â Â Â Â outString inspect Â Â Â ] So is it ok to use OSSubprocess with 64 bit even though documented as 32 bit only ? (here: https://github.com/pharo-contributions/OSSubprocess#installation) * LibC uniqueInstance system: 'zip -r 123.zip zipme/' ... works, but I don't know if its the right tool for this. Is there somewhere more info on which tool to use for which use case ? Thanks in advance! Albrecht PS.: I need to use zip as os process only because of this issue: https://github.com/pharo-project/pharo/issues/2584

Feb. 19, 2019

Re: [Pharo-users] [Pharo-dev] About Iceberg

by Damien Pollet

ð On Tue, 19 Feb 2019 at 10:06, Hilaire <hilaire(a)drgeo.eu> wrote: > I join your thank you note, although I only use one half, the tonel > part, it is pleasant to be able to commit to file base repository and > use related tools. > > Le 19/02/2019 Ã 09:50, Sven Van Caekenberghe a Ã©crit : > > This is a thank you note about Iceberg. > > -- > Dr. Geo > http://drgeo.eu > > > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Feb. 19, 2019

About Iceberg

by Sven Van Caekenberghe

Hi, This is a thank you note about Iceberg. I have been moving all my external and internal Pharo code to git/tonel/7 and on multiple occasions I have been pleasantly surprised about the functionality and performance of Iceberg. Basically, it just works. Finally, Pharo code lives in standard open source and commercial repositories (git, GitHub, Bitbucket, ...), without losing anything. I know that it took years to get here and that lots of code and community battles had to be fought. So thank you, to the whole team, you did a great job ! Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

Feb. 19, 2019

Re: [Pharo-users] im using pharo 7 with linux env. but cannot input korean.

by Hilaire

Hi Pierce, Yes, this option worked to key in Chinese. By the way, do you know if any option is needed on Windows? I checked for the options but I did not see anything relevant: hilaire@PCHome:~/Travaux/Developpement/DrGeoII/trunk/build/bundles/windows/DrGeo$ wine Contents/vm/DrGeo.exe --help Usage: Pharo Virtual Machine [vmOptions] imageFile [imageOptions] vmOptions: -service: ServiceName (install VM as NT service) -headless (force VM to run headless) -timephases (print start load and run times) -log: LogFile (use LogFile for VM messages) -memory: megaByte (set memory to megaByte MB) -breaksel: string (call warning on send of sel for debug) -breakmnu: string (call warning on MNU of sel for debug) -leakcheck: n (leak check on GC (1=full,2=incr,3=both)) -eden: bytes (set eden memory size to bytes) -stackpages: n (use n stack pages) -numextsems: n (allow up to n external semaphores) -checkpluginwrites (check for writes past end of object in plugins -noheartbeat (no heartbeat for debug) -trace[=num] enable tracing (optionally to a specific value) -warnpid (print pid in warnings) -[no]failonffiexception ([never]always catch exceptions in FFI calls) -codesize: bytes (set machine-code memory size to bytes) -cogmaxlits: n (set max number of literals for methods to be compiled to machine code) -cogminjumps: n (set min number of backward jumps for interpreted methods to be considered for compilation to machine code) -tracestores (assert-check stores for debug) -reportheadroom (report unused stack headroom on exit) -dpcso: bytes (stack offset for prim calls for debug) -maxoldspace: bytes (set max size of old space memory to bytes) -logscavenge (log scavenging to scavenge.log) Options begin with single -, but -- prefix is silently accepted Options with arguments -opt:n are also accepted with separators -opt n Le 16/02/2019 Ã 04:54, Pierce Ng a Ã©critÂ : > I start Pharo with -compositioninput (one dash, didn't try two dashes -- Dr. Geo http://drgeo.eu

Feb. 19, 2019

Re: [Pharo-users] Pharo 7: Problems with the new file chooser UI

by Offray Vladimir Luna CÃ¡rdenas

Hi Sven, Yes I was sure. But that's because I was using Pharo-7.0.0+rc1.build.19.sha.1fcbcd5170ad that was the one loaded from Pharo launcher 1.6.x from 31.01.2019. Now I have updated Pharo Launcher to 1.7.2 and it makes available the 7.0.1 versions of Pharo and now that functionality is working well... I just deal with other dependencies and changes... But Grafoscopio is taking better form now. Cheers, Offray On 18/2/19 17:13, Sven Van Caekenberghe wrote: > Are you really sure ? It works for me, Pharo 7.0.1 macOS. > >> On 18 Feb 2019, at 22:57, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >> >> Hi, >> >> While I'm migrating Grafoscopio to Pharo 7 I get a deprecation warning telling me that I need to change the previous code for choosing a file from the UI, but now when I proceed as advised (using chooseExistingFileReference: title extensions: exts path: path). It returns a FileReference but all the paths are referred to the place where the running image is located, instead of the place where the selected file is located. >> >> For example if you run: >> >> [1]~~~~ >> >> (FileLocator documents / 'test.ston') ensureCreateFile writeStreamDo: [:stream | STON put: (Rectangle center: 10@10 extent: 100@50) onStream: stream ]. >> >> ~~~~ >> >> You will get a file on your Documents folder called test.ston, but If I choose that file using: >> >> [2]~~~~ >> >> file := UIManager default >> chooseExistingFileReference:'Choose a file' >> extensions: #('ston') >> path: FileLocator documents. >> >> ~~~~ >> >> and I choose the "test.ston" file created at [1], Pharo tells me that the file is located in the same place as the running image, instead on my Documents folder. >> >> Am I missing something? >> >> Thanks, >> >> Offray >> > >

Feb. 19, 2019

Re: [Pharo-users] Partition/Sync ready databases for Pharo?

by Pierce Ng

On Mon, Feb 18, 2019 at 02:56:10PM -0300, Esteban Maringolo wrote: > I have the requirement that an app that I'm prospecting must be able > to work offline and synchronize changes once the connection is > restored. > > I want to avoid having to write "sync" logic manually. I've not done this for real before, but here are some possibilities: - https://github.com/sqlite-sync/SQLite-sync.com - http://www.symmetricds.org/ - https://github.com/CanonicalLtd/dqlite - Use Fossil as your database

Feb. 19, 2019

Re: [Pharo-users] Running pharo in daemon mode

by Pierce Ng

On Mon, Feb 18, 2019 at 04:39:03PM -0500, sergio ruiz wrote: > I found my issue.. I need to be running in daemon mode.. i was running with > &, but as soon as my connection lets go, the app dies.. My daemontools run file: #!/bin/sh /usr/bin/setuidgid app1 \ /pkg/vm/pharo -vm-display-null -vm-sound-null app1.image --no-quit My Dockerfile CMD /pkg/vm/pharo -vm-display-null -vm-sound-null app.image --no-quit st runApp.st You could also try '-headless' instead of '-vm-display-null'. Pierce

Feb. 19, 2019

Re: [Pharo-users] Iceberg working with forks - can it be easier?

by Tim Mackinnon

Hi Guille - thanks for taking the time to write this upâ¦ in the middle there I finally spotted the crucial bit âclone the original, push to your forkâ. I think thats what Iâve been doing wrong - and it leads to all kinds of confusion (at least Iâm hoping this is what it is). As I have cloned from my Fork (and in my defence - its because we were given a repository that collides with the pharo one - exercism/pharo - and P7 doesnât let us clone from that) - so Iâve had to clone from my fork. It all seemed to work until I started submitting my PRâs and then they seem to include commits going much further back than I think they should need Even wen I thought I was being careful and syncing to master - it still seems to go back to some of my earliest work. Now that we have managed to get the repo renamed - I will try working like you have suggested and make sure that it is working like you describe - as it shouldnât be as complicated as this to make clean isolated changes and then submit them as a PR. (otherwise Pharo would fall apart). One question I do have however - is what is the best procedure if you realised when making changes that A) you forgot to make changes in a branch (so are working on master) B) you are working in a branch but decide some of your changes should go in another branch itself based on master (how to stash?) These are 2 common scenarios Iâve found when trying to be a good citizen for my little project. Do I have to go to the terminal to do this stuff - or can I cleanly do these kinds of operations in Pharo (which I think you should be able to do, as its so easy to get into either of those states). Thanks in advance. Tim > On 18 Feb 2019, at 08:56, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi! > > On Fri, Feb 15, 2019 at 7:06 PM Tim Mackinnon <tim(a)testit.works> wrote: > Hi guys - Iâve spent a few hours scratching my head trying to understand why some of my Pull Requests to a project I had forked kept showing my previous commits when I thought I was all caught up. > > It suddenly dawned on me, that when I had forked, and then done some work and then submitted a PR, and then applied it upstream that my fork is now no longer in sync with its upstream counterpart. > > Having not done this in ages, it took me a while to then realise I have to do some git stuff to get it back in sync e.g. (and I think Iâve got this right) > > git fetch upstream (or whatever name you gave it) > Git checkout master > Git merge upstream/master > > When you did your clone, did you clone the original repository or your fork's? > One way to simplify this workflow is: > - you clone always the original repository > - you create a branch and work there > - then you'll push your branch to your fork + fork > > That way your branch will be always up to date with the original repository, and no need to sync (actually the sync is done automatically when you push to your fork). > > Of course this assumes you're doing a new clone every time you work :). > > > So I guess my question is - wouldnât it be helpful if this was a command in Iceberg? > > It would, there are several places where we could simplify the workflow for common cases, I agree. > > It seems quite common to fork a project (I think this is still recommended for pharo itself isnât it?) > > I'd say its mandatory :). Otherwise you will not be able to push directly to it because of permission problems (actually all main dev branches are now blocked so **nobody**, not even admins, push to them directly). > > - and then at some point you need to catchup with that origin again? Or am I missing something? > > Well, it really depends on the workflow you use. Above I've explained a workflow that works when you clone every time. > Git is so complex and so low level that you can do lots of different things with it. > > First thing is to understand what "catch up with origin" means. In my head it only means: > - checkout your "to-catchup" branch > - merge the remote "to-catchup" branch and merge it > > All the rest is workflow dependent. Even (!!) I would argue that merging is not, strictly speaking, a correct way to catch up: If you have made changes into "to-catchup", then merging will not make both branches the same, but your "to-catchup" branch may have extra commits that you did not want to introduce... > > And here I'm not saying you should not merge, actually I do it most of the times because I know that 90% of the times it will be ok, and I do rollback when I realize I was in the other 10%... > > I guess lots of stuff can go wrong - but if it does - youâd still get the same problems on the command line. > > Yes, and no. The "lots of stuff can go wrong" can be translated in most of the cases to "I had a merge conflict". But this is not git, this is git+pharo. > > The thing is that with Git, your code is dead in files. With Iceberg, your code is in the files but it also may be alive in your image too. So updating code for what you have existing instances, or announcement subscriptions or other could (and probably will) mess up with the running code... > So to the typical merge conflict, you may add breaking your running system. > > It just seems that for normal situations - it would be handy to run this straight in Pharo. > > Thoughts from the git experts? > > For these cases, you can do exactly as the command line from Iceberg's UI > > - change your branch to your "to-catchup" master > - fetch > - now you can go to the merge option, and choose to merge your remote branch into your checked-out branch. > - and push > > Of course, this simple workflow works most of the times, but you may find edge cases. > For those edge cases (typically updating iceberg itself, or trying to update pharo itself), in the checkout preview you will have the combo with the checkout strategy: choose the expert mode "do not load the code". This option will change the branch on git's world, but it will not load the code in your image. > > That is useful if you have living instances for example. > This option will though make a diff between the checked out version and your image code and show you differences. (think this as a git reset --soft) > > To me the fact that we are manipulating live code loaded in the image and not dead files makes a huge difference, and this makes that extrapolating git commands to iceberg is not so straight forward :). Also, understanding that git is stateful/context dependant, and applying an operation means changing your current state (modify your current branch, change your current branch) is useful to see the consequences. > > In any case, any more concrete suggestions for enhancing this workflow are welcome. I think that neither Esteban, Pablo, me nor other contributors are skilled UI designers, and thinking about the best way to present a usecase to a user is super super hard :). > > Guille, from his vacations >

Feb. 19, 2019

Re: [Pharo-users] Should epicea help me recover changes in a system crash?

by Tim Mackinnon

Ok - if its supposed to work in this situation, I will zip up that image and put it somewhere to try and figure out what happened. > On 18 Feb 2019, at 17:54, ducasse <stepharo(a)netcourrier.com> wrote: > > Hi tim > > this is strange. Normally epicea logs all the changes. In the past I got missing classes. > Epicea is git ignorant. So I do not see how it could interact. > I would love to see your bug solved. Could you keep your image and may be martin > has some time to have a look (he got flying back to chile). > > Stef > >> On 18 Feb 2019, at 18:13, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi - Iâve got mixed experiences with epicea - having had a few image seg faults recently its presented some of my changes and let me recover them. >> >> However just now, I had been working for an hour and my whole laptop went black (and then had the apple logo). I took the opportunity to apply the latest HighSierra updates (it has been a while) - but when I relaunched my image - epicea detected missing code however what it shows me is nothing like the changes I had recently made - it just showed me a merge change? >> >> Is it possible that if Iâm on the wrong branch - it wonât show me changes I made recently? >> >> I find Iâm kind of missing the old changes text file (which we say we are getting rid of) as at least it let me see an historic account of what I had done - as now things are a bit all of over the place (do-its you have to find in the playground history) and epicea is supposed to show the rest - execpt it doesnât appear to do so? >> >> Tim > > >

Feb. 19, 2019

Re: [Pharo-users] Pharo 7: Problems with the new file chooser UI

by Sven Van Caekenberghe

Are you really sure ? It works for me, Pharo 7.0.1 macOS. > On 18 Feb 2019, at 22:57, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi, > > While I'm migrating Grafoscopio to Pharo 7 I get a deprecation warning telling me that I need to change the previous code for choosing a file from the UI, but now when I proceed as advised (using chooseExistingFileReference: title extensions: exts path: path). It returns a FileReference but all the paths are referred to the place where the running image is located, instead of the place where the selected file is located. > > For example if you run: > > [1]~~~~ > > (FileLocator documents / 'test.ston') ensureCreateFile writeStreamDo: [:stream | STON put: (Rectangle center: 10@10 extent: 100@50) onStream: stream ]. > > ~~~~ > > You will get a file on your Documents folder called test.ston, but If I choose that file using: > > [2]~~~~ > > file := UIManager default > chooseExistingFileReference:'Choose a file' > extensions: #('ston') > path: FileLocator documents. > > ~~~~ > > and I choose the "test.ston" file created at [1], Pharo tells me that the file is located in the same place as the running image, instead on my Documents folder. > > Am I missing something? > > Thanks, > > Offray >

Feb. 18, 2019

Re: [Pharo-users] Running pharo in daemon mode

by Sven Van Caekenberghe

There are many options. Did you read https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… ? You can also study this https://github.com/svenvc/pharo-server-tools nohup is an easy to use, quick and dirty solution. > On 18 Feb 2019, at 22:39, sergio ruiz <sergio.rrd(a)gmail.com> wrote: > > Hey, all.. > > I found my issue.. I need to be running in daemon mode.. i was running with &, but as soon as my connection lets go, the app dies.. > > I tried using daemon tools, but it looks like the site stays up for one second, and a new PID is generated.. > > Anyone have any hints on how people are doing this lately? > > Thanks! > > > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.codeandmusic.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101

Feb. 18, 2019

Pharo 7: Problems with the new file chooser UI

by Offray Vladimir Luna CÃ¡rdenas

Hi, While I'm migrating Grafoscopio to Pharo 7 I get a deprecation warning telling me that I need to change the previous code for choosing a file from the UI, but now when I proceed as advised (using |chooseExistingFileReference: title extensions: exts path: path|). It returns a |FileReference| but all the paths are referred to the place where the running image is located, instead of the place where the selected file is located. For example if you run: [1]~~~~ (FileLocator documents / 'test.ston') ensureCreateFileÂ writeStreamDo:Â [:stream | STON put: (Rectangle center: 10@10 extent: 100@50) onStream: stream ]. ~~~~ You will get a file on your Documents folder called test.ston, but If I choose that file using: [2]~~~~ file := UIManager default Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â chooseExistingFileReference:'Choose a file' Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â extensions: #('ston') Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â path: FileLocator documents. ~~~~ and I choose the "test.ston" file created at [1], Pharo tells me that the file is located in the same place as the running image, instead on my Documents folder. Am I missing something? Thanks, Offray

Feb. 18, 2019

Running pharo in daemon mode

by sergio ruiz

Hey, all.. I found my issue.. I need to be running in daemon mode.. i was running with &, but as soon as my connection lets go, the app dies.. I tried using daemon tools, but it looks like the site stays up for one second, and a new PID is generated.. Anyone have any hints on how people are doing this lately? Thanks! ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 18, 2019

Re: [Pharo-users] Measuring memory usage

by Sven Van Caekenberghe

> On 18 Feb 2019, at 21:42, sergio ruiz <sergio.rrd(a)gmail.com> wrote: > > Snap! i forgot about that! > > I really need to get that put behind a password Yes, and especially disable the dev tools as they contain doit functionality ! > On February 18, 2019 at 1:56:23 PM, Sven Van Caekenberghe (sven(a)stfx.eu) wrote: > >> Do you know about Seaside's Status page/dev tool. >> >> It is there by default, it has many tabs that give you more information about the running image, including memory info, as well as a space tally (but that is very slow). > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.codeandmusic.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101

Feb. 18, 2019

Re: [Pharo-users] Measuring memory usage

by sergio ruiz

Snap! i forgot about that! I really need to get that put behind a password On February 18, 2019 at 1:56:23 PM, Sven Van Caekenberghe (sven(a)stfx.eu) wrote: Do you know about Seaside's Status page/dev tool. It is there by default, it has many tabs that give you more information about the running image, including memory info, as well as a space tally (but that is very slow). ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 18, 2019

Re: [Pharo-users] Calypso documentation? Or understanding menu building

by Denis Kudriashov

Hi Tim. Ð¿Ð½, 18 ÑÐµÐ²Ñ. 2019 Ð³. Ð² 14:48, Tim Mackinnon <tim(a)testit.works>: > Hi Dennis - Iâve been reading the book you mentioned and looking through > the code as well as your examples and I feel a bit more comfortable with > whatâs going on - however I am stumped about how you do an OR context (vs. > an AND context). > > I would like my menu item to appear for either a selected RPackage OR a > ClyTaggedClassGroup - I thought I had it with: > > RPackage asCalypsoItemContext, ClyTaggedClassGroup asCalypsoItemContext > (to get a composite context) but then I realised that the composite is an > AND. > > Is there some way to create an OR context, or do I simply have to create > multiple commands? > You simply need two annotations. One for context of RPackage and another for context of tag. > > Tim > > > On 12 Feb 2019, at 19:32, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi Tim > > Ð²Ñ, 12 ÑÐµÐ²Ñ. 2019 Ð³. Ð² 13:42, Tim Mackinnon <tim(a)testit.works>: > >> Is there any documentation on Calypso application contexts? I am trying >> to add a menu item to a package tag (the bit underneath a package - which I >> often call a sub-package). >> > > Only class comments are available for Calypso. Also there are a Commander > booklet > <https://github.com/SquareBracketAssociates/Booklet-Infrastructure>which > describes contexts and ClassAnnotation github readme > <https://github.com/pharo-ide/ClassAnnotation> (together with class > comments). > > >> >> Iâve specified: >> >> ^CmdContextMenuActivation >> byItemOf: ClyQueryMenuGroup for: RPackage >> asCalypsoItemContext >> >> > The #for: argument of command activations is a context where command > should be available. Context describes condition where given command (its > activation strategy) should be visible for users. > In your example "RPackage asCalypsoItemContext" is an instance of > ClyBrowserItemContext which matches any selected package in the browser > (when a kind of RPackage is selected). > And that's why you do not see it on selected tag because the tag is not a > package. > > But that puts my menu on the package and not the tag > > - and if I use the inspect extra menu in calypso, I get what looks to be >> something that could help me determine what I want but Iâm struggling to >> understand what ClyTaggedClassGroup does, and what a context is all about. >> > > Inspect command opens inspector of actually selected object which is an > instance of ClyTaggedClassGroup in that case (try inspect selected method > and you will get a CompiledMethod). > Children of package in browser are instances of ClyClassGroup and > subclasses. So they are not raw tags. If you need a command for a tag you > should add a command for ClyTaggedClassGroup items: > > ^CmdContextMenuActivation > byItemOf: ClyQueryMenuGroup for: ClyTaggedClassGroup > asCalypsoItemContext > > Look for example at SycPromotePackageFromTagCommand > class>>#fullBrowserMenuActivation which is defined this way. > > There are other kind of contexts which can be used in command annotations. > For example if you want a command for selected method only in full browser > then you should use ClyMethodContextOfFullBrowser: > > ^CmdContextMenuActivation byItemOf: ClyQueryMenuGroup for: > ClyMethodContextOfFullBrowser > > > it can be confusing that simple class is used in this case. But underhood > it is converted to the instance of context where command should be > available. > > >> >> Has anyone else played around with this at all? >> >> Ideally I want to have a menu appear on all the tags underneath a >> particular package - and possibly including that package (or maybe not - I >> havenât decided as I want to try it in the wild). >> >> While Iâm at it - I have quite understood how to create submenuâs either >> - as Iâd like to have several commands all as sub items of a menu item >> âExercismâ. >> > > Look at commander booklet. It includes example. > > >> >> Tim >> >> >> >> >

Feb. 18, 2019

Re: [Pharo-users] [PharoRemote] View remote Transcript

by Denis Kudriashov

Hi Serge. if it is related to TelePharo then you can register local transcript in remote image. Evaluate following code in playground: localTranscript := Transcript. remotePharo evaluate: [ Smalltalk globals at: #Transcript put: localTranscript ]. It will be not optimized solution because every message to transcript will send remote request to client. But it should work. Also all messages will go to main Transcript in you client image which is probably not desired. So the better solution requires real implementation of remote transcript. Ð¿Ð½, 18 ÑÐµÐ²Ñ. 2019 Ð³. Ð² 15:33, sergio ruiz <sergio.rrd(a)gmail.com>: > Hi, all.. > > Is it possible to use PharoRemote to watch the remote siteâs Transcript? > > Thanks! > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.codeandmusic.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101 >

Feb. 18, 2019

Re: [Pharo-users] Measuring memory usage

by Sven Van Caekenberghe

Do you know about Seaside's Status page/dev tool. It is there by default, it has many tabs that give you more information about the running image, including memory info, as well as a space tally (but that is very slow). > On 18 Feb 2019, at 19:16, sergio ruiz <sergio.rrd(a)gmail.com> wrote: > > Wondering if my image is dying due to memory usage. > > How would I go about getting a realistic measurement? > > Thanks! > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.codeandmusic.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101

Feb. 18, 2019

Measuring memory usage

by sergio ruiz

Wondering if my image is dying due to memory usage. How would I go about getting a realistic measurement? Thanks! ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 18, 2019

Partition/Sync ready databases for Pharo?

by Esteban Maringolo

I have the requirement that an app that I'm prospecting must be able to work offline and synchronize changes once the connection is restored. I want to avoid having to write "sync" logic manually. Is anybody using Pharo with a database that supports automatic synchronization (replicas?) like the one provided by Firebase (Realtime Sync or Firestore)? I rather use PostgreSQL/SQLite locally and sync with a "central" DB, because I'm familiar with SQL/RDBMS, but I'm open to options. Regards, Esteban A. Maringolo

Feb. 18, 2019

Re: [Pharo-users] Should epicea help me recover changes in a system crash?

by ducasse

Hi tim this is strange. Normally epicea logs all the changes. In the past I got missing classes. Epicea is git ignorant. So I do not see how it could interact. I would love to see your bug solved. Could you keep your image and may be martin has some time to have a look (he got flying back to chile). Stef > On 18 Feb 2019, at 18:13, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - Iâve got mixed experiences with epicea - having had a few image seg faults recently its presented some of my changes and let me recover them. > > However just now, I had been working for an hour and my whole laptop went black (and then had the apple logo). I took the opportunity to apply the latest HighSierra updates (it has been a while) - but when I relaunched my image - epicea detected missing code however what it shows me is nothing like the changes I had recently made - it just showed me a merge change? > > Is it possible that if Iâm on the wrong branch - it wonât show me changes I made recently? > > I find Iâm kind of missing the old changes text file (which we say we are getting rid of) as at least it let me see an historic account of what I had done - as now things are a bit all of over the place (do-its you have to find in the playground history) and epicea is supposed to show the rest - execpt it doesnât appear to do so? > > Tim

Feb. 18, 2019

Should epicea help me recover changes in a system crash?

by Tim Mackinnon

Hi - Iâve got mixed experiences with epicea - having had a few image seg faults recently its presented some of my changes and let me recover them. However just now, I had been working for an hour and my whole laptop went black (and then had the apple logo). I took the opportunity to apply the latest HighSierra updates (it has been a while) - but when I relaunched my image - epicea detected missing code however what it shows me is nothing like the changes I had recently made - it just showed me a merge change? Is it possible that if Iâm on the wrong branch - it wonât show me changes I made recently? I find Iâm kind of missing the old changes text file (which we say we are getting rid of) as at least it let me see an historic account of what I had done - as now things are a bit all of over the place (do-its you have to find in the playground history) and epicea is supposed to show the rest - execpt it doesnât appear to do so? Tim

Feb. 18, 2019

Pharo Image with Seaside dies without any clues

by sergio ruiz

Hi, all. My seaside image seems to run for an indeterminate amount of time here and there, then just stops running without writing to PharoDebug. How do I go about debugging the application crash? Is there another log somewhere? It looks like there are other (path) issues when the the image starts up, though.. the initial error log looks like: https://gist.github.com/sergio101/8ac04fe5db4786c36fa3bf795807da9a Iâm not sure these errors are related to the image just randomly crashing here and there. Thanks! ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 18, 2019

Re: [Pharo-users] Streams for FileReference in Pharo 7

by Sven Van Caekenberghe

OK, I that is what I expected. I will study this again and make a PR with better comments and tests. > On 18 Feb 2019, at 16:32, ducasse <stepharo(a)netcourrier.com> wrote: > >> >> >> I have been thinking a bit more about this, and I have a lot of problems with >> >> Integer>>#putOn: aStream >> aStream isBinary >> ifTrue: [ self asByteArray do: [ :each | aStream nextPut: each ] ] >> ifFalse: [ self asString putOn: aStream ] >> >> I think we should simply remove this method. It is ugly and wrong. > > I agree > >> #<< should simply be a shortcut for either #nextPut: and #nextPutAll: and nothing more. >> >> The following two are OK for me: >> >> String streamContents: [ :out | out << 'Hello' << $! ]. >> ByteArray streamContents: [ :out | out << #[ 1 2 3 ] << 4 ]. >> >> But the following most definitively not: >> >> (ByteArray streamContents: [ :out | out << 16rFF << 16rFF11 << 16rFFFF22 << 16rFFFFFF33 ]) hex. >> >> When you write out an integer, you have to decide its size, that can never depend on the magnitude (because there is no way to read this back unless there is additional bracketing). >> >> Also, printing to a stream should be (very) efficient. Making copies of objects just for conversion purposes should be avoided. > > yes. > >> >> I think that if we remove Integer>>#putOn: I could live with >> >> ZnEncodedStream>>#<< anObject >> anObject putOn: self > > Yes :) > and remove the ugly one? Yes > >> >> The other solution is to define #<< as strictly the same as #nextPutAll: and remove all #putOn: implementors. >> >> Sven

Feb. 18, 2019

Re: [Pharo-users] Aggregation framework in MongoTalk?

by JesÃºs MarÃ

Same question on 2019! are you planning to give support to aggregations in MongoTalk/voyage? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 18, 2019

How do you avoid loading master code which is indirectly referenced by a version in the baseline?

by Sabine Manaa

For test and deployment, I have to be sure that I know exactly which versions I load and I have to be sure to be able to load exactly the same code again. I do not speak from my projects but from the projects I use. I found myself asking people again and again to set tags in their projects and being surprised again and again by changed code even though I am trying to load versions (with versions I mean NOT #stable or #master but like v2.2.2). The reason for this problem I then have, is that often in baselines with version numbers (e.g. v2.2.2) other projects are referenced but as master. So in consequence, I load version but get master from another project which is referenced indirectly. For me, that this is not good at all. I was wondering that this seems not to be a problem for others. I found out that I can put a lock in my baselines preLoadDoIt for those indirectly referenced projects. Examlpe Artefact v1.0.1 https://github.com/pharo-contributions/Artefact/blob/v1.0.1/src/BaselineOfA… loads github://zweidenker/Units/src (which is master). I found a solution for this: In the preLoadDoIt of my baseline I lock Units to a certain commit. preLoadDoIt Metacello new baseline: 'Units'; repository: 'github://zweidenker/Units:98d5a3d/src'; lock. This solves my problem in this example. Disadvantage is that I have to analyze everything which is loaded from the projects I use and create a lock for it. Questions: 1.) Wouldn't it make sense to have some mechanism, perhaps in Rowan then, where I can say that a project which has a number can only reference other projects with numbers? This would avoid the whole problem 2.) How do others solve this problem? addendum: I do not speak about project versions which are in development, here #stable or master are great features. But sometime when a project has a certain state, and it gets a version, then it should not change..imho -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 18, 2019

[PharoRemote] View remote Transcript

by sergio ruiz

Hi, all.. Is it possible to use PharoRemote to watch the remote siteâs Transcript? Thanks! ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 18, 2019

Re: [Pharo-users] Streams for FileReference in Pharo 7

by ducasse

> > I have been thinking a bit more about this, and I have a lot of problems with > > Integer>>#putOn: aStream > aStream isBinary > ifTrue: [ self asByteArray do: [ :each | aStream nextPut: each ] ] > ifFalse: [ self asString putOn: aStream ] > > I think we should simply remove this method. It is ugly and wrong. I agree > #<< should simply be a shortcut for either #nextPut: and #nextPutAll: and nothing more. > > The following two are OK for me: > > String streamContents: [ :out | out << 'Hello' << $! ]. > ByteArray streamContents: [ :out | out << #[ 1 2 3 ] << 4 ]. > > But the following most definitively not: > > (ByteArray streamContents: [ :out | out << 16rFF << 16rFF11 << 16rFFFF22 << 16rFFFFFF33 ]) hex. > > When you write out an integer, you have to decide its size, that can never depend on the magnitude (because there is no way to read this back unless there is additional bracketing). > > Also, printing to a stream should be (very) efficient. Making copies of objects just for conversion purposes should be avoided. yes. > > I think that if we remove Integer>>#putOn: I could live with > > ZnEncodedStream>>#<< anObject > anObject putOn: self Yes :) and remove the ugly one? Yes > > The other solution is to define #<< as strictly the same as #nextPutAll: and remove all #putOn: implementors. > > Sven > >

Feb. 18, 2019

Re: [Pharo-users] Streams for FileReference in Pharo 7

by ducasse

Hi sven what I do not really with asString is that it potentially created another stream. with << the implementation of camillo (if I remember correctly) manages correctly both single object and collection and it is nice to have. I do not know if his implementation does not create additional stream. Stef > On 15 Feb 2019, at 10:25, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Jan, > > I like #<< too, but I think your assumption that it can print anything on a stream is generally wrong, dangerous and unreliable. > > IMHO, you better stick to #print: in that case. > > Consider the follow, that all fail: > > String streamContents: [ :s | s << 'hello' << 42.5 << $! ]. > > String streamContents: [ :s | s << 'hello' << (1@2) << $! ]. > > In other words: #<< works in bizar ways (check the implementors of #putOn:). > > I would be inclined to change > > ZnEncodedStream>>#<< collection > ^ self nextPutAll: collection > > to > > ZnEncodedStream>>#<< collection > ^ self nextPutAll: collection asString > > but it would technically not be the same as the original #<< for in-memory streams. > > Opinions ? > > Sven > >> On 15 Feb 2019, at 09:52, Jan BlizniÄenko <jan.bliznicenko(a)fit.cvut.cz> wrote: >> >> Hello everyone >> >> I am trying to use Pharo 7 for my project and I noticed that most of my >> streams related code does not work anymore. Reason is that API for streams >> received from writeStream of FileReference changed and I think it changed >> for the worse in my case, because << does not properly handle any other >> objects than strings anymore. >> >> In both Pharo 6 and 7 I can write >> String streamContents: [ :s | s << 'hello' << 42 << $! ]. >> and get 'hello42!'. >> I can write in Pharo 6 but cannot in Pharo 7 >> 'hello.txt' asFileReference writeStreamDo: [ :s | s << 'hello' << 42 << $! ] >> In Pharo 6, I get same result in both examples (written to the file in >> second case of course), but in Pharo 7, the second example results in >> exception because << does not work with anything other than strings, so it >> seems I have to manually convert everything to strings. >> >> This change to streams seems to me like a setback for 2 reasons: >> 1) API amongst streams is no longer consistent in this case >> 2) streams for files lost useful functionality and to make my project >> compatible with Pharo 7, I have to make lots of effort to make my code >> uglier and longer >> >> I would like to ask for the reason of this change and whether is there >> anything that can be done with it. Or do I just misuse or misunderstand >> anything? Thank you. >> >> Best regards, >> Jan >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> > >

Feb. 18, 2019

Re: [Pharo-users] [TelePharo] Error in remote playground..

by Denis Kudriashov

Yes 18 ÑÐµÐ²Ñ. 2019 Ð³. 14:37 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "sergio ruiz" <sergio.rrd(a)gmail.com> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: Awesome! is this the one i should be using? https://github.com/pharo-ide/TelePharo Thanks! On February 17, 2019 at 3:06:18 PM, Denis Kudriashov (dionisiydk(a)gmail.com) wrote: I released new version of TelePharo adopted for Pharo 7. So now it should work out of the box ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 18, 2019

Re: [Pharo-users] Bloc Tutorial

by horrido

Whoa! This works! Thank you very much. Andrei Chis wrote > In the same image you can do that from the Iceberg user interface. You can > open Iceberg from the Tools menu. > Then right click on the Tutorial project and from the context menu select > Pull. > > On Mon, Feb 18, 2019 at 12:29 AM horrido < > horrido.hobbies@ > > wrote: > >> So how do I force Iceberg to reload? >> >> >> Andrei Chis wrote >> > If you use repositories that start with `github://` in Metacello you >> are >> > using Iceberg. Iceberg is used to clone and load the code. Metacello is >> > just the interface through which that is done. >> > >> > Running the loading instruction does not pull new changes from remote >> > repositories. >> > >> > On Sun, Feb 17, 2019 at 10:11 PM horrido < >> >> > horrido.hobbies@ >> >> > > wrote: >> > >> >> ??? >> >> >> >> I'm not using a cloned repository. I'm using Metacello just like in >> the >> >> snippet I showed you. Shouldn't it pull in the latest repo? >> >> >> >> I've never used Iceberg; I don't know how to use it. I don't really >> want >> >> to >> >> fuck around with GitHub. I don't want to be pulled into a rabbit hole. >> >> >> >> >> >> >> >> Andrei Chis wrote >> >> > If you already have the repository cloned, running the code that you >> >> > mentioned does not update the content of the repository. >> >> > Hence, the existing version will be loaded again. >> >> > >> >> > Instead you need to do a pull using Iceberg to update the content of >> >> the >> >> > repository and the code. >> >> > >> >> > Cheers, >> >> > Andrei >> >> > >> >> > On Sun, Feb 17, 2019 at 8:06 PM horrido < >> >> >> >> > horrido.hobbies@ >> >> >> >> > > wrote: >> >> > >> >> >> If you're referring to this: >> >> >> >> >> >> Metacello new >> >> >> baseline: 'BlocTutorials'; >> >> >> repository: 'github://pharo-graphics/Tutorials/src'; >> >> >> load >> >> >> >> >> >> It made no difference. Same error message. >> >> >> >> >> >> >> >> >> >> >> >> Andrei Chis wrote >> >> >> > Hi, >> >> >> > >> >> >> > Thanks for the bug report. >> >> >> > Can you try loading the latest version for the code of the >> tutorial. >> >> I >> >> >> > fixed the deprecation warning. >> >> >> > >> >> >> > Let us know if you encounter any other issues. >> >> >> > >> >> >> > Cheers, >> >> >> > Andrei >> >> >> > >> >> >> > On Sun, Feb 17, 2019 at 6:49 PM Richard Kenneth Eng < >> >> >> >> >> >> > horrido.hobbies@ >> >> >> >> >> >> >> wrote: >> >> >> > >> >> >> >> I'm following the tutorial in the MemoryGame booklet. When I run >> >> the >> >> >> game >> >> >> >> and click on any square, I get: >> >> >> >> >> >> >> >> The method BlBaseAnimation>>#startOn: called from >> >> >> >> MgCardElement>>#onFlippedFace has been deprecated. >> >> >> >> Use BlElement>>#addAnimation: >> >> >> >> >> >> >> >> The tutorial is out of sync. How can I proceed? >> >> >> >> >> >> >> >> Is there another way to learn how to use Bloc? >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> 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 >> >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 18, 2019

Re: [Pharo-users] Calypso documentation? Or understanding menu building

by Tim Mackinnon

Hi Dennis - Iâve been reading the book you mentioned and looking through the code as well as your examples and I feel a bit more comfortable with whatâs going on - however I am stumped about how you do an OR context (vs. an AND context). I would like my menu item to appear for either a selected RPackage OR a ClyTaggedClassGroup - I thought I had it with: RPackage asCalypsoItemContext, ClyTaggedClassGroup asCalypsoItemContext (to get a composite context) but then I realised that the composite is an AND. Is there some way to create an OR context, or do I simply have to create multiple commands? Tim > On 12 Feb 2019, at 19:32, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi Tim > > Ð²Ñ, 12 ÑÐµÐ²Ñ. 2019 Ð³. Ð² 13:42, Tim Mackinnon <tim(a)testit.works>: > Is there any documentation on Calypso application contexts? I am trying to add a menu item to a package tag (the bit underneath a package - which I often call a sub-package). > > Only class comments are available for Calypso. Also there are a Commander booklet <https://github.com/SquareBracketAssociates/Booklet-Infrastructure>which describes contexts and ClassAnnotation github readme <https://github.com/pharo-ide/ClassAnnotation> (together with class comments). > > > Iâve specified: > > ^CmdContextMenuActivation > byItemOf: ClyQueryMenuGroup for: RPackage asCalypsoItemContext > > > The #for: argument of command activations is a context where command should be available. Context describes condition where given command (its activation strategy) should be visible for users. > In your example "RPackage asCalypsoItemContext" is an instance of ClyBrowserItemContext which matches any selected package in the browser (when a kind of RPackage is selected). > And that's why you do not see it on selected tag because the tag is not a package. > > But that puts my menu on the package and not the tag > - and if I use the inspect extra menu in calypso, I get what looks to be something that could help me determine what I want but Iâm struggling to understand what ClyTaggedClassGroup does, and what a context is all about. > > Inspect command opens inspector of actually selected object which is an instance of ClyTaggedClassGroup in that case (try inspect selected method and you will get a CompiledMethod). > Children of package in browser are instances of ClyClassGroup and subclasses. So they are not raw tags. If you need a command for a tag you should add a command for ClyTaggedClassGroup items: > > ^CmdContextMenuActivation > byItemOf: ClyQueryMenuGroup for: ClyTaggedClassGroup asCalypsoItemContext > > Look for example at SycPromotePackageFromTagCommand class>>#fullBrowserMenuActivation which is defined this way. > > There are other kind of contexts which can be used in command annotations. For example if you want a command for selected method only in full browser then you should use ClyMethodContextOfFullBrowser: > > ^CmdContextMenuActivation byItemOf: ClyQueryMenuGroup for: ClyMethodContextOfFullBrowser > > it can be confusing that simple class is used in this case. But underhood it is converted to the instance of context where command should be available. > > > Has anyone else played around with this at all? > > Ideally I want to have a menu appear on all the tags underneath a particular package - and possibly including that package (or maybe not - I havenât decided as I want to try it in the wild). > > While Iâm at it - I have quite understood how to create submenuâs either - as Iâd like to have several commands all as sub items of a menu item âExercismâ. > > Look at commander booklet. It includes example. > > > Tim > > >

Feb. 18, 2019

Re: [Pharo-users] [TelePharo] Error in remote playground..

by sergio ruiz

Awesome! is this the one i should be using? https://github.com/pharo-ide/TelePharo Thanks! On February 17, 2019 at 3:06:18 PM, Denis Kudriashov (dionisiydk(a)gmail.com) wrote: I released new version of TelePharo adopted for Pharo 7. So now it should work out of the box ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 18, 2019

Re: [Pharo-users] Bloc Tutorial

by Andrei Chis

In the same image you can do that from the Iceberg user interface. You can open Iceberg from the Tools menu. Then right click on the Tutorial project and from the context menu select Pull. On Mon, Feb 18, 2019 at 12:29 AM horrido <horrido.hobbies(a)gmail.com> wrote: > So how do I force Iceberg to reload? > > > Andrei Chis wrote > > If you use repositories that start with `github://` in Metacello you are > > using Iceberg. Iceberg is used to clone and load the code. Metacello is > > just the interface through which that is done. > > > > Running the loading instruction does not pull new changes from remote > > repositories. > > > > On Sun, Feb 17, 2019 at 10:11 PM horrido < > > > horrido.hobbies@ > > > > wrote: > > > >> ??? > >> > >> I'm not using a cloned repository. I'm using Metacello just like in the > >> snippet I showed you. Shouldn't it pull in the latest repo? > >> > >> I've never used Iceberg; I don't know how to use it. I don't really want > >> to > >> fuck around with GitHub. I don't want to be pulled into a rabbit hole. > >> > >> > >> > >> Andrei Chis wrote > >> > If you already have the repository cloned, running the code that you > >> > mentioned does not update the content of the repository. > >> > Hence, the existing version will be loaded again. > >> > > >> > Instead you need to do a pull using Iceberg to update the content of > >> the > >> > repository and the code. > >> > > >> > Cheers, > >> > Andrei > >> > > >> > On Sun, Feb 17, 2019 at 8:06 PM horrido < > >> > >> > horrido.hobbies@ > >> > >> > > wrote: > >> > > >> >> If you're referring to this: > >> >> > >> >> Metacello new > >> >> baseline: 'BlocTutorials'; > >> >> repository: 'github://pharo-graphics/Tutorials/src'; > >> >> load > >> >> > >> >> It made no difference. Same error message. > >> >> > >> >> > >> >> > >> >> Andrei Chis wrote > >> >> > Hi, > >> >> > > >> >> > Thanks for the bug report. > >> >> > Can you try loading the latest version for the code of the > tutorial. > >> I > >> >> > fixed the deprecation warning. > >> >> > > >> >> > Let us know if you encounter any other issues. > >> >> > > >> >> > Cheers, > >> >> > Andrei > >> >> > > >> >> > On Sun, Feb 17, 2019 at 6:49 PM Richard Kenneth Eng < > >> >> > >> >> > horrido.hobbies@ > >> >> > >> >> >> wrote: > >> >> > > >> >> >> I'm following the tutorial in the MemoryGame booklet. When I run > >> the > >> >> game > >> >> >> and click on any square, I get: > >> >> >> > >> >> >> The method BlBaseAnimation>>#startOn: called from > >> >> >> MgCardElement>>#onFlippedFace has been deprecated. > >> >> >> Use BlElement>>#addAnimation: > >> >> >> > >> >> >> The tutorial is out of sync. How can I proceed? > >> >> >> > >> >> >> Is there another way to learn how to use Bloc? > >> >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> -- > >> >> 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 > >

Feb. 18, 2019

Re: [Pharo-users] Monticello diff between image and tonel repo

by Hilaire

I confirm again this issue, while annoying, flushing Monticello helps to get a proper diff. https://github.com/pharo-project/pharo/issues/2583 Hilaire Le 16/02/2019 Ã 11:56, Hilaire a Ã©critÂ : > Closing Monticello windows and opening a fresh one helped to get the > changes right, sometime... Other time, forcing flush cash on Monticello > helps. -- Dr. Geo http://drgeo.eu

Feb. 18, 2019

Re: [Pharo-users] Iceberg working with forks - can it be easier?

by Guillermo Polito

On Mon, Feb 18, 2019 at 7:50 AM Konrad Hinsen <konrad.hinsen(a)fastmail.net> wrote: > Am 18.02.19 um 01:19 schrieb Tim Mackinnon: > > > Hey Ben - Iâm not sure that this actually does the same thing. I just > > tried it now, and it resulted in an extra merge in my forked repo - as I > > think this effectively pulls down from upstream into pharo and then if > > you have any differences in your local image copy they might cause some > > changes which then you would push back into your fork origin. > > > > If you just want a verbatim copy in your fork - you have to resort the > > command line? > > That's at least what I do: > > git pull upstream master > git push origin master > > I am pretty sure these basic operations are somewhere accessible in the > Iceberg code, but I have no idea how. > You can do these two from the UI :) You cannot do (from the UI) - a push --force - a reset You can do the reset from Iceberg's API, but you the force is not implemented yet... > > Iceberg would definitely gain from having a documented programmer's > interface. Git is way too complicated for a point-and-click interface to > be sufficient. I'd even say that "scriptable git" could become a Pharo > killer feature if done well. > This will soon come ;) At least the documented API for the most common features (then ones that are stable enough ^^). It's just people in our team is super busy... > > Konrad. > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Feb. 18, 2019

Re: [Pharo-users] Iceberg working with forks - can it be easier?

by Guillermo Polito

On Mon, Feb 18, 2019 at 2:45 AM Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Tim Mackinnon wrote > > wouldnât it be helpful if this was a command in Iceberg? > > Yes! This is a super common task and for easy cases would be great to > automate > https://help.github.com/articles/syncing-a-fork/ > > > That's useful as long as you don't find you have extra commits in your branch [image: image.png] Which AFAIU, it's Tim's case.

Feb. 18, 2019

Re: [Pharo-users] Iceberg working with forks - can it be easier?

by Guillermo Polito

On Mon, Feb 18, 2019 at 1:19 AM Tim Mackinnon <tim(a)testit.works> wrote: > Hey Ben - Iâm not sure that this actually does the same thing. I just > tried it now, and it resulted in an extra merge in my forked repo - as I > think this effectively pulls down from upstream into pharo and then if you > have any differences in your local image copy they might cause some changes > which then you would push back into your fork origin. > > If you just want a verbatim copy in your fork - you have to resort the > command line? > Ah! well merging may do two things: - create a merge commit (in case of diverging history) - do a fast forward (just update your branch) The thing is that you want to **undo** your changes before merging, otherwise you'll have a dangling commit there that you did not want :). You cannot do that from Iceberg's UI right now, you can do it from any expression evaluator: "Rough equivalent of reset --hard HEAD~1" repository branch commit: repository branch commit parent. But even then, Iceberg does not (yet) implement push --force, because we never found a useful use case (other than bad practices) to it. This is important: if you have made changes to your repository, then "making a verbatim copy" means to undo your changes. Even from the command line, what you may want to do is: move to another branch, remove your "to-sync" branch, fetch from origin, checkout origin/"to-sync", push force to your fork. But you may lose your changes... > Iâm still mulling this over - as would you then pull from your upstream > fork and still get the same differences that you would then apply? Iâm not > sure now - but if the idea was just to get yourself back into a consistent > state - Its not clear to me how you can get all 3 copies saying the same > thing in pharo? > > Tim > > On 16 Feb 2019, at 06:19, Ben Coman <btc(a)openInWorld.com> wrote: > > > > On Sat, 16 Feb 2019 at 02:06, Tim Mackinnon <tim(a)testit.works> wrote: > >> Hi guys - Iâve spent a few hours scratching my head trying to understand >> why some of my Pull Requests to a project I had forked kept showing my >> previous commits when I thought I was all caught up. >> >> It suddenly dawned on me, that when I had forked, and then done some work >> and then submitted a PR, and then applied it upstream that my fork is now >> no longer in sync with its upstream counterpart. >> >> Having not done this in ages, it took me a while to then realise I have >> to do some git stuff to get it back in sync e.g. (and I think Iâve got this >> right) >> >> git fetch upstream (or whatever name you gave it) >> Git checkout master >> Git merge upstream/master >> >> So I guess my question is - wouldnât it be helpful if this was a command >> in Iceberg? It seems quite common to fork a project (I think this is still >> recommended for pharo itself isnât it?) - and then at some point you need >> to catchup with that origin again? Or am I missing something? I guess lots >> of stuff can go wrong - but if it does - youâd still get the same problems >> on the command line. It just seems that for normal situations - it would be >> handy to run this straight in Pharo. >> > > I'm not fully-conversant with Iceberg, but if I guess right... > in Iceberg, right-click a repo and open its "Repository" window. > In the top-right click the "Add remote" button, to add the upstream repo. > That button is a bit hidden there. It might be nice to have it as a menu > item on "Remotes" in the first pane. > Then click the <Merge> button, then select the upstream master branch and > you should be up to date. > > cheers -ben > > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Feb. 18, 2019

Re: [Pharo-users] Iceberg working with forks - can it be easier?

by Guillermo Polito

Hi! On Fri, Feb 15, 2019 at 7:06 PM Tim Mackinnon <tim(a)testit.works> wrote: > Hi guys - Iâve spent a few hours scratching my head trying to understand > why some of my Pull Requests to a project I had forked kept showing my > previous commits when I thought I was all caught up. > > It suddenly dawned on me, that when I had forked, and then done some work > and then submitted a PR, and then applied it upstream that my fork is now > no longer in sync with its upstream counterpart. > > Having not done this in ages, it took me a while to then realise I have to > do some git stuff to get it back in sync e.g. (and I think Iâve got this > right) > > git fetch upstream (or whatever name you gave it) > Git checkout master > Git merge upstream/master > When you did your clone, did you clone the original repository or your fork's? One way to simplify this workflow is: - you clone always the original repository - you create a branch and work there - then you'll push your branch to your fork + fork That way your branch will be always up to date with the original repository, and no need to sync (actually the sync is done automatically when you push to your fork). Of course this assumes you're doing a new clone every time you work :). > > So I guess my question is - wouldnât it be helpful if this was a command > in Iceberg? It would, there are several places where we could simplify the workflow for common cases, I agree. > It seems quite common to fork a project (I think this is still recommended > for pharo itself isnât it?) I'd say its mandatory :). Otherwise you will not be able to push directly to it because of permission problems (actually all main dev branches are now blocked so **nobody**, not even admins, push to them directly). > - and then at some point you need to catchup with that origin again? Or am > I missing something? Well, it really depends on the workflow you use. Above I've explained a workflow that works when you clone every time. Git is so complex and so low level that you can do lots of different things with it. First thing is to understand what "catch up with origin" means. In my head it only means: - checkout your "to-catchup" branch - merge the remote "to-catchup" branch and merge it All the rest is workflow dependent. Even (!!) I would argue that merging is not, strictly speaking, a correct way to catch up: If you have made changes into "to-catchup", then merging will not make both branches the same, but your "to-catchup" branch may have extra commits that you did not want to introduce... And here I'm not saying you should not merge, actually I do it most of the times because I know that 90% of the times it will be ok, and I do rollback when I realize I was in the other 10%... > I guess lots of stuff can go wrong - but if it does - youâd still get the > same problems on the command line. Yes, and no. The "lots of stuff can go wrong" can be translated in most of the cases to "I had a merge conflict". But this is not git, this is git+pharo. The thing is that with Git, your code is dead in files. With Iceberg, your code is in the files but it also may be alive in your image too. So updating code for what you have existing instances, or announcement subscriptions or other could (and probably will) mess up with the running code... So to the typical merge conflict, you may add breaking your running system. It just seems that for normal situations - it would be handy to run this > straight in Pharo. > > Thoughts from the git experts? > For these cases, you can do exactly as the command line from Iceberg's UI - change your branch to your "to-catchup" master - fetch - now you can go to the merge option, and choose to merge your remote branch into your checked-out branch. - and push Of course, this simple workflow works most of the times, but you may find edge cases. For those edge cases (typically updating iceberg itself, or trying to update pharo itself), in the checkout preview you will have the combo with the checkout strategy: choose the expert mode "do not load the code". This option will change the branch on git's world, but it will not load the code in your image. That is useful if you have living instances for example. This option will though make a diff between the checked out version and your image code and show you differences. (think this as a git reset --soft) To me the fact that we are manipulating live code loaded in the image and not dead files makes a huge difference, and this makes that extrapolating git commands to iceberg is not so straight forward :). Also, understanding that git is stateful/context dependant, and applying an operation means changing your current state (modify your current branch, change your current branch) is useful to see the consequences. In any case, any more concrete suggestions for enhancing this workflow are welcome. I think that neither Esteban, Pablo, me nor other contributors are skilled UI designers, and thinking about the best way to present a usecase to a user is super super hard :). Guille, from his vacations

Feb. 18, 2019

Re: [Pharo-users] Stability of Pharo 7 vs 6?

by Hilaire

Le 18/02/2019 Ã 02:00, Tim Mackinnon a Ã©critÂ : > > Having said this - Iâm still not having the smooth ride others are > reporting - and 7 is still suspect to me. Indeed, the Pharo stability (or any other software) depends on several factors: in your case OSX, fullscreen, P7 image and VM, plugin. Also likely, not many of us are using Pharo fullscreen > > Iâm kind of suprised this isnât getting much traction from the core > team - and I wonder if I should post this on the dev list instead? > Reporting these kind of issues here seems to me as the right place. The dev list is dedicated to exchange related to the development of Pharo. As your issue is likely related to the VM, you could report it to the VM list, there http://forum.world.st/Squeak-VM-f104410.html? You may have some additional clues. While it is annoying to be under such circumstance when you just want to work on your project (been there many times), it could be a valuable contribution, eventually with self knowledge amplification outcome. Hilaire -- Dr. Geo http://drgeo.eu

Feb. 18, 2019

Re: [Pharo-users] Iceberg working with forks - can it be easier?

by Konrad Hinsen

Am 18.02.19 um 01:19 schrieb Tim Mackinnon: > Hey Ben - Iâm not sure that this actually does the same thing. I just > tried it now, and it resulted in an extra merge in my forked repo - as I > think this effectively pulls down from upstream into pharo and then if > you have any differences in your local image copy they might cause some > changes which then you would push back into your fork origin. > > If you just want a verbatim copy in your fork - you have to resort the > command line? That's at least what I do: git pull upstream master git push origin master I am pretty sure these basic operations are somewhere accessible in the Iceberg code, but I have no idea how. Iceberg would definitely gain from having a documented programmer's interface. Git is way too complicated for a point-and-click interface to be sufficient. I'd even say that "scriptable git" could become a Pharo killer feature if done well. Konrad.

Feb. 18, 2019

Re: [Pharo-users] Bloc Tutorial

by Tudor Girba

Hi, The simplest thing is to take a fresh image, in a fresh directory and rerun the Metacello script. Let us know how it works. Cheers, Doru > On Feb 18, 2019, at 12:28 AM, horrido <horrido.hobbies(a)gmail.com> wrote: > > So how do I force Iceberg to reload? > > > Andrei Chis wrote >> If you use repositories that start with `github://` in Metacello you are >> using Iceberg. Iceberg is used to clone and load the code. Metacello is >> just the interface through which that is done. >> >> Running the loading instruction does not pull new changes from remote >> repositories. >> >> On Sun, Feb 17, 2019 at 10:11 PM horrido < > >> horrido.hobbies@ > >> > wrote: >> >>> ??? >>> >>> I'm not using a cloned repository. I'm using Metacello just like in the >>> snippet I showed you. Shouldn't it pull in the latest repo? >>> >>> I've never used Iceberg; I don't know how to use it. I don't really want >>> to >>> fuck around with GitHub. I don't want to be pulled into a rabbit hole. >>> >>> >>> >>> Andrei Chis wrote >>>> If you already have the repository cloned, running the code that you >>>> mentioned does not update the content of the repository. >>>> Hence, the existing version will be loaded again. >>>> >>>> Instead you need to do a pull using Iceberg to update the content of >>> the >>>> repository and the code. >>>> >>>> Cheers, >>>> Andrei >>>> >>>> On Sun, Feb 17, 2019 at 8:06 PM horrido < >>> >>>> horrido.hobbies@ >>> >>>> > wrote: >>>> >>>>> If you're referring to this: >>>>> >>>>> Metacello new >>>>> baseline: 'BlocTutorials'; >>>>> repository: 'github://pharo-graphics/Tutorials/src'; >>>>> load >>>>> >>>>> It made no difference. Same error message. >>>>> >>>>> >>>>> >>>>> Andrei Chis wrote >>>>>> Hi, >>>>>> >>>>>> Thanks for the bug report. >>>>>> Can you try loading the latest version for the code of the tutorial. >>> I >>>>>> fixed the deprecation warning. >>>>>> >>>>>> Let us know if you encounter any other issues. >>>>>> >>>>>> Cheers, >>>>>> Andrei >>>>>> >>>>>> On Sun, Feb 17, 2019 at 6:49 PM Richard Kenneth Eng < >>>>> >>>>>> horrido.hobbies@ >>>>> >>>>>>> wrote: >>>>>> >>>>>>> I'm following the tutorial in the MemoryGame booklet. When I run >>> the >>>>> game >>>>>>> and click on any square, I get: >>>>>>> >>>>>>> The method BlBaseAnimation>>#startOn: called from >>>>>>> MgCardElement>>#onFlippedFace has been deprecated. >>>>>>> Use BlElement>>#addAnimation: >>>>>>> >>>>>>> The tutorial is out of sync. How can I proceed? >>>>>>> >>>>>>> Is there another way to learn how to use Bloc? >>>>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> 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 -- www.feenk.com "We are all great at making mistakes."

Feb. 18, 2019

Re: [Pharo-users] Iceberg working with forks - can it be easier?

by Sean P. DeNigris

Tim Mackinnon wrote > wouldnât it be helpful if this was a command in Iceberg? Yes! This is a super common task and for easy cases would be great to automate https://help.github.com/articles/syncing-a-fork/ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 18, 2019

Re: [Pharo-users] im using pharo 7 with linux env. but cannot input korean.

by Sean P. DeNigris

HilaireFernandes wrote > In your trad. chinese app were you able to key in chinese? I didn't try because the characters were pulled in from an external data source. I only needed to display them. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 18, 2019

Re: [Pharo-users] Stability of Pharo 7 vs 6?

by Tim Mackinnon

Hmmm Ben - its interesting that other languages/environments show that same stack error - and they seem to hint at memory issues- although in our case Iâm working with a simple Pharo image that has very little in it (Iâve had much larger ones in Pharo 6.x without issue). Interestingly - since launching a zeroconf image and not going full screen - its been running now for 1.5 days without a crash (whereas previously around 24 hours or less it would crash). Having said this - Iâve just started another clean zeroconf image (not full screen) and during the initial metecallo (iceberg) load - its seg faulted again - but this one I think is iceberg related as the crash.dmp looks a bit different, and I did notice that it was loading my baseline a bit slowly (and stifling with some of the dependencies, making me think that something timing related might be at issue). Having said this - Iâm still not having the smooth ride others are reporting - and 7 is still suspect to me. Iâm kind of suprised this isnât getting much traction from the core team - and I wonder if I should post this on the dev list instead? Tim > On 16 Feb 2019, at 16:27, Ben Coman <btc(a)openInWorld.com> wrote: > > I'm not on a Mac to test, but it might be worth browsing the top few of these.. > https://github.com/search?o=desc&q=can%27t+allocate+region+securely&s=creat… <https://github.com/search?o=desc&q=can%27t+allocate+region+securely&s=creat…> > > cheers -ben > > On Sat, 16 Feb 2019 at 20:10, Tim Mackinnon <tim(a)testit.works> wrote: > Iâve actually being using both - but 32bit has generally been considered the older more stable cousin (until Pharo 6 - where it was felt that 64bit was now just as stable). > > I only mentioned it - because the zeroconf example that has crashed a few of my several times - was 32 bit (but I have also had 64 bit crash too. Probably a good experiment to try zeroconf with the 64bit variation and load my baseline as well). > > I just think we might have an easily reproducable (and small) example that shows this issue that many have experienced a bit more randomly. >

Feb. 18, 2019

Re: [Pharo-users] Iceberg working with forks - can it be easier?

by Tim Mackinnon

Hey Ben - Iâm not sure that this actually does the same thing. I just tried it now, and it resulted in an extra merge in my forked repo - as I think this effectively pulls down from upstream into pharo and then if you have any differences in your local image copy they might cause some changes which then you would push back into your fork origin. If you just want a verbatim copy in your fork - you have to resort the command line? Iâm still mulling this over - as would you then pull from your upstream fork and still get the same differences that you would then apply? Iâm not sure now - but if the idea was just to get yourself back into a consistent state - Its not clear to me how you can get all 3 copies saying the same thing in pharo? Tim > On 16 Feb 2019, at 06:19, Ben Coman <btc(a)openInWorld.com> wrote: > > > > On Sat, 16 Feb 2019 at 02:06, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: > Hi guys - Iâve spent a few hours scratching my head trying to understand why some of my Pull Requests to a project I had forked kept showing my previous commits when I thought I was all caught up. > > It suddenly dawned on me, that when I had forked, and then done some work and then submitted a PR, and then applied it upstream that my fork is now no longer in sync with its upstream counterpart. > > Having not done this in ages, it took me a while to then realise I have to do some git stuff to get it back in sync e.g. (and I think Iâve got this right) > > git fetch upstream (or whatever name you gave it) > Git checkout master > Git merge upstream/master > > So I guess my question is - wouldnât it be helpful if this was a command in Iceberg? It seems quite common to fork a project (I think this is still recommended for pharo itself isnât it?) - and then at some point you need to catchup with that origin again? Or am I missing something? I guess lots of stuff can go wrong - but if it does - youâd still get the same problems on the command line. It just seems that for normal situations - it would be handy to run this straight in Pharo. > > I'm not fully-conversant with Iceberg, but if I guess right... > in Iceberg, right-click a repo and open its "Repository" window. > In the top-right click the "Add remote" button, to add the upstream repo. > That button is a bit hidden there. It might be nice to have it as a menu item on "Remotes" in the first pane. > Then click the <Merge> button, then select the upstream master branch and you should be up to date. > > cheers -ben

Feb. 18, 2019

Re: [Pharo-users] Bloc Tutorial

by horrido

So how do I force Iceberg to reload? Andrei Chis wrote > If you use repositories that start with `github://` in Metacello you are > using Iceberg. Iceberg is used to clone and load the code. Metacello is > just the interface through which that is done. > > Running the loading instruction does not pull new changes from remote > repositories. > > On Sun, Feb 17, 2019 at 10:11 PM horrido < > horrido.hobbies@ > > wrote: > >> ??? >> >> I'm not using a cloned repository. I'm using Metacello just like in the >> snippet I showed you. Shouldn't it pull in the latest repo? >> >> I've never used Iceberg; I don't know how to use it. I don't really want >> to >> fuck around with GitHub. I don't want to be pulled into a rabbit hole. >> >> >> >> Andrei Chis wrote >> > If you already have the repository cloned, running the code that you >> > mentioned does not update the content of the repository. >> > Hence, the existing version will be loaded again. >> > >> > Instead you need to do a pull using Iceberg to update the content of >> the >> > repository and the code. >> > >> > Cheers, >> > Andrei >> > >> > On Sun, Feb 17, 2019 at 8:06 PM horrido < >> >> > horrido.hobbies@ >> >> > > wrote: >> > >> >> If you're referring to this: >> >> >> >> Metacello new >> >> baseline: 'BlocTutorials'; >> >> repository: 'github://pharo-graphics/Tutorials/src'; >> >> load >> >> >> >> It made no difference. Same error message. >> >> >> >> >> >> >> >> Andrei Chis wrote >> >> > Hi, >> >> > >> >> > Thanks for the bug report. >> >> > Can you try loading the latest version for the code of the tutorial. >> I >> >> > fixed the deprecation warning. >> >> > >> >> > Let us know if you encounter any other issues. >> >> > >> >> > Cheers, >> >> > Andrei >> >> > >> >> > On Sun, Feb 17, 2019 at 6:49 PM Richard Kenneth Eng < >> >> >> >> > horrido.hobbies@ >> >> >> >> >> wrote: >> >> > >> >> >> I'm following the tutorial in the MemoryGame booklet. When I run >> the >> >> game >> >> >> and click on any square, I get: >> >> >> >> >> >> The method BlBaseAnimation>>#startOn: called from >> >> >> MgCardElement>>#onFlippedFace has been deprecated. >> >> >> Use BlElement>>#addAnimation: >> >> >> >> >> >> The tutorial is out of sync. How can I proceed? >> >> >> >> >> >> Is there another way to learn how to use Bloc? >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> 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

Feb. 17, 2019

Re: [Pharo-users] Bloc Tutorial

by Andrei Chis

If you use repositories that start with `github://` in Metacello you are using Iceberg. Iceberg is used to clone and load the code. Metacello is just the interface through which that is done. Running the loading instruction does not pull new changes from remote repositories. On Sun, Feb 17, 2019 at 10:11 PM horrido <horrido.hobbies(a)gmail.com> wrote: > ??? > > I'm not using a cloned repository. I'm using Metacello just like in the > snippet I showed you. Shouldn't it pull in the latest repo? > > I've never used Iceberg; I don't know how to use it. I don't really want to > fuck around with GitHub. I don't want to be pulled into a rabbit hole. > > > > Andrei Chis wrote > > If you already have the repository cloned, running the code that you > > mentioned does not update the content of the repository. > > Hence, the existing version will be loaded again. > > > > Instead you need to do a pull using Iceberg to update the content of the > > repository and the code. > > > > Cheers, > > Andrei > > > > On Sun, Feb 17, 2019 at 8:06 PM horrido < > > > horrido.hobbies@ > > > > wrote: > > > >> If you're referring to this: > >> > >> Metacello new > >> baseline: 'BlocTutorials'; > >> repository: 'github://pharo-graphics/Tutorials/src'; > >> load > >> > >> It made no difference. Same error message. > >> > >> > >> > >> Andrei Chis wrote > >> > Hi, > >> > > >> > Thanks for the bug report. > >> > Can you try loading the latest version for the code of the tutorial. I > >> > fixed the deprecation warning. > >> > > >> > Let us know if you encounter any other issues. > >> > > >> > Cheers, > >> > Andrei > >> > > >> > On Sun, Feb 17, 2019 at 6:49 PM Richard Kenneth Eng < > >> > >> > horrido.hobbies@ > >> > >> >> wrote: > >> > > >> >> I'm following the tutorial in the MemoryGame booklet. When I run the > >> game > >> >> and click on any square, I get: > >> >> > >> >> The method BlBaseAnimation>>#startOn: called from > >> >> MgCardElement>>#onFlippedFace has been deprecated. > >> >> Use BlElement>>#addAnimation: > >> >> > >> >> The tutorial is out of sync. How can I proceed? > >> >> > >> >> Is there another way to learn how to use Bloc? > >> >> > >> > >> > >> > >> > >> > >> -- > >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >> > >> > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Feb. 17, 2019

Re: [Pharo-users] Bloc Tutorial

by horrido

??? I'm not using a cloned repository. I'm using Metacello just like in the snippet I showed you. Shouldn't it pull in the latest repo? I've never used Iceberg; I don't know how to use it. I don't really want to fuck around with GitHub. I don't want to be pulled into a rabbit hole. Andrei Chis wrote > If you already have the repository cloned, running the code that you > mentioned does not update the content of the repository. > Hence, the existing version will be loaded again. > > Instead you need to do a pull using Iceberg to update the content of the > repository and the code. > > Cheers, > Andrei > > On Sun, Feb 17, 2019 at 8:06 PM horrido < > horrido.hobbies@ > > wrote: > >> If you're referring to this: >> >> Metacello new >> baseline: 'BlocTutorials'; >> repository: 'github://pharo-graphics/Tutorials/src'; >> load >> >> It made no difference. Same error message. >> >> >> >> Andrei Chis wrote >> > Hi, >> > >> > Thanks for the bug report. >> > Can you try loading the latest version for the code of the tutorial. I >> > fixed the deprecation warning. >> > >> > Let us know if you encounter any other issues. >> > >> > Cheers, >> > Andrei >> > >> > On Sun, Feb 17, 2019 at 6:49 PM Richard Kenneth Eng < >> >> > horrido.hobbies@ >> >> >> wrote: >> > >> >> I'm following the tutorial in the MemoryGame booklet. When I run the >> game >> >> and click on any square, I get: >> >> >> >> The method BlBaseAnimation>>#startOn: called from >> >> MgCardElement>>#onFlippedFace has been deprecated. >> >> Use BlElement>>#addAnimation: >> >> >> >> The tutorial is out of sync. How can I proceed? >> >> >> >> Is there another way to learn how to use Bloc? >> >> >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 17, 2019

Re: [Pharo-users] [TelePharo] Error in remote playground..

by Denis Kudriashov

Hi Sergio. I released new version of TelePharo adopted for Pharo 7. So now it should work out of the box Ð²Ñ, 12 ÑÐµÐ²Ñ. 2019 Ð³. Ð² 21:24, Denis Kudriashov <dionisiydk(a)gmail.com>: > I think it would be enough to do on client side > > 12 ÑÐµÐ²Ñ. 2019 Ð³. 21:23 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "Denis Kudriashov" < > dionisiydk(a)gmail.com> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: > > Checkout dev branch using iceberg > > 12 ÑÐµÐ²Ñ. 2019 Ð³. 21:10 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "sergio ruiz" <sergio.rrd(a)gmail.com> > Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: > > I am not sure I follow.. > > Do you mean grab the source from github using Iceberg? > > Thanks! > > On February 12, 2019 at 4:03:25 PM, Denis Kudriashov (dionisiydk(a)gmail.com) > wrote: > > Ah, it needs new release. > Try load dev versions of telepharo and seamless from Iceberg > > ---- > > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.codeandmusic.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101 > > > >

Feb. 17, 2019

Re: [Pharo-users] Bloc Tutorial

by Andrei Chis

If you already have the repository cloned, running the code that you mentioned does not update the content of the repository. Hence, the existing version will be loaded again. Instead you need to do a pull using Iceberg to update the content of the repository and the code. Cheers, Andrei On Sun, Feb 17, 2019 at 8:06 PM horrido <horrido.hobbies(a)gmail.com> wrote: > If you're referring to this: > > Metacello new > baseline: 'BlocTutorials'; > repository: 'github://pharo-graphics/Tutorials/src'; > load > > It made no difference. Same error message. > > > > Andrei Chis wrote > > Hi, > > > > Thanks for the bug report. > > Can you try loading the latest version for the code of the tutorial. I > > fixed the deprecation warning. > > > > Let us know if you encounter any other issues. > > > > Cheers, > > Andrei > > > > On Sun, Feb 17, 2019 at 6:49 PM Richard Kenneth Eng < > > > horrido.hobbies@ > > >> wrote: > > > >> I'm following the tutorial in the MemoryGame booklet. When I run the > game > >> and click on any square, I get: > >> > >> The method BlBaseAnimation>>#startOn: called from > >> MgCardElement>>#onFlippedFace has been deprecated. > >> Use BlElement>>#addAnimation: > >> > >> The tutorial is out of sync. How can I proceed? > >> > >> Is there another way to learn how to use Bloc? > >> > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Feb. 17, 2019

Re: [Pharo-users] Bloc Tutorial

by horrido

If you're referring to this: Metacello new baseline: 'BlocTutorials'; repository: 'github://pharo-graphics/Tutorials/src'; load It made no difference. Same error message. Andrei Chis wrote > Hi, > > Thanks for the bug report. > Can you try loading the latest version for the code of the tutorial. I > fixed the deprecation warning. > > Let us know if you encounter any other issues. > > Cheers, > Andrei > > On Sun, Feb 17, 2019 at 6:49 PM Richard Kenneth Eng < > horrido.hobbies@ >> wrote: > >> I'm following the tutorial in the MemoryGame booklet. When I run the game >> and click on any square, I get: >> >> The method BlBaseAnimation>>#startOn: called from >> MgCardElement>>#onFlippedFace has been deprecated. >> Use BlElement>>#addAnimation: >> >> The tutorial is out of sync. How can I proceed? >> >> Is there another way to learn how to use Bloc? >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 17, 2019

Re: [Pharo-users] Bloc Tutorial

by Andrei Chis

Hi, Thanks for the bug report. Can you try loading the latest version for the code of the tutorial. I fixed the deprecation warning. Let us know if you encounter any other issues. Cheers, Andrei On Sun, Feb 17, 2019 at 6:49 PM Richard Kenneth Eng < horrido.hobbies(a)gmail.com> wrote: > I'm following the tutorial in the MemoryGame booklet. When I run the game > and click on any square, I get: > > The method BlBaseAnimation>>#startOn: called from > MgCardElement>>#onFlippedFace has been deprecated. > Use BlElement>>#addAnimation: > > The tutorial is out of sync. How can I proceed? > > Is there another way to learn how to use Bloc? >

Feb. 17, 2019

Re: [Pharo-users] Pharo 7.0 image size

by Sven Van Caekenberghe

Sure that exists: SpaceTally printSpaceAnalysis will generate a file with all the data. But it probably won't be that easy to interpret. > On 17 Feb 2019, at 18:38, Trussardi Dario Romano <dario.trussardi(a)tiscali.it> wrote: > > Ciao, > > thanks Hilaire. > >> May be you have a lot of still open Seaside session, which if I remember >> correctly are automatically shutdown after 10 min when not active. >> >> Looking at Seaside session instances may give clue. > > OK, > > but it is possible to have a report on the state of employment related to each class? > > className Instances Memory > > ClassA 222 1MB > ClassB 11 128Byte > ecc..... > > Thanks, > > Dario >> >> Hilaire >> >> >> Le 16/02/2019 Ã 13:18, Trussardi Dario Romano a Ã©crit : >>> Starting from 94 MB, now after rebooting and save the image the relative size is 252 MB. >>> >>> How can I understand what is happening? >> >> -- >> Dr. Geo >> http://drgeo.eu >> >> >> > >

Feb. 17, 2019

Bloc Tutorial

by Richard Kenneth Eng

I'm following the tutorial in the MemoryGame booklet. When I run the game and click on any square, I get: The method BlBaseAnimation>>#startOn: called from MgCardElement>>#onFlippedFace has been deprecated. Use BlElement>>#addAnimation: The tutorial is out of sync. How can I proceed? Is there another way to learn how to use Bloc?

Feb. 17, 2019

Re: [Pharo-users] Pharo 7.0 image size

by Trussardi Dario Romano

Ciao, thanks Hilaire. > May be you have a lot of still open Seaside session, which if I remember > correctly are automatically shutdown after 10 min when not active. > > Looking at Seaside session instances may give clue. OK, but it is possible to have a report on the state of employment related to each class? className Instances Memory ClassA 222 1MB ClassB 11 128Byte ecc..... Thanks, Dario > > Hilaire > > > Le 16/02/2019 Ã 13:18, Trussardi Dario Romano a Ã©crit : >> Starting from 94 MB, now after rebooting and save the image the relative size is 252 MB. >> >> How can I understand what is happening? > > -- > Dr. Geo > http://drgeo.eu > > >

Feb. 17, 2019

Re: [Pharo-users] Working VM for OS X for Pharo 7

by Alistair Grant

Hi Hilaire, On Thu, 14 Feb 2019 at 11:54, Hilaire <hilaire(a)drgeo.eu> wrote: > > I know what you are describing, for example cairo can be impacted. > > My self questioning was: Does the VM rely on the host git library or is > the one shipped with the vm sufficient? I don't know the reasoning for including libgit2. For libssh2 I believe it was to ensure that certain options had been compiled in, maybe this is the same? Cheers, Alistair > Best, > > Hilaire > > Le 14/02/2019 Ã 10:33, Alistair Grant a Ã©crit : > > On Linux it is almost always: > > > > - A library isn't found because the search path is wrong, i.e. > > LD_LIBRARY_PATH needs to be set, and/or > > - there's a missing dependency. > > > > The ldd command helps track these down by showing which dependencies > > are missing. > > > > On Linux you need to be careful because the pharo script sets > > up LD_LIBRARY_PATH, so ldd may show something as missing which will be > > found when pharo is actually run, e.g libssh. > > > > Cheers, > > Alistair > > (on phone) > > -- > Dr. Geo > http://drgeo.eu > > >

Feb. 17, 2019

Re: [Pharo-users] Pharo 7.0 image size

by Hilaire

May be you have a lot of still open Seaside session, which if I remember correctly are automatically shutdown after 10 min when not active. Looking at Seaside session instances may give clue. Hilaire Le 16/02/2019 Ã 13:18, Trussardi Dario Romano a Ã©critÂ : > Starting from 94 MB, now after rebooting and save the image the relative size is 252 MB. > > How can I understand what is happening? -- Dr. Geo http://drgeo.eu

Feb. 17, 2019

Pragma "only for place of definition", is there one?

by Herby VojÄÃk

Hi! I'd just like to know if there is some pragma (eg. <onlyForMe>) which would say to a (class-level) method only to use the code in the case self is method definition class, otherwise just delegate to super. I only see it useful in class-side `initialize` method, as in: Foo class >> initialize self == Foo ifTrue: [ registry := Dictionary new ]. ^ super initialize would be Foo class >> initialize <onlyForMe> registry := Dictionary new Asking because I look for a way to easily subclass JS classes in Amber and such pragma would be useful in such cases, and since Amber treats Pharo as a reference, asking for the name of the pragma if there is one. Thanks, Herby

Feb. 16, 2019

Re: [Pharo-users] im using pharo 7 with linux env. but cannot input korean.

by peter yoo

maybe my linux env is fail now. because xterm cannot use korean input. more check after report this thread. thanks for all. :D

Feb. 16, 2019

Re: [Pharo-users] Streams for FileReference in Pharo 7

by Alistair Grant

On Sat, 16 Feb 2019 at 15:49, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 16 Feb 2019, at 14:35, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > Hi Sven & Jan, > > > > On Fri, 15 Feb 2019 at 10:25, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> > >> Hi Jan, > >> > >> I like #<< too, but I think your assumption that it can print anything on a stream is generally wrong, dangerous and unreliable. > >> > >> IMHO, you better stick to #print: in that case. > >> > >> Consider the follow, that all fail: > >> > >> String streamContents: [ :s | s << 'hello' << 42.5 << $! ]. > >> > >> String streamContents: [ :s | s << 'hello' << (1@2) << $! ]. > >> > >> In other words: #<< works in bizar ways (check the implementors of #putOn:). > >> > >> I would be inclined to change > >> > >> ZnEncodedStream>>#<< collection > >> ^ self nextPutAll: collection > >> > >> to > >> > >> ZnEncodedStream>>#<< collection > >> ^ self nextPutAll: collection asString > >> > >> but it would technically not be the same as the original #<< for in-memory streams. > >> > >> Opinions ? > > > > I've often thought that this change would be nice to have. #putOn: > > doesn't really fit in with writing to text streams (text in the loose > > sense of "something that will be read"). > > > > I think an argument could be made that #printString or #displayString > > should be used, but they both have their own issues in practice. > > So... > > > > +1 to "collection asString". > > > > Cheers, > > Alistair > > I have been thinking a bit more about this, and I have a lot of problems with > > Integer>>#putOn: aStream > aStream isBinary > ifTrue: [ self asByteArray do: [ :each | aStream nextPut: each ] ] > ifFalse: [ self asString putOn: aStream ] > > I think we should simply remove this method. It is ugly and wrong. > > #<< should simply be a shortcut for either #nextPut: and #nextPutAll: and nothing more. > > The following two are OK for me: > > String streamContents: [ :out | out << 'Hello' << $! ]. > ByteArray streamContents: [ :out | out << #[ 1 2 3 ] << 4 ]. > > But the following most definitively not: > > (ByteArray streamContents: [ :out | out << 16rFF << 16rFF11 << 16rFFFF22 << 16rFFFFFF33 ]) hex. > > When you write out an integer, you have to decide its size, that can never depend on the magnitude (because there is no way to read this back unless there is additional bracketing). > > Also, printing to a stream should be (very) efficient. Making copies of objects just for conversion purposes should be avoided. > > I think that if we remove Integer>>#putOn: I could live with > > ZnEncodedStream>>#<< anObject > anObject putOn: self > > The other solution is to define #<< as strictly the same as #nextPutAll: and remove all #putOn: implementors. My thoughts aren't fully formed on this, but: I think we can break the streams up in to three categories: - Streams of arbitrary objects, i.e. streams writing to Arrays, OrderedCollections, etc. - Streams that serialise the objects, e.g. JSON, STON, ASN.1, etc. - Streams that write to some form of text output intended for human reading. We can then group the messages used by each category: - Arbitrary object: nextPut:, nextPutAll:, putOn:, etc. - Serialising: stonOn:, etc. - Text: <<, cr, lf, etc. Following these guidelines: - I'd remove the Integer>>putOn: as you suggest. - Add the #asString to ZnEncodedStream>><< as suggested earlier. Cheers, Alistair

Feb. 16, 2019

Re: [Pharo-users] Stability of Pharo 7 vs 6?

by Ben Coman

I'm not on a Mac to test, but it might be worth browsing the top few of these.. https://github.com/search?o=desc&q=can%27t+allocate+region+securely&s=creat… cheers -ben On Sat, 16 Feb 2019 at 20:10, Tim Mackinnon <tim(a)testit.works> wrote: > Iâve actually being using both - but 32bit has generally been considered > the older more stable cousin (until Pharo 6 - where it was felt that 64bit > was now just as stable). > > I only mentioned it - because the zeroconf example that has crashed a few > of my several times - was 32 bit (but I have also had 64 bit crash too. > Probably a good experiment to try zeroconf with the 64bit variation and > load my baseline as well). > > I just think we might have an easily reproducable (and small) example that > shows this issue that many have experienced a bit more randomly. > >

Feb. 16, 2019

Re: [Pharo-users] Streams for FileReference in Pharo 7

by Sven Van Caekenberghe

> On 16 Feb 2019, at 14:35, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Sven & Jan, > > On Fri, 15 Feb 2019 at 10:25, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi Jan, >> >> I like #<< too, but I think your assumption that it can print anything on a stream is generally wrong, dangerous and unreliable. >> >> IMHO, you better stick to #print: in that case. >> >> Consider the follow, that all fail: >> >> String streamContents: [ :s | s << 'hello' << 42.5 << $! ]. >> >> String streamContents: [ :s | s << 'hello' << (1@2) << $! ]. >> >> In other words: #<< works in bizar ways (check the implementors of #putOn:). >> >> I would be inclined to change >> >> ZnEncodedStream>>#<< collection >> ^ self nextPutAll: collection >> >> to >> >> ZnEncodedStream>>#<< collection >> ^ self nextPutAll: collection asString >> >> but it would technically not be the same as the original #<< for in-memory streams. >> >> Opinions ? > > I've often thought that this change would be nice to have. #putOn: > doesn't really fit in with writing to text streams (text in the loose > sense of "something that will be read"). > > I think an argument could be made that #printString or #displayString > should be used, but they both have their own issues in practice. > So... > > +1 to "collection asString". > > Cheers, > Alistair I have been thinking a bit more about this, and I have a lot of problems with Integer>>#putOn: aStream aStream isBinary ifTrue: [ self asByteArray do: [ :each | aStream nextPut: each ] ] ifFalse: [ self asString putOn: aStream ] I think we should simply remove this method. It is ugly and wrong. #<< should simply be a shortcut for either #nextPut: and #nextPutAll: and nothing more. The following two are OK for me: String streamContents: [ :out | out << 'Hello' << $! ]. ByteArray streamContents: [ :out | out << #[ 1 2 3 ] << 4 ]. But the following most definitively not: (ByteArray streamContents: [ :out | out << 16rFF << 16rFF11 << 16rFFFF22 << 16rFFFFFF33 ]) hex. When you write out an integer, you have to decide its size, that can never depend on the magnitude (because there is no way to read this back unless there is additional bracketing). Also, printing to a stream should be (very) efficient. Making copies of objects just for conversion purposes should be avoided. I think that if we remove Integer>>#putOn: I could live with ZnEncodedStream>>#<< anObject anObject putOn: self The other solution is to define #<< as strictly the same as #nextPutAll: and remove all #putOn: implementors. Sven

Feb. 16, 2019

Re: [Pharo-users] Streams for FileReference in Pharo 7

by Alistair Grant

Hi Sven & Jan, On Fri, 15 Feb 2019 at 10:25, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Jan, > > I like #<< too, but I think your assumption that it can print anything on a stream is generally wrong, dangerous and unreliable. > > IMHO, you better stick to #print: in that case. > > Consider the follow, that all fail: > > String streamContents: [ :s | s << 'hello' << 42.5 << $! ]. > > String streamContents: [ :s | s << 'hello' << (1@2) << $! ]. > > In other words: #<< works in bizar ways (check the implementors of #putOn:). > > I would be inclined to change > > ZnEncodedStream>>#<< collection > ^ self nextPutAll: collection > > to > > ZnEncodedStream>>#<< collection > ^ self nextPutAll: collection asString > > but it would technically not be the same as the original #<< for in-memory streams. > > Opinions ? I've often thought that this change would be nice to have. #putOn: doesn't really fit in with writing to text streams (text in the loose sense of "something that will be read"). I think an argument could be made that #printString or #displayString should be used, but they both have their own issues in practice. So... +1 to "collection asString". Cheers, Alistair

Feb. 16, 2019

Re: [Pharo-users] How do I find the RPackageTag of a class?

by Denis Kudriashov

Hi Tim. aPackage classTagForClass: aClass Calypso shows more kind of children than just a package tags. And it can be extended. That's the reason why you don't have raw packageTag there. Also in Pharo 6 new API was introduced to handle tags of classes and methods in similar way https://pharo.manuscript.com/f/cases/19341/New-class-and-method-tags-API. ÑÑ, 14 ÑÐµÐ²Ñ. 2019 Ð³. Ð² 13:40, Tim Mackinnon <tim(a)testit.works>: > Actually - Iâve realised that Calypso can give me the tag name from its > context - (aToolContext lastSelectedClassGroup). > > However it does highlight a very strange package/tag design. Are you not > supposed to be easily able to derive RPacakgeTags? > > Tim > > > On 14 Feb 2019, at 13:19, Tim Mackinnon <tim(a)testit.works> wrote: > > > > Iâm trying to understand how RPackage and RPackageTag work in Pharo7? It > seems different than Pharo6 at least with Nautilus (vs Calypso) - as > previously the Nautilus UI gave me the RPacakgeTag, and I could just work > with that. Calypso doesnât seem to give me the tag object, but if I have a > known class and I want to know its RPackageTag I canât see how you do it? > It all seems rather messyâ¦. > > > > I can ask a class for its category - which just gives me a symbol of the > form âmypackage-tagnameâ, and if I ask a class for its package, it will > give me an RPackage(myPackage) - but that RPackage has a set of > RPackageTags which just use the tagname (so not prefixed with > "mypackage-â)? So am I really supposed to split the category name on â-â > myself, and then select the correct RPackageTag? > > > > If I look at the RPackageTag tests - they all seem to use hard coded > values and so donât really show you how you deal with the question above? > > > > It really seems quite messy? > > > > I naively thought that if I wanted a browser extension to deal with a > selected package tag - and file out some classes in that tag (for exercism) > - I could easily get the RPackageTag from any class and then use it? > > > > Tim > > >

Feb. 16, 2019

Pharo 7.0 image size

by Trussardi Dario Romano

Ciao, i have a Pharo 7.0 alpha build 1262. I development a Seaside application. The size of the image keeps increasing, without an apparent reason. Starting from 94 MB, now after rebooting and save the image the relative size is 252 MB. How can I understand what is happening? How can I analyze the data to understand who is occupying more and more space? The other day the system generated a warning that in practice said that there was no more space and that image had to be started with a particular value. Some considerations ? Thanks, Dario

Feb. 16, 2019

Re: [Pharo-users] Stability of Pharo 7 vs 6?

by Tim Mackinnon

Iâve actually being using both - but 32bit has generally been considered the older more stable cousin (until Pharo 6 - where it was felt that 64bit was now just as stable). I only mentioned it - because the zeroconf example that has crashed a few of my several times - was 32 bit (but I have also had 64 bit crash too. Probably a good experiment to try zeroconf with the 64bit variation and load my baseline as well). I just think we might have an easily reproducable (and small) example that shows this issue that many have experienced a bit more randomly. Tim > On 16 Feb 2019, at 11:17, Hilaire <hilaire(a)drgeo.eu> wrote: > > I can't tell, but in your initial email you mentionned using the 64bits > VM, so the image is 64bits too. > > So if you are using 32bits, you can try 64bitsVM https://get.pharo.org/64/ > > Le 16/02/2019 Ã 12:01, Tim Mackinnon a Ã©crit : >> As mentioned, Iâm on OSX HighSierra I get a zero conf image (which I >> believe is the 32 bit version?) >> > -- > Dr. Geo > http://drgeo.eu > > >

Feb. 16, 2019

Re: [Pharo-users] im using pharo 7 with linux env. but cannot input korean.

by Hilaire

Thanks, I will test with my friend -- Dr. Geo http://drgeo.eu

Feb. 16, 2019

Re: [Pharo-users] Stability of Pharo 7 vs 6?

by Hilaire

I can't tell, but in your initial email you mentionned using the 64bits VM, so the image is 64bits too. So if you are using 32bits, you can try 64bitsVM https://get.pharo.org/64/ Le 16/02/2019 Ã 12:01, Tim Mackinnon a Ã©critÂ : > As mentioned, Iâm on OSX HighSierra I get a zero conf image (which I > believe is the 32 bit version?) > -- Dr. Geo http://drgeo.eu

Feb. 16, 2019

Re: [Pharo-users] Stability of Pharo 7 vs 6?

by Tim Mackinnon

So the zeroconf image I launched yesterday morning crashed at 10:30pm last night. So I will try leaving the same image open again but not full screen (and see if thats the difference). But this is honestly a trivial example, and Iâm surprised it crashes so easily (5 or 6 times, so every day this week) - As mentioned, Iâm on OSX HighSierra I get a zero conf image (which I believe is the 32 bit version?) curl https://get.pharo.org | bash Then I run: ./pharo-ui Pharo.image eval " Metacello new baseline: 'Exercism'; repository: 'github://macta/pharo-exercism:master/dev/src'; load. ExercismManager welcome. " This loads a pretty small baseline along with 25ish classes that make up the Exercism project: setUpDependencies: spec spec configuration: 'OSProcess' with: [ spec className: #ConfigurationOfOSProcess; versionString: #'stable'; repository: 'http://www.squeaksource.com/OSProcess' ]. spec baseline: 'ExternalWebBrowser' with: [ spec repository: 'github://seandenigris/Pharo-Web-Browser:master/repository' ]; import: 'ExternalWebBrowser'. I then run a few tests, and use exercism to retrieve a few exercises (via http). Then I do a bit of TDD with the debugger to solve 1 or 2 exercises (but trivial, like reverse-string). And then I leave my image open and close my laptop. This is nothing that I havenât done in Pharo 6 hundreds of time. For the record - The console reports (and the apple diagnostic is below that) CurrentExecutionEnvironment class>>runTestCase: TwoFerTest(TestCase)>>runCaseManaged [ aTestCase announce: TestCaseStarted withResult: self. aTestCase runCaseManaged. aTestCase announce: TestCaseEnded withResult: self. "To not affect performance of big test suites following logic is not inside addPass: method" errors remove: aTestCase ifAbsent: [ ]. failures remove: aTestCase ifAbsent: [ ]. self addPass: aTestCase ] in TestResult>>runCaseForDebug: in Block: [ aTestCase announce: TestCaseStarted withResult: ...etc... BlockClosure>>on:do: TestResult>>runCaseForDebug: [ result runCaseForDebug: self ] in TwoFerTest(TestCase)>>debug in Block: [ result runCaseForDebug: self ] BlockClosure>>ensure: TwoFerTest(TestCase)>>debug Pharo(85584,0xa983a1c0) malloc: *** mach_vm_map(size=8388608) failed (error code=3) *** error: can't allocate region securely *** set a breakpoint in malloc_error_break to debug Segmentation fault Fri Feb 15 22:34:53 2019 VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git C stack backtrace & registers: eax 0x00000000 ebx 0xfd159000 ecx 0x00000000 edx 0xfd159000 edi 0xfd159000 esi 0xfd159000 ebp 0xbff51c58 esp 0xbff51c50 eip 0xa67905d7 0 libobjc.A.dylib 0xa67905d7 _ZN12_GLOBAL__N_119AutoreleasePoolPageC1EPS0_ + 9 1 Pharo 0x00124cf3 reportStackState + 770 2 Pharo 0x001250b1 sigsegv + 213 3 libsystem_platform.dylib 0xa757102b _sigtramp + 43 4 ??? 0xffffffff 0x0 + 4294967295 5 libobjc.A.dylib 0xa67933f2 _ZN12_GLOBAL__N_119AutoreleasePoolPage19autoreleaseFullPageEP11objc_objectPS0_ + 56 6 libobjc.A.dylib 0xa6791495 _ZN11objc_object16rootAutorelease2Ev + 79 7 AppKit 0x91aed8cb -[NSApplication(NSEvent) _setCurrentEvent:] + 63 8 AppKit 0x91aed15a -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3577 9 AppKit 0x91aec359 -[NSApplication(NSEvent) nextEventMatchingMask:untilDate:inMode:dequeue:] + 134 10 Pharo 0x001191f8 -[sqSqueakOSXApplication(events) pumpRunLoopEventSendAndSignal:] + 332 11 Pharo 0x0011929f -[sqSqueakOSXApplication(events) pumpRunLoop] + 67 12 Pharo 0x00123770 vmIOProcessEvents + 190 13 Pharo 0x001237d7 ioProcessEvents + 57 14 Pharo 0x000b6726 checkForEventsMayContextSwitch + 866 15 Pharo 0x000b7e51 ceCheckForInterrupts + 16 16 ??? 0x0375f1cb 0x0 + 58061259 17 Pharo 0x000a7189 interpret + 757 18 Pharo 0x0012618c -[sqSqueakMainApplication runSqueak] + 439 19 Foundation 0x95214299 __NSFirePerformWithOrder + 432 20 CoreFoundation 0x937994b6 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 22 21 CoreFoundation 0x937993d2 __CFRunLoopDoObservers + 498 22 CoreFoundation 0x9377c81d __CFRunLoopRun + 1661 23 CoreFoundation 0x9377be71 CFRunLoopRunSpecific + 641 24 CoreFoundation 0x9377bbda CFRunLoopRunInMode + 122 25 HIToolbox 0x92d7937b RunCurrentEventLoopInMode + 321 26 HIToolbox 0x92d78f5f ReceiveNextEventCommon + 454 27 HIToolbox 0x92d78d7b _BlockUntilNextEventMatchingListInModeWithFilter + 71 28 AppKit 0x9137ab2d _DPSNextEvent + 2101 29 AppKit 0x91aece8c -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 2859 30 AppKit 0x91aec359 -[NSApplication(NSEvent) nextEventMatchingMask:untilDate:inMode:dequeue:] + 134 31 AppKit 0x9136fa7d -[NSApplication run] + 763 32 AppKit 0x91341b3a NSApplicationMain + 1228 33 libdyld.dylib 0xa7268611 start + 1 Smalltalk stack dump: 0xbff57ed0 M ProcessorScheduler class>idleProcess 0x4473c98: a(n) ProcessorScheduler class 0x6e68f18 s [] in ProcessorScheduler class>startUp 0x6947bc8 s [] in BlockClosure>newProcess Most recent primitives tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: **StackOverflow** **StackOverflow** **StackOverflow** tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: **StackOverflow** tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: **StackOverflow** **StackOverflow** tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: **StackOverflow** tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: **StackOverflow** tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: **StackOverflow** tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: **StackOverflow** tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: **StackOverflow** **StackOverflow** tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: tempAt: tempAt:put: tempAt: terminateTo: findNextUnwindContextUpTo: terminateTo: millisecondClockValue yield millisecondClockValue wait signal signal nowTick + nowTick >= nowTick + < primSignal:atUTCMicroseconds: wait wait relinquishProcessorForMicroseconds: stack page bytes 4096 available headroom 2788 minimum unused headroom 2072 (Segmentation fault) ./pharo-ui: line 11: 85584 Abort trap: 6 "$DIR"/"pharo-vm/Pharo.app/Contents/MacOS/Pharo" "$@â apple diagnostic reports: Process: Pharo [85584] Path: /Users/USER/*/Pharo.app/Contents/MacOS/Pharo Identifier: org.pharo.Pharo Version: 5.0.201901051900 (5.0.201901051900) Code Type: X86 (Native) Parent Process: ??? [85580] Responsible: Pharo [85584] User ID: 501 Date/Time: 2019-02-15 22:34:53.892 +0000 OS Version: Mac OS X 10.13.5 (17F77) Report Version: 12 Anonymous UUID: 262197AA-D8D7-1768-420F-0B635BF5C77D Sleep/Wake UUID: 229479AF-3866-4F5C-954B-280CC41FBBCE Time Awake Since Boot: 1000000 seconds Time Since Wake: 2000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGABRT) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY VM Regions Near 0: --> __TEXT 00000000000a5000-0000000000176000 [ 836K] r-x/rwx SM=COW ] [/Users/macta/Dev/Exercism/pharo7e1/pharo-vm/Pharo.app/Contents/MacOS/Pharo] Application Specific Information: abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0xa73c3eda __pthread_kill + 10 1 libsystem_pthread.dylib 0xa757c427 pthread_kill + 363 2 libsystem_c.dylib 0xa7312956 abort + 133 3 org.pharo.Pharo 0x001250bf sigsegv + 227 4 libsystem_platform.dylib 0xa757102b _sigtramp + 43 5 ??? 0xffffffff 0 + 4294967295 6 org.pharo.Pharo 0x00124fdc getCrashDumpFilenameInto + 82 7 libobjc.A.dylib 0xa67933f2 (anonymous namespace)::AutoreleasePoolPage::autoreleaseFullPage(objc_object*, (anonymous namespace)::AutoreleasePoolPage*) + 56 8 libobjc.A.dylib 0xa6791495 objc_object::rootAutorelease2() + 79 9 com.apple.AppKit 0x91aed8cb -[NSApplication(NSEvent) _setCurrentEvent:] + 63 10 com.apple.AppKit 0x91aed15a -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3577 11 com.apple.AppKit 0x91aec359 -[NSApplication(NSEvent) nextEventMatchingMask:untilDate:inMode:dequeue:] + 134 12 org.pharo.Pharo 0x001191f8 -[sqSqueakOSXApplication(events) pumpRunLoopEventSendAndSignal:] + 332 13 org.pharo.Pharo 0x0011929f -[sqSqueakOSXApplication(events) pumpRunLoop] + 67 14 org.pharo.Pharo 0x00123770 vmIOProcessEvents + 190 15 org.pharo.Pharo 0x001237d7 ioProcessEvents + 57 16 org.pharo.Pharo 0x000b6726 checkForEventsMayContextSwitch + 866 17 org.pharo.Pharo 0x000b7e51 ceCheckForInterrupts + 16 18 ??? 0x0375f1cb 0 + 58061259 19 org.pharo.Pharo 0x000a7189 interpret + 757 20 org.pharo.Pharo 0x0012618c -[sqSqueakMainApplication runSqueak] + 439 21 com.apple.Foundation 0x95214299 __NSFirePerformWithOrder + 432 22 com.apple.CoreFoundation 0x937994b6 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 22 23 com.apple.CoreFoundation 0x937993d2 __CFRunLoopDoObservers + 498 24 com.apple.CoreFoundation 0x9377c81d __CFRunLoopRun + 1661 25 com.apple.CoreFoundation 0x9377be71 CFRunLoopRunSpecific + 641 26 com.apple.CoreFoundation 0x9377bbda CFRunLoopRunInMode + 122 27 com.apple.HIToolbox 0x92d7937b RunCurrentEventLoopInMode + 321 28 com.apple.HIToolbox 0x92d78f5f ReceiveNextEventCommon + 454 29 com.apple.HIToolbox 0x92d78d7b _BlockUntilNextEventMatchingListInModeWithFilter + 71 30 com.apple.AppKit 0x9137ab2d _DPSNextEvent + 2101 31 com.apple.AppKit 0x91aece8c -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 2859 32 com.apple.AppKit 0x91aec359 -[NSApplication(NSEvent) nextEventMatchingMask:untilDate:inMode:dequeue:] + 134 33 com.apple.AppKit 0x9136fa7d -[NSApplication run] + 763 34 com.apple.AppKit 0x91341b3a NSApplicationMain + 1228 35 libdyld.dylib 0xa7268611 start + 1 Thread 1:: com.apple.coreaudio.AQClient 0 libsystem_kernel.dylib 0xa73ba422 mach_msg_trap + 10 1 libsystem_kernel.dylib 0xa73b9acf mach_msg + 159 2 com.apple.CoreFoundation 0x9377da88 __CFRunLoopServiceMachPort + 296 3 com.apple.CoreFoundation 0x9377ca76 __CFRunLoopRun + 2262 4 com.apple.CoreFoundation 0x9377be71 CFRunLoopRunSpecific + 641 5 com.apple.CoreFoundation 0x9377bbda CFRunLoopRunInMode + 122 6 com.apple.audio.toolbox.AudioToolbox 0x9263c084 GenericRunLoopThread::Entry(void*) + 138 7 com.apple.audio.toolbox.AudioToolbox 0x9263bfba CAPThread::Entry(CAPThread*) + 94 8 libsystem_pthread.dylib 0xa75794d5 _pthread_body + 347 9 libsystem_pthread.dylib 0xa757937a _pthread_start + 357 10 libsystem_pthread.dylib 0xa7578a56 thread_start + 34 Thread 2: 0 libsystem_kernel.dylib 0xa73c4152 __semwait_signal + 10 1 libsystem_c.dylib 0xa732fdb7 nanosleep$UNIX2003 + 189 2 org.pharo.Pharo 0x00127f30 beatStateMachine + 106 3 libsystem_pthread.dylib 0xa75794d5 _pthread_body + 347 4 libsystem_pthread.dylib 0xa757937a _pthread_start + 357 5 libsystem_pthread.dylib 0xa7578a56 thread_start + 34 Thread 3:: com.apple.NSEventThread 0 libsystem_kernel.dylib 0xa73ba422 mach_msg_trap + 10 1 libsystem_kernel.dylib 0xa73b9a5f mach_msg + 47 2 com.apple.CoreFoundation 0x9377da88 __CFRunLoopServiceMachPort + 296 3 com.apple.CoreFoundation 0x9377ca76 __CFRunLoopRun + 2262 4 com.apple.CoreFoundation 0x9377be71 CFRunLoopRunSpecific + 641 5 com.apple.CoreFoundation 0x9377bbda CFRunLoopRunInMode + 122 6 com.apple.AppKit 0x914aa57c _NSEventThread + 165 7 libsystem_pthread.dylib 0xa75794d5 _pthread_body + 347 8 libsystem_pthread.dylib 0xa757937a _pthread_start + 357 9 libsystem_pthread.dylib 0xa7578a56 thread_start + 34 Thread 4: 0 libsystem_kernel.dylib 0xa73c471a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0xa7578e64 _pthread_wqthread + 1035 2 libsystem_pthread.dylib 0xa7578a32 start_wqthread + 34 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00000000 ebx: 0xa983a1c0 ecx: 0xbff513cc edx: 0x00000000 edi: 0xa757c2ca esi: 0x0000002d ebp: 0xbff513f8 esp: 0xbff513cc ss: 0x00000023 efl: 0x00000206 eip: 0xa73c3eda cs: 0x0000000b ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f cr2: 0x7d45f004 Logical CPU: 0 Error Code: 0x00080148 Trap Number: 132 Binary Images: 0xa5000 - 0x175ff7 +org.pharo.Pharo (5.0.201901051900 - 5.0.201901051900) <91D8A7F9-5FC3-3EB7-8198-D18F6262AF2A> /Users/USER/*/Pharo.app/Contents/MacOS/Pharo 0x28a000 - 0x2d005f dyld (551.3) <AEE46C03-FE99-3D3F-9A28-119D4A885857> /usr/lib/dyld 0x260b000 - 0x260ffff com.apple.audio.AppleHDAHALPlugIn (281.52 - 281.52) <943990E2-9A7B-3078-845B-9D0153680DB4> /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn 0x2615000 - 0x2616fff +libLocalePlugin.dylib (0) <26B928B3-B609-3924-8B88-0355CB1B91A9> /Users/USER/*/Pharo.app/Contents/MacOS/Plugins/libLocalePlugin.dylib 0x2738000 - 0x28f6ff3 com.apple.audio.units.Components (1.14 - 1.14) <1D9A7479-0C4A-3368-A63C-D42A5DAD714F> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio 0x2a28000 - 0x2a28fff +libSurfacePlugin.dylib (0) <818104D7-071E-31DC-B2C6-158647AB76FC> /Users/USER/*/Pharo.app/Contents/MacOS/Plugins/libSurfacePlugin.dylib 0x80a2000 - 0x80a2fff +libClipboardExtendedPlugin.dylib (0) <3AC80DFD-F452-3B75-A405-B30587D14254> /Users/USER/*/Pharo.app/Contents/MacOS/Plugins/libClipboardExtendedPlugin.dylib 0x80a8000 - 0x80aaff3 +libSqueakSSL.dylib (0) <8A426718-013D-3FED-ACAF-EE4CF8780488> /Users/USER/*/Pharo.app/Contents/MacOS/Plugins/libSqueakSSL.dylib 0x833e000 - 0x8888fff com.apple.driver.AppleIntelBDWGraphicsGLDriver (10.34.27 - 10.3.4) <3A8B322A-03DB-32E4-B61C-D8A7BEEB65B7> /System/Library/Extensions/AppleIntelBDWGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelBDWGraphicsGLDriver 0x96d7000 - 0x979cff7 +libfreetype.dylib (0) <D81AD667-A12B-316D-A8D3-0765404C85D3> /Users/USER/*/Pharo.app/Contents/MacOS/Plugins/libfreetype.dylib 0x97bb000 - 0x98f1ffb +libgit2.dylib (0) <11C18863-E2BB-3009-A037-708521D8371B> /Users/USER/*/Pharo.app/Contents/MacOS/Plugins/libgit2.dylib 0x9978000 - 0x99bdffb +libssl.1.0.0.dylib (0) <0A56F172-FA67-3840-ABB7-56FE5532C694> /Users/USER/*/Pharo.app/Contents/MacOS/Plugins/libssl.1.0.0.dylib 0x99d8000 - 0x9a0dfff +libssh2.1.dylib (0) <7737B8F7-3D13-39F8-9BF0-FE64A2E4AF12> /Users/USER/*/Pharo.app/Contents/MacOS/Plugins/libssh2.1.dylib 0xb9f3000 - 0xbb2dfe7 +libcrypto.1.0.0.dylib (0) <B8A5E463-33B2-3400-8AB6-C2B5135778AF> /Users/USER/*/Pharo.app/Contents/MacOS/Plugins/libcrypto.1.0.0.dylib 0xc33b000 - 0xc6a6ff7 com.apple.RawCamera.bundle (8.04.0 - 1017.3.7) <77CE2AAF-C0AF-3006-B472-C0887E1BB9A8> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera 0x9029f000 - 0x9029ffff com.apple.Accelerate (1.11 - Accelerate 1.11) <4FE55EFA-2AAB-3639-8340-CB00CC245170> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate 0x902a0000 - 0x902b6ff7 libCGInterfaces.dylib (417.2) <A85F54BA-AE25-3B4D-8958-9B62C65C3891> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib 0x902b7000 - 0x909f8fdf com.apple.vImage (8.1 - ???) <7BA2CB00-F6B3-3798-9CED-D0C3BB3E5231> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage 0x909f9000 - 0x90b33ff7 libBLAS.dylib (1211.50.2) <056DFB80-2D9C-39BA-8953-EB264FDFDEAA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib 0x90b34000 - 0x90b61ffb libBNNS.dylib (38.1) <B9685933-6EBE-3123-9CA2-CD7963241A22> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib 0x90b62000 - 0x90ed5fff libLAPACK.dylib (1211.50.2) <88232E9D-AD52-3E4F-8ACE-C2468400B626> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib 0x90ed6000 - 0x90eecffb libLinearAlgebra.dylib (1211.50.2) <E9BB8A56-3AB9-33F5-91B5-079F5BAF78E9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib 0x90eed000 - 0x90f06ff7 libSparseBLAS.dylib (1211.50.2) <43DB3D39-727E-3C75-9286-11045DEFC21D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib 0x90f07000 - 0x91066fc7 libvDSP.dylib (622.50.5) <A10E62DA-511A-35C0-9EC2-6B22D56494E5> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib 0x91067000 - 0x91147ffb libvMisc.dylib (622.50.5) <5969D356-9DDA-33FB-B9E8-6BD5E1C4EB05> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib 0x91148000 - 0x91148fff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <D3929A06-59EB-3DCA-89B1-5F44817DBC93> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib 0x9133c000 - 0x920feffb com.apple.AppKit (6.9 - 1561.40.112) <2BA80E54-46C2-3FFA-9631-F845F40A8F81> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit 0x92150000 - 0x92150fff com.apple.ApplicationServices (48 - 50) <28B28337-CFEA-3688-9C35-9EE64A1CA6CB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices 0x92151000 - 0x921b7ff3 com.apple.ApplicationServices.ATS (377 - 445.4) <65D4E2E8-5B98-3666-863D-4DE452311550> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS 0x921ba000 - 0x922deff3 libFontParser.dylib (222.1.6) <486BD2ED-E834-31DB-8522-D6B255D6CC58> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib 0x922df000 - 0x9232bff3 libFontRegistry.dylib (221.3) <65513B66-D028-32B6-81CB-075161A419DE> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib 0x9237a000 - 0x923adff3 libTrueTypeScaler.dylib (222.1.6) <185D1DD1-5764-33FD-BCA6-A651934956FB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib 0x92419000 - 0x9241efff com.apple.ColorSyncLegacy (4.13.0 - 1) <987F0D58-C5CD-3C1F-A88B-DBDE4C3E73D8> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy 0x924c8000 - 0x92520fff com.apple.HIServices (1.22 - 624.1) <3D8C7044-D149-325D-B55E-09BC57665193> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices 0x92521000 - 0x92530ff7 com.apple.LangAnalysis (1.7.0 - 1.7.0) <92601EB8-3F73-3BBF-B3B6-0C7D47D819A9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis 0x92531000 - 0x92589ffb com.apple.print.framework.PrintCore (13.4 - 503.2) <E28CF09A-9AEC-3D70-AF27-F428332FEB74> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore 0x9258a000 - 0x92620ff7 com.apple.QD (3.12 - 404.2) <113D0ECA-A6B2-39A7-AE1E-CAE7B40A3CAF> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD 0x92621000 - 0x9262dff3 com.apple.speech.synthesis.framework (7.5.1 - 7.5.1) <7CDC3350-95F1-34C1-8B4F-9B31368BEEB0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis 0x9262e000 - 0x9287cffb com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <92F5F62A-4707-35D3-BF73-88239ED7F79C> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox 0x9287e000 - 0x9287efff com.apple.audio.units.AudioUnit (1.14 - 1.14) <24D68C49-15B8-31B8-A3BB-CAD584CD2CAC> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit 0x929b6000 - 0x92d2bfff com.apple.CFNetwork (901.1 - 901.1) <F957C597-9C0F-3884-B9A2-0CAAF17FCE64> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork 0x92d41000 - 0x92d4aff3 com.apple.audio.SoundManager (4.2 - 4.2) <FA75FD1F-2FEE-3E25-A160-AF78044082BE> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/Versions/A/CarbonSound 0x92d50000 - 0x930e6ff7 com.apple.HIToolbox (2.1.1 - 911.10) <9D42DFC7-DB53-352C-BAD3-3C5CD23EF53D> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox 0x93146000 - 0x931e0ffb com.apple.ink.framework (10.9 - 221) <68D3D209-BCB1-3750-8632-C12DE8F250B1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink 0x931e1000 - 0x9321bfff com.apple.NavigationServices (3.8 - 227) <AD26CCEE-6468-317F-9540-EEE95A6E0990> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServices.framework/Versions/A/NavigationServices 0x9323e000 - 0x93240fff com.apple.securityhi (9.0 - 55006) <15724ACD-75A1-3CEF-8A53-3BE31CD0CEB6> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI 0x93241000 - 0x93247fff com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <03DE054B-239F-3D6F-BBED-98FE8EC6A3C0> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition 0x93248000 - 0x93248fff com.apple.Cocoa (6.11 - 22) <8419F291-2B0B-322A-91CE-DBCD8082C778> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa 0x93255000 - 0x93314ff3 com.apple.ColorSync (4.13.0 - 3325) <C28DA8B8-868E-3BF8-A327-904DC9348FA6> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync 0x93315000 - 0x933b0fff com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <B665144E-6421-39FD-9DFA-E1B2BB96CD34> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio 0x9340e000 - 0x93413fff com.apple.CoreBluetooth (1.0 - 1) <D8E00284-8021-3A90-8379-CF161DA6078B> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth 0x93414000 - 0x936f6ff7 com.apple.CoreData (120 - 851) <FCC5890C-147F-3A85-92D1-751C3E33F96A> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData 0x936f7000 - 0x936fdff3 com.apple.CoreDisplay (1.0 - 97.21) <3C9F1E4B-0BEB-3BBC-81D1-3F90F54211DF> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay 0x936fe000 - 0x93b88ff7 com.apple.CoreFoundation (6.9 - 1452.23) <17321B27-67AB-3D26-B9DF-A69624B1C82B> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x93b8a000 - 0x941bdff3 com.apple.CoreGraphics (2.0 - 1161.21) <909796EA-77A5-3584-AE65-48B11952DBBC> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics 0x941bf000 - 0x94435ffb com.apple.CoreImage (13.0.0 - 579.5) <3ABBFE1A-2E03-31E5-98E8-4E3D5D6D1FB4> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage 0x944f2000 - 0x945e9ff7 com.apple.CoreMedia (1.0 - 2276.50) <0BF2ADE6-51A4-3AAC-B247-0E6629669ABA> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia 0x9463d000 - 0x9463dfff com.apple.CoreServices (822.33 - 822.33) <DAD579FC-6A21-3989-B014-C3CE888E5E5E> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices 0x9463e000 - 0x946b0ff3 com.apple.AE (735.1 - 735.1) <72876D21-3967-3CBE-9006-3E33FEFA6505> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE 0x946b1000 - 0x9498fff7 com.apple.CoreServices.CarbonCore (1178.4 - 1178.4) <3BC3590D-F528-39EE-8D6B-13526E5CE810> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore 0x94990000 - 0x949c4ffb com.apple.DictionaryServices (1.2 - 284.2) <351D5B30-AC6C-3BCC-AE26-632AE228BBAC> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices 0x949c5000 - 0x949cdfff com.apple.CoreServices.FSEvents (1239.50.1 - 1239.50.1) <C0631AEA-6D41-3BA5-B5D0-4ACD95234303> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents 0x949ce000 - 0x94b2dff7 com.apple.LaunchServices (822.32 - 822.32) <F6BFB16B-D6B3-3730-94C0-9490B2C63371> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices 0x94b2e000 - 0x94bdbfff com.apple.Metadata (10.7.0 - 1191.4.13) <95F0D9F8-315B-364C-AC92-A750D8CE3CD4> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata 0x94bdc000 - 0x94c3dfff com.apple.CoreServices.OSServices (822.33 - 822.33) <897A8A5A-8A70-340D-A041-057957F321D6> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices 0x94c3e000 - 0x94caffff com.apple.SearchKit (1.4.0 - 1.4.0) <B3E3985C-7739-3815-8A89-477F975C2029> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit 0x94cb0000 - 0x94cd3fff com.apple.coreservices.SharedFileList (71.21 - 71.21) <8B10F426-0DF3-3FCE-B5DB-F3860BAA860F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList 0x94cd4000 - 0x94e20ffb com.apple.CoreText (352.0 - 578.18) <CF0AF654-0DDD-3FA3-BE0E-FBB90D45BE83> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText 0x94e21000 - 0x94e5bffb com.apple.CoreVideo (1.8 - 0.0) <4B4E52AC-7BBA-375E-9D86-1DD096410604> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo 0x94e5c000 - 0x94ee3ff3 com.apple.framework.CoreWLAN (13.0 - 1350.1) <68C405BD-8A07-3080-A9F0-938D0A2B49C8> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN 0x95137000 - 0x95140ff7 com.apple.DiskArbitration (2.7 - 2.7) <F866E76D-7FFA-3E93-9A8A-32C3754F1F33> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration 0x95151000 - 0x954c1ffb com.apple.Foundation (6.9 - 1452.23) <9212AB5F-B5FC-37C8-8059-853B006434E1> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation 0x95502000 - 0x95531ff3 com.apple.GSS (4.0 - 2.0) <0BB8D894-20EA-3D83-A79B-654623C674B4> /System/Library/Frameworks/GSS.framework/Versions/A/GSS 0x9555e000 - 0x95676ff3 com.apple.Bluetooth (6.0.6 - 6.0.6f2) <E83F7CF7-7776-3FE6-9B45-8FA27C09EACE> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth 0x956dc000 - 0x9577dff7 com.apple.framework.IOKit (2.0.2 - 1445.60.1) <5289B606-E36C-3DDC-B8D5-2151B1EE2933> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit 0x9577f000 - 0x95786fff com.apple.IOSurface (211.12 - 211.12) <B24705CD-3B67-3D4C-A194-FE817FAFF983> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface 0x957db000 - 0x9595fff7 com.apple.ImageIO.framework (3.3.0 - 1739.3) <EEC26E38-3136-346E-8293-4993854F328C> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO 0x95960000 - 0x95964ffb libGIF.dylib (1739.3) <017E36E0-FB42-303A-9D10-58E082C97BF9> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib 0x95965000 - 0x95a56ff7 libJP2.dylib (1739.3) <2A34D143-026C-3572-9CC1-ED4751B1E2A3> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib 0x95a57000 - 0x95a79ff7 libJPEG.dylib (1739.3) <80C0109B-2D63-331D-B595-01D2A8CDD431> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib 0x95a7a000 - 0x95aa0ff7 libPng.dylib (1739.3) <B2C1476E-296E-3E8A-AD98-C95C192D9329> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib 0x95aa1000 - 0x95aa3ffb libRadiance.dylib (1739.3) <65386E46-F92D-30C6-BA00-33C16C6AD3D7> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib 0x95aa4000 - 0x95aeeff3 libTIFF.dylib (1739.3) <59086815-1D75-36AB-9B74-CD8A00DEEE49> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib 0x964fa000 - 0x96512fff com.apple.Kerberos (3.0 - 1) <BFC5A83F-78BD-3FEC-AF28-CF36927117C6> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos 0x96513000 - 0x96546ffb com.apple.LDAPFramework (2.4.28 - 194.5) <3E612921-B937-3B7E-9636-9FBBF94D1019> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP 0x9656a000 - 0x96572fff com.apple.MediaAccessibility (1.0 - 114) <D6008060-F087-3713-8C1C-86E259D493AF> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility 0x96573000 - 0x96bd1ff7 com.apple.MediaToolbox (1.0 - 2276.50) <458F8EA5-E32C-3CBC-97AB-4CD925136880> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox 0x96bd3000 - 0x96c4bff3 com.apple.Metal (125.25 - 125.25) <C1BFDD6D-6162-355B-9B87-C6F67FA3FC65> /System/Library/Frameworks/Metal.framework/Versions/A/Metal 0x96c4d000 - 0x96c59fff com.apple.NetFS (6.0 - 4.0) <4A9454E1-FF5C-321A-8317-4C120332356A> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS 0x99586000 - 0x9958eff7 libcldcpuengine.dylib (2.8.7) <464D7F18-5876-3751-A7BF-E1289C502B5F> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib 0x9958f000 - 0x995dbfff com.apple.opencl (2.8.15 - 2.8.15) <41D0BAA4-B8AA-3277-A5E4-8256B839C636> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL 0x995dc000 - 0x995f8fff com.apple.CFOpenDirectory (10.13 - 207.50.1) <F183AEDA-CC0A-3B26-B20F-6228D0704724> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory 0x995f9000 - 0x99604fff com.apple.OpenDirectory (10.13 - 207.50.1) <92CD87D2-E933-3A4F-AE00-0304034876E6> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory 0x9a80e000 - 0x9a80ffff libCVMSPluginSupport.dylib (16.5.10) <621A9123-A958-340E-86D0-997C9E1DDB4C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib 0x9a810000 - 0x9a814fff libCoreFSCache.dylib (162.6.1) <FBF63A91-5B45-36FF-9340-D9223DA9A49B> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib 0x9a815000 - 0x9a819fff libCoreVMClient.dylib (162.6.1) <0958F095-D449-343F-9F13-AD82E5D2055A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib 0x9a81a000 - 0x9a823ff7 libGFXShared.dylib (16.5.10) <0C5906D1-B9BB-3C7B-B0D5-DB4EE842978D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib 0x9a824000 - 0x9a830fff libGL.dylib (16.5.10) <85E5F934-C3AE-3E82-B411-0C790FF69773> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib 0x9a831000 - 0x9a86cffb libGLImage.dylib (16.5.10) <F2CE94F0-47FD-35E1-806B-0F29AF0495EC> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib 0x9a86d000 - 0x9a9e5ffb libGLProgrammability.dylib (16.5.10) <283B04BF-52D4-3EBE-A173-23D28E3EEB45> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib 0x9a9e6000 - 0x9aa28ff7 libGLU.dylib (16.5.10) <8CAAAB65-FC03-39C1-8594-BBBFB6B0BD12> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib 0x9b3cf000 - 0x9b3defff com.apple.opengl (16.5.10 - 16.5.10) <F2D5732F-7734-3CE2-ABA3-A8F49C071839> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL 0x9b3df000 - 0x9b56cfff GLEngine (16.5.10) <DF07720E-FEA4-37B4-8BD5-9682CDF6D0BC> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine 0x9b56d000 - 0x9b597fff GLRendererFloat (16.5.10) <39E3D87C-A4E3-3621-83E1-17B05C4E018C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat 0x9c14a000 - 0x9c384ff3 com.apple.QuartzCore (1.11 - 584.52.1) <7DABD878-75F0-3AF2-8E5C-8A92CDD34C9B> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore 0x9c3da000 - 0x9c632ffb com.apple.QuickTime (7.7.3 - 3014.8) <43E74F6E-7BF5-3EE0-BBFC-8399C04A793C> /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime 0x9c818000 - 0x9cb49ff3 com.apple.security (7.0 - 58286.60.28) <282B7924-67E3-3F3B-8FE5-54550DA22447> /System/Library/Frameworks/Security.framework/Versions/A/Security 0x9cb4a000 - 0x9cbd2ffb com.apple.securityfoundation (6.0 - 55185.50.5) <D6375494-880A-30A4-8670-31DA8E789912> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation 0x9cbfe000 - 0x9cc02fff com.apple.xpc.ServiceManagement (1.0 - 1) <43F3C3AA-4C1D-37B7-BA13-D6CB542A3307> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement 0x9cd2d000 - 0x9cd9dff3 com.apple.SystemConfiguration (1.17 - 1.17) <D7C33CE2-30D1-3602-A8D8-B05C8A8C79B3> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration 0x9cf47000 - 0x9d2d6ff7 com.apple.VideoToolbox (1.0 - 2276.50) <F9F8DDCD-FB7C-39B0-AA2B-111138F4800A> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox 0x9ede6000 - 0x9ee85ff7 com.apple.APFS (1.0 - 1) <1C8712C6-0469-3564-BF63-DFCB4E7EAF87> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS 0x9f49b000 - 0x9f4c6ff3 com.apple.framework.Apple80211 (13.0 - 1361.7) <D7355E97-AB0B-3587-82AD-6B9FBFF1C256> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211 0x9f4c8000 - 0x9f4d2fff com.apple.AppleFSCompression (96.60.1 - 1.0) <191C4733-0521-30C8-AB00-54DC56F7E7E5> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression 0x9f5d0000 - 0x9f60dffb com.apple.AppleJPEG (1.0 - 1) <B7271B9B-A441-35F0-9B30-0FA646E981AA> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG 0x9f62c000 - 0x9f634fff com.apple.AppleSRP (5.0 - 1) <0C288A20-01A0-3C3C-8091-B8672B1F0CC6> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP 0x9f707000 - 0x9f756ffb com.apple.AppleVAFramework (5.0.41 - 5.0.41) <02C2E120-F1F7-31E0-8716-43120084A793> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA 0x9f760000 - 0x9f767fff com.apple.coreservices.BackgroundTaskManagement (1.0 - 57.1) <22080179-8A2A-32EF-A66A-5415E05B6EBF> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement 0x9f768000 - 0x9f7f3ff7 com.apple.backup.framework (1.9.5 - 1.9.5) <633E36AC-7AAE-351B-A279-7E217DC6644B> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup 0x9f938000 - 0x9f941ffb com.apple.CommonAuth (4.0 - 2.0) <1096BDDF-4D5D-3C36-8AF6-556CC7F1F66A> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth 0x9f9eb000 - 0x9fd2cfef com.apple.CoreAUC (259.0.0 - 259.0.0) <0F3A5737-EED7-39A9-A06A-4F9F3B9CD1E1> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC 0x9fd2d000 - 0x9fd5efff com.apple.CoreAVCHD (5.9.0 - 5900.4.1) <3DB6ECE9-3F33-3DB9-95F0-4CD85253C21D> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD 0x9fdd3000 - 0x9fddbfff com.apple.frameworks.CoreDaemon (1.3 - 1.3) <DFFFED5D-D7EE-356C-A114-E81A51FA04CC> /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon 0x9fddc000 - 0x9fdecff7 com.apple.CoreEmoji (1.0 - 69.3) <165A133F-DED4-3B24-A9BF-6EA6F3F7A152> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji 0x9ff75000 - 0x9ffa8ff7 com.apple.CoreServicesInternal (309.1 - 309.1) <0C4952C6-785B-3E1F-8588-1C914ADF954D> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal 0x9ffa9000 - 0xa003fff3 com.apple.CoreSymbolication (9.3 - 64026) <7895DF41-EF5D-36AC-BB0E-C3020D87C200> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication 0xa0040000 - 0xa0167ff3 com.apple.coreui (2.1 - 494.1) <91CFA81E-25D5-32AD-AEAE-9AC690F37481> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI 0xa0168000 - 0xa0206ff7 com.apple.CoreUtils (5.6 - 560.11) <FD566F31-AAB0-30A8-B069-BF6AB1E4F647> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils 0xa0257000 - 0xa02b4ff3 com.apple.framework.CoreWiFi (13.0 - 1350.1) <CCED77D5-2751-3EA9-9413-859D2F09B4A4> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi 0xa02b5000 - 0xa02c5ffb com.apple.CrashReporterSupport (10.13 - 1) <EF523AD9-1BE6-3C49-986C-F737910EAAE3> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport 0xa0333000 - 0xa0340fff com.apple.framework.DFRFoundation (1.0 - 191.7) <D6B46C05-938E-39BF-B085-20D25FDEEDF7> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation 0xa038c000 - 0xa03fdfff com.apple.datadetectorscore (7.0 - 590.3) <31B3BFAC-FF9C-3F58-A01B-6A01A28FDEE0> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore 0xa03fe000 - 0xa043effb com.apple.DebugSymbols (181.0 - 181.0) <51B67F42-ACCD-39A3-8739-E223FAEDFF93> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols 0xa043f000 - 0xa057effb com.apple.desktopservices (1.12.5 - 1.12.5) <27DE2928-4DCB-3AA3-B490-ECD108C0F3F5> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv 0xa08be000 - 0xa0ceeff7 com.apple.vision.FaceCore (3.3.2 - 3.3.2) <8B37289B-EB90-32F0-97A6-21566B236CAD> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore 0xa2a8a000 - 0xa2a94fff libGPUSupportMercury.dylib (16.5.10) <DEF9523E-2B09-3C01-9A7B-19B6A5E5B4F7> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib 0xa36a0000 - 0xa3713ff3 com.apple.Heimdal (4.0 - 2.0) <03A4EE80-4E4A-390C-9E2E-0CEC3307496D> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal 0xa39cb000 - 0xa39d2fff com.apple.IOAccelerator (378.18.1 - 378.18.1) <6519F950-374B-35FA-A383-3BABB9354D99> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator 0xa39d3000 - 0xa39ecfff com.apple.IOPresentment (1.0 - 35.1) <46620404-9D01-339D-8EFC-56E09B19C9AA> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment 0xa3a49000 - 0xa3a69ffb com.apple.IconServices (97.6 - 97.6) <C107CE67-BF5F-3AC9-A514-C864310F2BBB> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices 0xa3aa1000 - 0xa3b95fff com.apple.LanguageModeling (1.0 - 159.5.3) <D8038B28-4A97-3E03-8AE6-5D3C3A1CE8F2> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling 0xa3b96000 - 0xa3bd6fff com.apple.Lexicon-framework (1.0 - 33.5) <C8DEE7FC-6CCE-3645-B6C1-CCF5FD07C20C> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon 0xa3bda000 - 0xa3be0ff3 com.apple.LinguisticData (1.0 - 238.3) <16C6495B-D87B-3144-846C-C2C1214900CF> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData 0xa3f5c000 - 0xa3f86fff com.apple.MultitouchSupport.framework (1404.4 - 1404.4) <591C5CFA-F49A-3AA3-9ACB-5076483D6BB0> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport 0xa40a5000 - 0xa40affff com.apple.NetAuth (6.2 - 6.2) <D74A6D47-3D72-3E44-820B-9381D7425B11> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth 0xa4157000 - 0xa4164ffb com.apple.PerformanceAnalysis (1.194 - 194) <761316A9-016F-3C95-A020-CADDC50E4F39> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis 0xa4204000 - 0xa4220ff7 com.apple.ProtocolBuffer (1 - 260) <1EE82E2E-BA9D-33CC-904F-A9467619FB6B> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer 0xa430f000 - 0xa4331fff com.apple.RemoteViewServices (2.0 - 125) <54C07CCF-E480-3033-979D-A7E6BCC6281F> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices 0xa43d9000 - 0xa4406ffb com.apple.Sharing (1050.21 - 1050.21) <09DF5459-E2B7-39C5-9600-474DFD22F131> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing 0xa4425000 - 0xa4426fff com.apple.performance.SignpostNotification (1.2.5 - 2.5) <86B3053F-0169-3663-924F-91186D05151D> /System/Library/PrivateFrameworks/SignpostNotification.framework/Versions/A/SignpostNotification 0xa4427000 - 0xa44adff7 com.apple.SkyLight (1.600.0 - 312.62) <747AEAD4-5F54-3B3C-B92F-54B35F490C3A> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight 0xa44dd000 - 0xa44eaff7 com.apple.SpeechRecognitionCore (4.6.1 - 4.6.1) <750D7D56-1633-3762-9B3A-B342D2AD614D> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore 0xa47ba000 - 0xa4840ffb com.apple.Symbolication (9.3 - 64033) <A6EE4F4A-35E3-303D-8B7C-F84368546DC1> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication 0xa4893000 - 0xa489bfff com.apple.TCC (1.0 - 1) <449D3E94-0C9A-3F2A-835B-593D846F6006> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC 0xa489c000 - 0xa48b3ff3 com.apple.TextureIO (3.7 - 3.7) <9D532312-C024-38CA-B137-A4C88919C5EC> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO 0xa48e0000 - 0xa48e1fff com.apple.TrustEvaluationAgent (2.0 - 31) <185BD5A9-5A2D-3317-B7FE-9B67F14C4D2C> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent 0xa48e2000 - 0xa4a6cfff com.apple.UIFoundation (1.0 - 547.5) <1B6390A9-8D94-3E6D-BDB4-A1E6B39497C4> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation 0xa4e04000 - 0xa4ec8fff com.apple.ViewBridge (343.2 - 343.2) <D34224CE-BF51-3F7E-A714-4FD465ED5670> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge 0xa503b000 - 0xa503dfff com.apple.loginsupport (1.0 - 1) <96644B33-7507-3AE7-BC45-D83934517F37> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport 0xa503e000 - 0xa504ffff com.apple.login (3.0 - 3.0) <CDB5BDAD-934C-390D-A1B6-0EBA73043BCE> /System/Library/PrivateFrameworks/login.framework/Versions/A/login 0xa50c8000 - 0xa50fbff7 libclosured.dylib (551.3) <F357ECA7-469A-3611-8D9C-3267FB90071A> /usr/lib/closure/libclosured.dylib 0xa5157000 - 0xa518eff3 libCRFSuite.dylib (41) <7B102174-C6BA-3EA8-93AC-A53254B79D78> /usr/lib/libCRFSuite.dylib 0xa518f000 - 0xa5199ffb libChineseTokenizer.dylib (28) <00EF6AE9-C195-334C-9776-79E9BD298AF6> /usr/lib/libChineseTokenizer.dylib 0xa5235000 - 0xa5236fff libDiagnosticMessagesClient.dylib (104) <6829B180-2556-3A7E-A2E6-BD4859DF30A7> /usr/lib/libDiagnosticMessagesClient.dylib 0xa5268000 - 0xa5452ff7 libFosl_dynamic.dylib (17.8) <2806AC88-9928-3848-B63E-E3891CD58511> /usr/lib/libFosl_dynamic.dylib 0xa545a000 - 0xa545afff libOpenScriptingUtil.dylib (174) <BD4EA519-A75C-3840-8870-4DE884502F47> /usr/lib/libOpenScriptingUtil.dylib 0xa54ae000 - 0xa54b2fff libScreenReader.dylib (562.18.4) <24F173B6-9EB9-3730-A6CE-D43827265020> /usr/lib/libScreenReader.dylib 0xa54b3000 - 0xa54b4fff libSystem.B.dylib (1252.50.4) <AA5E65F6-81A7-3B9D-A322-C8230EA2DD9E> /usr/lib/libSystem.B.dylib 0xa54c3000 - 0xa54d8ff7 libapple_nghttp2.dylib (1.24) <480C0C04-2533-3D44-8232-006B6CBA7758> /usr/lib/libapple_nghttp2.dylib 0xa54d9000 - 0xa5504fff libarchive.2.dylib (54) <D55C5F86-251D-3C33-A617-0C623D4F512E> /usr/lib/libarchive.2.dylib 0xa5505000 - 0xa5654ffb libate.dylib (1.13.1) <E109CCBF-357D-3C87-9CE5-D53AE03609A2> /usr/lib/libate.dylib 0xa5658000 - 0xa5658ff3 libauto.dylib (187) <CE2A78CC-670F-3E07-9539-822DCD2F6084> /usr/lib/libauto.dylib 0xa5659000 - 0xa5669fff libbsm.0.dylib (39) <6A4D8D43-8AD8-3B0C-A19C-22A77D30DD8E> /usr/lib/libbsm.0.dylib 0xa566a000 - 0xa5676ff7 libbz2.1.0.dylib (38) <77C24A36-BE84-3702-A786-935C597A0A86> /usr/lib/libbz2.1.0.dylib 0xa5677000 - 0xa56d0ffb libc++.1.dylib (400.9) <BA03445F-C2AD-3C30-A25D-3654091142AB> /usr/lib/libc++.1.dylib 0xa56d1000 - 0xa56f2fff libc++abi.dylib (400.8.2) <60422228-2A4A-3A12-AB94-3110E9082D62> /usr/lib/libc++abi.dylib 0xa56f4000 - 0xa5705ff7 libcmph.dylib (6) <EC7664F1-B5A1-37F4-B7DC-F6AC10587E35> /usr/lib/libcmph.dylib 0xa5706000 - 0xa571bff7 libcompression.dylib (47.60.2) <FB4313A1-D9BE-36DD-A8A2-1AC45D0320AD> /usr/lib/libcompression.dylib 0xa571c000 - 0xa5733ffb libcoretls.dylib (155.50.1) <A7FFC69E-B53D-324D-8AE1-C1AC50CEB37F> /usr/lib/libcoretls.dylib 0xa5734000 - 0xa5735fff libcoretls_cfhelpers.dylib (155.50.1) <D210E966-844F-3A00-A17E-7489EE444E36> /usr/lib/libcoretls_cfhelpers.dylib 0xa58b6000 - 0xa5a5dff3 libcrypto.35.dylib (22.50.2) <A658A3FD-A5C4-3DC9-9A45-A2E97282D419> /usr/lib/libcrypto.35.dylib 0xa5c1d000 - 0xa5c74fff libcups.2.dylib (462.2.1) <806D6B01-D043-325B-9EB3-7BC8DD781B8C> /usr/lib/libcups.2.dylib 0xa5ca0000 - 0xa5cf2fff libcurl.4.dylib (105.40.1) <9809E78E-365C-3F94-A230-4933A28558E0> /usr/lib/libcurl.4.dylib 0xa5d8b000 - 0xa5d8bfff libenergytrace.dylib (16) <34FC43C7-D9B6-3C01-8B65-E49059D31279> /usr/lib/libenergytrace.dylib 0xa5dbf000 - 0xa5dc3fff libheimdal-asn1.dylib (520.50.6) <CAA45AC8-3953-38C7-B6C1-E7ACA1607054> /usr/lib/libheimdal-asn1.dylib 0xa5def000 - 0xa5edfff3 libiconv.2.dylib (51.50.1) <F3BF51D6-CFAD-3105-AF32-0667945E0F99> /usr/lib/libiconv.2.dylib 0xa5ee0000 - 0xa6102ff7 libicucore.A.dylib (59180.0.1) <7A26EF2B-5D18-319D-9FF5-72D1142A6059> /usr/lib/libicucore.A.dylib 0xa614a000 - 0xa614bfff liblangid.dylib (128) <120FE992-47E4-3A73-A039-1B401F5696DC> /usr/lib/liblangid.dylib 0xa614c000 - 0xa6164ff7 liblzma.5.dylib (10) <8A5C9679-430A-3A19-AF68-9D21BAC442C7> /usr/lib/liblzma.5.dylib 0xa6165000 - 0xa617afff libmarisa.dylib (9) <805453EE-B829-3DA5-8DF3-5132D03D5B74> /usr/lib/libmarisa.dylib 0xa622f000 - 0xa644cfff libmecabra.dylib (779.7.6) <A6D0BC1B-9DF2-3A26-8E1A-06AE207355E7> /usr/lib/libmecabra.dylib 0xa6613000 - 0xa678aff3 libnetwork.dylib (1229.60.3) <25A51968-46C6-3E05-A005-5D4F6CE01AD2> /usr/lib/libnetwork.dylib 0xa678b000 - 0xa6b6b0fb libobjc.A.dylib (723) <069E8DD2-ECBD-3296-9688-199A93DB8F1F> /usr/lib/libobjc.A.dylib 0xa6b6f000 - 0xa6b72fff libpam.2.dylib (22) <7106F43C-84DD-3F26-905A-B52780AFEB3E> /usr/lib/libpam.2.dylib 0xa6b75000 - 0xa6ba6fff libpcap.A.dylib (79.20.1) <154889CF-5F83-3012-953E-0FC8FEE50FF8> /usr/lib/libpcap.A.dylib 0xa6be4000 - 0xa6bffffb libresolv.9.dylib (65) <65A43F5B-CF88-3948-AE5C-D7CA02D814A1> /usr/lib/libresolv.9.dylib 0xa6c38000 - 0xa6c49ff7 libsasl2.2.dylib (211) <42C44CD3-07F5-3D62-8D63-350AD6FC6A63> /usr/lib/libsasl2.2.dylib 0xa6c4a000 - 0xa6dd4ffb libsqlite3.dylib (274.8.1) <2865CDEE-96C4-3ECC-9F4B-876D0CD27C41> /usr/lib/libsqlite3.dylib 0xa6e2c000 - 0xa6e8affb libssl.35.dylib (22.50.2) <1AAEE15A-D711-3B1B-81A9-3195E6EFB3DE> /usr/lib/libssl.35.dylib 0xa6f78000 - 0xa6fd7fff libusrtcp.dylib (1229.60.3) <39EAD1BC-7817-3C8B-890E-B1619826479D> /usr/lib/libusrtcp.dylib 0xa6fd8000 - 0xa6fdbff7 libutil.dylib (51.20.1) <86BD9675-16A2-345D-9B8D-E8A3397F2365> /usr/lib/libutil.dylib 0xa6fdc000 - 0xa6feaff7 libxar.1.dylib (400) <4B664A7E-EC05-34AD-ACC6-C879B69DBA7C> /usr/lib/libxar.1.dylib 0xa6feb000 - 0xa70c9ff7 libxml2.2.dylib (31.10) <A5264063-CE4F-38CE-B884-197B2765E5AB> /usr/lib/libxml2.2.dylib 0xa70ca000 - 0xa70f2ff3 libxslt.1.dylib (15.12) <2A385CB5-9458-3408-A4F2-1F51553823F4> /usr/lib/libxslt.1.dylib 0xa70f3000 - 0xa7102ff7 libz.1.dylib (70) <588F445F-0065-3D77-8002-BA9411DA1D70> /usr/lib/libz.1.dylib 0xa713d000 - 0xa7141fff libcache.dylib (80) <E9928057-A238-3619-8E30-4D1C21C9493C> /usr/lib/system/libcache.dylib 0xa7142000 - 0xa714cfff libcommonCrypto.dylib (60118.50.1) <95434E97-2B85-3607-9E02-2A8CFD178D23> /usr/lib/system/libcommonCrypto.dylib 0xa714d000 - 0xa7152fff libcompiler_rt.dylib (62) <B9947B1F-9930-385A-A960-856CF6C539CF> /usr/lib/system/libcompiler_rt.dylib 0xa7153000 - 0xa715dff3 libcopyfile.dylib (146.50.5) <6A3EF295-2778-3405-BE11-8947695F4A31> /usr/lib/system/libcopyfile.dylib 0xa715e000 - 0xa71c6ff7 libcorecrypto.dylib (562.50.17) <FCA475BB-944F-3589-A662-D71043482D28> /usr/lib/system/libcorecrypto.dylib 0xa7231000 - 0xa7266fff libdispatch.dylib (913.60.2) <49A9530D-9FB7-38C3-9583-E5F0AAEB3E95> /usr/lib/system/libdispatch.dylib 0xa7267000 - 0xa7284fff libdyld.dylib (551.3) <42AC1F77-75EC-3464-B24D-8E95F72FFE21> /usr/lib/system/libdyld.dylib 0xa7285000 - 0xa7285fff libkeymgr.dylib (28) <35604C10-4B09-3AA0-9694-87D40C15E706> /usr/lib/system/libkeymgr.dylib 0xa7286000 - 0xa7292ff7 libkxld.dylib (4570.61.1) <166C52CE-93C2-3512-923F-542EDC492A4C> /usr/lib/system/libkxld.dylib 0xa7293000 - 0xa7293fff liblaunch.dylib (1205.60.9) <3853D7AE-4A44-3D5A-BD3C-210F04C8D523> /usr/lib/system/liblaunch.dylib 0xa7294000 - 0xa7299fff libmacho.dylib (906) <14070ABC-E6F7-3CD5-9527-56E38D65BC74> /usr/lib/system/libmacho.dylib 0xa729a000 - 0xa729cfff libquarantine.dylib (86) <2660EB51-FA02-36ED-9416-83A4A6849026> /usr/lib/system/libquarantine.dylib 0xa729d000 - 0xa729efff libremovefile.dylib (45) <BE0DA6CE-2EF4-3BE9-84E1-BB27E1F385DD> /usr/lib/system/libremovefile.dylib 0xa729f000 - 0xa72b6ff7 libsystem_asl.dylib (356.50.1) <8C2103F0-0293-3450-A4D5-CDA224D6B1DD> /usr/lib/system/libsystem_asl.dylib 0xa72b7000 - 0xa72b7fff libsystem_blocks.dylib (67) <D45F0CE1-D217-3B46-A84A-F884FE576E04> /usr/lib/system/libsystem_blocks.dylib 0xa72b8000 - 0xa7344ff3 libsystem_c.dylib (1244.50.9) <3A7B32B2-F70C-3148-A2B0-38412EF1489F> /usr/lib/system/libsystem_c.dylib 0xa7345000 - 0xa7348fff libsystem_configuration.dylib (963.50.8) <EBE21758-807D-3038-91A9-F6075353C6A0> /usr/lib/system/libsystem_configuration.dylib 0xa7349000 - 0xa734cfff libsystem_coreservices.dylib (51) <CF4379BC-AEDD-34DF-BFD7-CEA27B0930D5> /usr/lib/system/libsystem_coreservices.dylib 0xa734d000 - 0xa734efff libsystem_darwin.dylib (1244.50.9) <326B9F59-5784-3C79-8A44-7C40D662C695> /usr/lib/system/libsystem_darwin.dylib 0xa734f000 - 0xa7355ff3 libsystem_dnssd.dylib (878.50.17) <72A8BEDC-0C7C-355F-843D-75469DD85581> /usr/lib/system/libsystem_dnssd.dylib 0xa7356000 - 0xa73a5ffb libsystem_info.dylib (517.30.1) <E2FFFE29-1405-342E-8C57-31F681F510F7> /usr/lib/system/libsystem_info.dylib 0xa73a6000 - 0xa73caff3 libsystem_kernel.dylib (4570.61.1) <CF8A4C44-02A4-3C2B-B91B-9015F02D8DCF> /usr/lib/system/libsystem_kernel.dylib 0xa73cb000 - 0xa741afdb libsystem_m.dylib (3147.50.1) <290D02E2-227B-3B0A-BBFC-B14BC657ADE8> /usr/lib/system/libsystem_m.dylib 0xa741b000 - 0xa7435fff libsystem_malloc.dylib (140.50.6) <970603BE-8A36-3776-81A6-BC1B1D04AC35> /usr/lib/system/libsystem_malloc.dylib 0xa7436000 - 0xa755aff7 libsystem_network.dylib (1229.60.3) <6FCFE312-E7FD-382D-9246-2C8500A86ACB> /usr/lib/system/libsystem_network.dylib 0xa755b000 - 0xa7565fff libsystem_networkextension.dylib (767.60.1) <E8916FFA-B9A1-300E-84C8-669933B8B92E> /usr/lib/system/libsystem_networkextension.dylib 0xa7566000 - 0xa756eff3 libsystem_notify.dylib (172) <27A79E60-9B05-3B28-B389-5759A72F7321> /usr/lib/system/libsystem_notify.dylib 0xa756f000 - 0xa7575ffb libsystem_platform.dylib (161.50.1) <04C8CF15-A241-3BD8-87B5-DD5DA2DCD564> /usr/lib/system/libsystem_platform.dylib 0xa7576000 - 0xa7580ff3 libsystem_pthread.dylib (301.50.1) <95F98870-7DB1-3273-9E61-DEC04059BF18> /usr/lib/system/libsystem_pthread.dylib 0xa7581000 - 0xa7584ff3 libsystem_sandbox.dylib (765.60.1) <E689BACE-E8EE-39C6-BFD7-EE82CBD5EE82> /usr/lib/system/libsystem_sandbox.dylib 0xa7585000 - 0xa7587fff libsystem_secinit.dylib (30) <F11770B6-8928-3F4A-A5B6-1A7E93247738> /usr/lib/system/libsystem_secinit.dylib 0xa7588000 - 0xa7590ff7 libsystem_symptoms.dylib (820.60.2) <7FECC881-A6A0-3DC5-9382-F7EFB829FB1C> /usr/lib/system/libsystem_symptoms.dylib 0xa7591000 - 0xa75a3ffb libsystem_trace.dylib (829.50.17) <3786EA81-F02C-3115-A8B6-3AC9088EA04C> /usr/lib/system/libsystem_trace.dylib 0xa75a5000 - 0xa75abfff libunwind.dylib (35.3) <C9C74974-E6CE-386D-AF72-DC21323AF40B> /usr/lib/system/libunwind.dylib 0xa75ac000 - 0xa75d5ff7 libxpc.dylib (1205.60.9) <D3F2BB40-7D04-362C-BDF0-2C379C05EE99> /usr/lib/system/libxpc.dylib External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 44 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 979830 thread_create: 0 thread_set_state: 0 VM Region Summary: ReadOnly portion of Libraries: Total=243.1M resident=0K(0%) swapped_out_or_unallocated=243.1M(100%) Writable regions: Total=3.3G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=3.3G(100%) VIRTUAL REGION REGION TYPE SIZE COUNT (non-coalesced) =========== ======= ======= Accelerate framework 128K 2 Activity Tracing 256K 2 CG backing stores 11.1M 4 CG image 172K 16 CoreAnimation 144K 16 CoreGraphics 8K 2 CoreImage 16K 3 CoreUI image data 2028K 15 CoreUI image file 180K 4 Foundation 4K 2 Kernel Alloc Once 8K 2 MALLOC 3.2G 295 MALLOC guard page 48K 13 MALLOC_LARGE (reserved) 1024K 2 reserved VM address space (unallocated) Memory Tag 242 12K 2 Memory Tag 249 156K 2 OpenGL GLSL 128K 3 SBRK (reserved) 4096K 2 reserved VM address space (unallocated) Stack 10.0M 6 Stack Guard 56.0M 6 VM_ALLOCATE 98.7M 33 __DATA 10.6M 240 __FONT_DATA 4K 2 __GLSLBUILTINS 2588K 2 __LINKEDIT 78.9M 17 __OBJC 3220K 85 __TEXT 164.2M 241 __UNICODE 560K 2 mapped file 301.7M 219 shared memory 5416K 15 =========== ======= ======= TOTAL 3.9G 1225 TOTAL, minus reserved VM space 3.9G 1225 Model: MacBookPro12,1, BootROM MBP121.0176.B00, 2 processors, Intel Core i7, 3.1 GHz, 16 GB, SMC 2.28f7 Graphics: Intel Iris Graphics 6100, Intel Iris Graphics 6100, Built-In Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1867 MHz, 0x02FE, 0x4544464232333241314D412D4A442D460000 Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1867 MHz, 0x02FE, 0x4544464232333241314D412D4A442D460000 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x133), Broadcom BCM43xx 1.0 (7.77.37.31.1a9) Bluetooth: Version 6.0.6f2, 3 services, 27 devices, 1 incoming serial ports Network Service: Wi-Fi, AirPort, en0 Serial ATA Device: APPLE SSD SM0512G, 500.28 GB USB Device: USB 3.0 Bus USB Device: Internal Memory Card Reader USB Device: Bluetooth USB Host Controller Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1 > On 15 Feb 2019, at 23:40, Tim Mackinnon <tim(a)mackinnon.email> wrote: > > I will try not using full screen - but I guess it still stands that Iâm doing the same sort of things I did with 6 (where I did use full screen and an earlier iceberg - and donât recall the same level of instability). > > Again - Iâm still a fan, and want to forge forward - but I think we need to be careful. And I fully accept that - careful means all of us doing more testing and fixing more things ourselves. Itâs just the vm stuff and lower level iceberg are that much more difficult for more casual users to grapple with (although Iâm always impressed how far you can go) > > Tim > > > > Sent from my iPhone > >> On 15 Feb 2019, at 22:32, Hilaire <hilaire(a)drgeo.eu> wrote: >> >> Depends on what you are doing, I guess. >> >> I am using the same P7 32bits image on linux since June 2018, but I am >> doing bare bone smalltalk, and I don't use iceberg. It could be the >> source of your problem as it is still new, or it could be the 64bits >> image/vm. You could give a try for the 32bits version for a few days.. >> >>> Le 15/02/2019 Ã 12:11, Tim Mackinnon a Ã©crit : >>> Iâm not sure if this is born out by others - but Iâm finding that Pharo 7 is a bit less stable than Pharo 6 - Iâm seeing quite a few seg-faults where the vm dies and terminates - both when the image is left running for a while, but also in fresh images where I do an Iceberg load of my projects. Iâve also seen a lot of weird things like corrupted fonts and keyboard focus/cursor keys not working properly. >> >> -- >> Dr. Geo >> http://drgeo.eu >> >> >>

Feb. 16, 2019

Re: [Pharo-users] Monticello diff between image and tonel repo

by Hilaire

Hi Ben, I am not looking at you reproducing the scenario (you asked for) as it is some work and the outcome may not be reliable as you mentioned it. Nevertheless, the steps I described will likely get you on the trouble and are easy to get in. But more on sharing experience on this topic, as I meet it several times. I think it is an important issue, I have since migrating to Tonel, and it needs to be reported. Closing Monticello windows and opening a fresh one helped to get the changes right, sometime... Other time, forcing flush cash on Monticello helps. But still, this really makes fell the environment to be fragile and inconstant for serious work. It seems Monticello is confused by two sources of package tonel, and mcz. Already meet this problem too. Hilaire PS: DrGeo is free software. Le 16/02/2019 Ã 10:52, Ben Coman a Ã©critÂ : > That isn't even close to "steps to reproduce". > > Thats just a lot of effort for me to produce scenario B that has a > high chance ofÂ > being entirely unrelated to scenario A you presented. > -- Dr. Geo http://drgeo.eu

Feb. 16, 2019

Re: [Pharo-users] Monticello diff between image and tonel repo

by Ben Coman

Le 16/02/2019 Ã 07:23, Ben Coman a Ã©crit : > Its hard to determine what is wrong from the screen shot. > I'm probably not the one able to provide an answer, > but anyway... can you provide steps-to-reproduce in a fresh Image? On Sat, 16 Feb 2019 at 16:49, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi Ben, > > The screenshot shows two things: > > 1. In the top (black background), it shows the first lines of the file > 'DrGAngle3ptsOrientedItem.class.st' from the tonel repository, in > the DrGeoII-Core tonel package. In this source, you see a > 'CostumeClasse' method. > 2. In the second half of the screenshot, in the Pharo environment, > there are three windows to look at: > 1. in the background the Monticello window with the DrGeoII-Core > package selected from the tonel repo (the same as in 1.); > 2. on top of the Monticello window, the repository is open and you > can see its packages. The DrGeoII-Core package is selected; > 3. then the foreground window shows the changes between two > packages: one is the tonel package, the other one I don't know > (HilaireFernandes.7). Importantly, it look like costumClass > method does not exist in the tonel package, which is wrong as > seen in 1. That helped my understanding a lot. Its still a static snapshot though. It would be much easier to comment if I could scroll that changes list looking for patterns. > At the minimum, the information misrepresented, or I miss use the tool. Anyway it is confusing for me or not obvious, likely more confusing for > newbie which may think the tool is unreliable, and they want to go away. > > To reproduce, create a tonel repo, add package to this repo, or repo to > the package, and test the same as explained above. > That isn't even close to "steps to reproduce". Thats just a lot of effort for me to produce scenario B that has a high chance of being entirely unrelated to scenario A you presented. To make it easiest to help you, "steps to reproduce" means you hold my hand to *exactly* reproduce your screenshot. If you code is proprietary, you need to create a non-proprietary scenario B with the same problem which you can share in full. If that is too much effort for you, then its too much effort for me to GUESS at producing scenario B that is remotely close to your problem. Anyway, I'm a sucker and went digging anyway. I'm only *guessing* this is the referenced code... https://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/view/head:/src/D… What I notice is that all the "green-plus" methods are missing from there, and the "red-cross" method exists. So while I forget the semantics of each changes pane, perhaps you are reading it in reverse? "green-plus" methods are in Monticello package "red-cross" methods are missing from Monticello package HTH, YMMV, cheers -ben

Feb. 16, 2019

Re: [Pharo-users] Quality assistant

by Hilaire

Thanks Denis. By the way, Calypso is pretty cool. Le 15/02/2019 Ã 23:54, Denis Kudriashov a Ã©critÂ : > > Use following script to disable it: > > ClyCriticBrowserPlugin disable > -- Dr. Geo http://drgeo.eu

Feb. 16, 2019

Re: [Pharo-users] Monticello diff between image and tonel repo

by Hilaire

Hi Ben, The screenshot shows two things: 1. In the top (black background), it shows the first lines of the file 'DrGAngle3ptsOrientedItem.class.st' from the tonel repository, in the DrGeoII-Core tonel package. In this source, you see a 'CostumeClasse' method. 2. In the second half of the screenshot, in the Pharo environment, there are three windows to look at: 1. in the background the Monticello window with the DrGeoII-Core package selected from the tonel repo (the same as in 1.); 2. on top of the Monticello window, the repository is open and you can see its packages. The DrGeoII-Core package is selected; 3. then the foreground window shows the changes between two packages: one is the tonel package, the other one I don't know (HilaireFernandes.7). Importantly, it look like costumClass method does not exist in the tonel package, which is wrong as seen in 1. At the minimum, the information misrepresented, or I miss use the tool. Anyway it is confusing for me or not obvious, likely more confusing for newbie which may think the tool is unreliable, and they want to go away. To reproduce, create a tonel repo, add package to this repo, or repo to the package, and test the same as explained above. Hilaire Le 16/02/2019 Ã 07:23, Ben Coman a Ã©critÂ : > Its hard to determine what is wrong from the screen shot. > I'm probably not the one able to provide an answer,Â > but anyway... can you provide steps-to-reproduce in a fresh Image? > -- Dr. Geo http://drgeo.eu

Feb. 16, 2019

Re: [Pharo-users] Monticello diff between image and tonel repo

by Ben Coman

Its hard to determine what is wrong from the screen shot. I'm probably not the one able to provide an answer, but anyway... can you provide steps-to-reproduce in a fresh Image? cheers -ben On Sat, 16 Feb 2019 at 06:13, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi, > > I think I already report it but I still see this issue. From Monticello > when I request changes between image and my tonel repo I got wrong diff > report. It is a bit scarry. Will code be lost? You are not sure about > what really change. > > Or do I misunderstand something? > > See screenshot > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > >

Feb. 16, 2019

Re: [Pharo-users] Iceberg working with forks - can it be easier?

by Ben Coman

On Sat, 16 Feb 2019 at 02:06, Tim Mackinnon <tim(a)testit.works> wrote: > Hi guys - Iâve spent a few hours scratching my head trying to understand > why some of my Pull Requests to a project I had forked kept showing my > previous commits when I thought I was all caught up. > > It suddenly dawned on me, that when I had forked, and then done some work > and then submitted a PR, and then applied it upstream that my fork is now > no longer in sync with its upstream counterpart. > > Having not done this in ages, it took me a while to then realise I have to > do some git stuff to get it back in sync e.g. (and I think Iâve got this > right) > > git fetch upstream (or whatever name you gave it) > Git checkout master > Git merge upstream/master > > So I guess my question is - wouldnât it be helpful if this was a command > in Iceberg? It seems quite common to fork a project (I think this is still > recommended for pharo itself isnât it?) - and then at some point you need > to catchup with that origin again? Or am I missing something? I guess lots > of stuff can go wrong - but if it does - youâd still get the same problems > on the command line. It just seems that for normal situations - it would be > handy to run this straight in Pharo. > I'm not fully-conversant with Iceberg, but if I guess right... in Iceberg, right-click a repo and open its "Repository" window. In the top-right click the "Add remote" button, to add the upstream repo. That button is a bit hidden there. It might be nice to have it as a menu item on "Remotes" in the first pane. Then click the <Merge> button, then select the upstream master branch and you should be up to date. cheers -ben

Feb. 16, 2019

Re: [Pharo-users] im using pharo 7 with linux env. but cannot input korean.

by Pierce Ng

On Fri, Feb 15, 2019 at 10:42:42PM +0900, peter yoo wrote: > hello~.. im using pharo 7 with linux env. but cannot input korean. > and.. already start shell script file open and add "--compositioninput". I start Pharo with -compositioninput (one dash, didn't try two dashes for the option). Chinese and Japanese input works for me. In Pharo I use Noto Sans font loaded from system. OS is Xubuntu 18.04. Input system is fcitx and mozc for Japanese. In Pharo playground, press alt-space to enable Chinese/Japanese input, and just type.

Feb. 16, 2019

Re: [Pharo-users] Quality assistant

by Denis Kudriashov

Hi Hilaire Use following script to disable it: ClyCriticBrowserPlugin disable Ð¿Ñ, 15 ÑÐµÐ²Ñ. 2019 Ð³. Ð² 19:56, Hilaire <hilaire(a)drgeo.eu>: > So, no option to turn it off I guess? > > Hilaire > > Le 14/02/2019 Ã 12:03, Hilaire a Ã©crit : > > How to turn off the quality assitant in the calypso browser? > > > > I don't find anymore the option in the settings browser. > > -- > Dr. Geo > http://drgeo.eu > > > >

Feb. 15, 2019

Re: [Pharo-users] Stability of Pharo 7 vs 6?

by Hilaire

Depends on what you are doing, I guess. I am using the same P7 32bits image on linux since June 2018, but I am doing bare bone smalltalk, and I don't use iceberg. It could be the source of your problem as it is still new, or it could be the 64bits image/vm. You could give a try for the 32bits version for a few days.. Le 15/02/2019 Ã 12:11, Tim Mackinnon a Ã©critÂ : > Iâm not sure if this is born out by others - but Iâm finding that Pharo 7 is a bit less stable than Pharo 6 - Iâm seeing quite a few seg-faults where the vm dies and terminates - both when the image is left running for a while, but also in fresh images where I do an Iceberg load of my projects. Iâve also seen a lot of weird things like corrupted fonts and keyboard focus/cursor keys not working properly. -- Dr. Geo http://drgeo.eu

Feb. 15, 2019

Monticello diff between image and tonel repo

by Hilaire

Hi, I think I already report it but I still see this issue. From Monticello when I request changes between image and my tonel repo I got wrong diff report.Â It is a bit scarry. Will code be lost? You are not sure about what really change. Or do I misunderstand something? See screenshot Hilaire -- Dr. Geo http://drgeo.eu

Feb. 15, 2019

Re: [Pharo-users] im using pharo 7 with linux env. but cannot input korean.

by Hilaire

In your trad. chinese app were you able to key in chinese? A taiwanese friend of mine will be interested to know. Hilaire Le 15/02/2019 Ã 19:06, Sean P. DeNigris a Ã©critÂ : > Will you say more about your issue (e.g. steps to reproduce)? Make sure you > use a font that contains Korean characters. When I wrote a Chinese > (traditional) app, the default Pharo font did not and I had to change to > "Arial Unicode MS" -- Dr. Geo http://drgeo.eu

Feb. 15, 2019

Re: [Pharo-users] Quality assistant

by Hilaire

So, no option to turn it off I guess? Hilaire Le 14/02/2019 Ã 12:03, Hilaire a Ã©critÂ : > How to turn off the quality assitant in the calypso browser? > > I don't find anymore the option in the settings browser. -- Dr. Geo http://drgeo.eu

Feb. 15, 2019

Re: [Pharo-users] im using pharo 7 with linux env. but cannot input korean.

by Sean P. DeNigris

peter yoo wrote > cannot input korean. Will you say more about your issue (e.g. steps to reproduce)? Make sure you use a font that contains Korean characters. When I wrote a Chinese (traditional) app, the default Pharo font did not and I had to change to "Arial Unicode MS" ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 15, 2019

Iceberg working with forks - can it be easier?

by Tim Mackinnon

Hi guys - Iâve spent a few hours scratching my head trying to understand why some of my Pull Requests to a project I had forked kept showing my previous commits when I thought I was all caught up. It suddenly dawned on me, that when I had forked, and then done some work and then submitted a PR, and then applied it upstream that my fork is now no longer in sync with its upstream counterpart. Having not done this in ages, it took me a while to then realise I have to do some git stuff to get it back in sync e.g. (and I think Iâve got this right) git fetch upstream (or whatever name you gave it) Git checkout master Git merge upstream/master So I guess my question is - wouldnât it be helpful if this was a command in Iceberg? It seems quite common to fork a project (I think this is still recommended for pharo itself isnât it?) - and then at some point you need to catchup with that origin again? Or am I missing something? I guess lots of stuff can go wrong - but if it does - youâd still get the same problems on the command line. It just seems that for normal situations - it would be handy to run this straight in Pharo. Thoughts from the git experts? Tim

Feb. 15, 2019

im using pharo 7 with linux env. but cannot input korean.

by peter yoo

hello~.. im using pharo 7 with linux env. but cannot input korean. and.. already start shell script file open and add "--compositioninput". but any receive data from XIM(fcitx). who know for this issue? thanks. -- http://lookandwalk.com http://looknw.com | http://onionmixer.net peter yoo(Jonghwa Yoo). ROK

Feb. 15, 2019

Re: [Pharo-users] Stability of Pharo 7 vs 6?

by Sven Van Caekenberghe

I have been running Pharo 7.0[.1] for months on macOS 10.14.3 64-bit downloaded with ZeroConf and I have had no stability issues. I leave one or more images open going in and out of sleep on my MacBook Pro. I don't run full-screen, just semi-full-screen (Option-Click the green grow bullet, which leaves the menu bar visible). But YMMV, it all depends on what you are exactly doing. One (external) library, one different behaviour, one UI change can make a difference. > On 15 Feb 2019, at 12:11, Tim Mackinnon <tim(a)testit.works> wrote: > > Iâm not sure if this is born out by others - but Iâm finding that Pharo 7 is a bit less stable than Pharo 6 - Iâm seeing quite a few seg-faults where the vm dies and terminates - both when the image is left running for a while, but also in fresh images where I do an Iceberg load of my projects. Iâve also seen a lot of weird things like corrupted fonts and keyboard focus/cursor keys not working properly. > > From memory - I saw a lot less of this in Pharo 6 when I first moved to it. > > Possibly my usage is a bit different (although Iâm not sure) - but in all the cases above Iâm using OSX (HighSierra - so the same Mac OS as Pharo 6) - with the 64bit vm and running full screen. > > One thing that seems to help (but this is an early empirical observation) - if I save my image to a new name - this seems to help. So Iâm wondering if there might be something in the build process that has changed and is causing some sort of instability? > > I havenât done this long enough to really comment - but from all of the above, having a Pharo.1.image seemed to stop my problems. > > Possibly Iâve been unlucky - but of 7 images Iâve used in the last 2 weeks - 5 of them have had issues. I did notice that half of these images were the rc1 build 1436 setup (as I hadnât noticed that the blessed 7.0 stable image has a different version number (previously, the last builds in PL Pharo 7 development - was the stable version - unless work then went forward for a Pharo 7.1. I liked to nab the dev version so that I know the build number to report it. I now see the about Pharo in the image also lists this number). Also some of my images were retrieved via zeroConf in the terminal (again, not sure if this makes a difference - but did that a lot with P6 too). > > This isnât a complaint per se - as we need to move the platform forward and forge new approaches. So I really mention it to try and help diagnose the issues - or possibly understand if Iâm doing something weird. > > Tim

Feb. 15, 2019

Re: [Pharo-users] Stability of Pharo 7 vs 6?

by Alexandre Bergel

Personally, when I leave P7 open for a few hours, it slows down significantly. I have to save the image and open it back to not have any slug. Cheers, Alexandre http://bergel.eu > Le 15 fÃ©vr. 2019 Ã 08:11, Tim Mackinnon <tim(a)testit.works> a Ã©crit : > > Iâm not sure if this is born out by others - but Iâm finding that Pharo 7 is a bit less stable than Pharo 6 - Iâm seeing quite a few seg-faults where the vm dies and terminates - both when the image is left running for a while, but also in fresh images where I do an Iceberg load of my projects. Iâve also seen a lot of weird things like corrupted fonts and keyboard focus/cursor keys not working properly. > > From memory - I saw a lot less of this in Pharo 6 when I first moved to it. > > Possibly my usage is a bit different (although Iâm not sure) - but in all the cases above Iâm using OSX (HighSierra - so the same Mac OS as Pharo 6) - with the 64bit vm and running full screen. > > One thing that seems to help (but this is an early empirical observation) - if I save my image to a new name - this seems to help. So Iâm wondering if there might be something in the build process that has changed and is causing some sort of instability? > > I havenât done this long enough to really comment - but from all of the above, having a Pharo.1.image seemed to stop my problems. > > Possibly Iâve been unlucky - but of 7 images Iâve used in the last 2 weeks - 5 of them have had issues. I did notice that half of these images were the rc1 build 1436 setup (as I hadnât noticed that the blessed 7.0 stable image has a different version number (previously, the last builds in PL Pharo 7 development - was the stable version - unless work then went forward for a Pharo 7.1. I liked to nab the dev version so that I know the build number to report it. I now see the about Pharo in the image also lists this number). Also some of my images were retrieved via zeroConf in the terminal (again, not sure if this makes a difference - but did that a lot with P6 too). > > This isnât a complaint per se - as we need to move the platform forward and forge new approaches. So I really mention it to try and help diagnose the issues - or possibly understand if Iâm doing something weird. > > Tim

Feb. 15, 2019