March 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Script to download Pharo 4 vm for Mac os sierra

by Christophe Demarey

http://files.pharo.org/get-files/40/pharo-mac-stable.zip <http://files.pharo.org/get-files/40/pharo-mac-stable.zip> > Le 16 mars 2017 Ã 15:41, Cyrille Delaunay <cy.delaunay(a)gmail.com> a Ã©crit : > > Hello, > > We have a jenkins job, running on a linux machine, that is responsible for building and outputing a Pharo 4 development image + vm ready to be used on mac machines. > > We use this command line to download the VM and archived it as output of the job: > > curl -O http://files.pharo.org/vm/pharo/mac/Pharo-VM-mac-latest.zip <http://files.pharo.org/vm/pharo/mac/Pharo-VM-mac-latest.zip> > > On my mac (10.12.1), when i open the pharo image with this vm , I am facing what seem to be some known issues for Mac OS sierra: > > Pharo[13048:431565] *** -[NSPathStore2 stringByAppendingPathExtension:]: cannot append extension 'bundle/Contents/MacOS/' to path ... > > Now, when I try to download a Pharo 4 vm directly from my mac sierra machine, > with a zeroconf script (get.pharo.org/vm40 <http://get.pharo.org/vm40>), > It works: I am able to open the pharo image with this vm. > > Is there a script that allows to download a pharo 4 vm working for mac os sierra, from a linux machine ? > > -- > Cyrille Delaunay

March 16, 2017

Script to download Pharo 4 vm for Mac os sierra

by Cyrille Delaunay

Hello, We have a jenkins job, running on a linux machine, that is responsible for building and outputing a Pharo 4 development image + vm ready to be used on mac machines. We use this command line to download the VM and archived it as output of the job: curl -O http://files.pharo.org/vm/pharo/mac/Pharo-VM-mac-latest.zip On my mac (10.12.1), when i open the pharo image with this vm , I am facing what seem to be some known issues for Mac OS sierra: Pharo[13048:431565] *** -[NSPathStore2 stringByAppendingPathExtension:]: cannot append extension 'bundle/Contents/MacOS/' to path ... Now, when I try to download a Pharo 4 vm directly from my mac sierra machine, with a zeroconf script (get.pharo.org/vm40) It works: I am able to open the pharo image with this vm. Is there a script that allows to download a pharo 4 vm working for mac os sierra, from a linux machine ? -- Cyrille Delaunay

March 16, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60446 Home: https://github.com/pharo-project/pharo-core

March 16, 2017

[pharo-project/pharo-core] f18bb0: 60446

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: f18bb0ac2c9e97695cc0cd5e63a9cb501371e9c5 https://github.com/pharo-project/pharo-core/commit/f18bb0ac2c9e97695cc0cd5e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-03-16 (Thu, 16 Mar 2017) Changed paths: M Nautilus.package/AbstractNautilusUI.class/instance/updating/okToChange.st A Reflectivity-Examples.package/ReflectivityDemos.class/README.md A Reflectivity-Examples.package/ReflectivityDemos.class/definition.st A Reflectivity-Examples.package/ReflectivityDemos.class/instance/cleanup/cleanUp.st A Reflectivity-Examples.package/ReflectivityDemos.class/instance/demos/demoSelfSendLogging.st M Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - links/testSetLink.st A Reflectivity.package/extension/RBProgramNode/instance/hasMetalink_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60445.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60446.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60445.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60446.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60446 19842 add simple api for testing if a link is installed in a node https://pharo.fogbugz.com/f/cases/19842 19841 Format as you read can produce confusing "contents has been modified" questions https://pharo.fogbugz.com/f/cases/19841 19843 add simple demo of logging self sends https://pharo.fogbugz.com/f/cases/19843 http://files.pharo.org/image/60/60446.zip

March 16, 2017

[pharo-project/pharo-core] 29dba2: 60445

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 29dba2c3c2aa46417d000a01f7df575968e3f7b7 https://github.com/pharo-project/pharo-core/commit/29dba2c3c2aa46417d000a01… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-03-16 (Thu, 16 Mar 2017) Changed paths: A Reflectivity.package/ReflectiveMethod.class/instance/printing/printOn_.st A Reflectivity.package/ReflectiveMethod.class/instance/spotter/spotterActDefault.st A Reflectivity.package/ReflectiveMethod.class/instance/spotter/spotterForBytecodesFor_.st A Reflectivity.package/ReflectiveMethod.class/instance/spotter/spotterForImplementorsFor_.st A Reflectivity.package/ReflectiveMethod.class/instance/spotter/spotterForMessagesFor_.st A Reflectivity.package/ReflectiveMethod.class/instance/spotter/spotterForSendersFor_.st A Reflectivity.package/ReflectiveMethod.class/instance/spotter/spotterItemsFor_.st A Reflectivity.package/ReflectiveMethod.class/instance/spotter/spotterMethodClassFor_.st A Reflectivity.package/ReflectiveMethod.class/instance/spotter/spotterPreviewCodeIn_.st A Reflectivity.package/ReflectiveMethod.class/instance/spotter/spotterSelectFor_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60444.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60445.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60444.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60445.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Examples.package/TabsExample.class/class/examples/example.st Log Message: ----------- 60445 19844 remove some trivial duplicated code from TabsExample>>#open https://pharo.fogbugz.com/f/cases/19844 19845 add printOn: to ReflectiveMethod https://pharo.fogbugz.com/f/cases/19845 19846 Make spotter work with ReflectiveMethods. https://pharo.fogbugz.com/f/cases/19846 http://files.pharo.org/image/60/60445.zip

March 16, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60445 Home: https://github.com/pharo-project/pharo-core

March 16, 2017

Re: [Pharo-dev] [Vm-dev] BUG? A problem with callbacks that shows up in 64bits (but is on 32bits too)

by Igor Stasenko

On 16 March 2017 at 01:44, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Igor, > > On Wed, Mar 15, 2017 at 2:53 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> >> Here's my d) >> implement callback functions in C, or in native form => no need for >> entering the smalltalk execution => no risk of GC => nothing to worry about. >> >> I guess nobody will like it (and will be right, of course ;) , but it is >> how it was originally done. I used NativeBoost to implement those callback >> functions and they're won't cause any GC problems. >> > > yes, I like this. I was wondering why the callbacks solution was used at > all yesterday. All they do is redirect to the cairo library. What are the > reasons? Tedious to write and maintain the necessary simple plugin? > > ClÃ©ment pointed out a really ugly problem with the current > implementation. If one calls back into Pharo from the BitBlt primitives > and then reinvokes BitBlt, say by innocently putting a halt in those > callbacks, then the original BitBlt's state will get overwritten by the > BitBlt invocations in the callback's dynamic exert. At least with my > changes the BitBlt primitive will abort, rather than continue with the > invalid state. > > >> That, of course, gave me solution in this concrete case, but not in >> general.. i.e. : if you have another callback that cannot be implemented >> na(t)ively, then >> you facing similar problems, mainly: how to work around the problem, that >> primitive(s) that using callbacks may capture state, that are subject of GC >> activity. >> >> In general , then, i think such primitive should be (re)written in such >> way , that it won't get puzzled by GC.. and addGCRoot(s), IMO then best >> way, from general interfacing/implementation standpoint. >> I would just add extra interface for using it especially in primitives, >> so that it >> 1) won't punish primitive writer with too much coding >> 2) automatically handle primitive/callback nesting e.g. >> primitive1 -> adds roots1 -> calls fn -> callback -> st code -> >> primitive2 -> adds roots2 -> calls fn2 -> callback2 ... >> >> >> something like this: >> >> static initialized once myprimooptable = [ a,b,c]. >> vm pushPrimRoots: myooptable. >> self do things primitive does. >> vm popPrimRoots >> >> or, since we have green threading, then maybe better will be in this >> form: >> >> rootsId := static initialized once myprimooptable = [ a,b,c]. >> vm pushPrimRoots: myooptable. >> self do things primitive does. >> vm popPrimRoots: rootsId. >> > > We kind of have this with the addGCRoot: interface. But I think it's much > better to design the system so that the primitive fails and can be > retried. The problem there is having to have the primitive failure code > check and roll back. For example in the copyBits primitive one sees > > ((sourceForm isForm) and: [sourceForm unhibernate]) > ifTrue: [^ self copyBits]. > ((destForm isForm) and: [destForm unhibernate]) > ifTrue: [^ self copyBits]. > ((halftoneForm isForm) and: [halftoneForm unhibernate]) > ifTrue: [^ self copyBits]. > > This is really scruffy because...GrafPort implements copyBits, so this > ends up not just retrying the primitive but running a lot more besides. > One way to write it is > > > ((sourceForm isForm) and: [sourceForm unhibernate]) > ifTrue: [^ self perform: #copyBits withArguments: #() inSuperclass: > BitBlt]. > ((destForm isForm) and: [destForm unhibernate]) > ifTrue: [^ self perform: #copyBits withArguments: #() inSuperclass: > thisContext method methodClass]. > ((halftoneForm isForm) and: [halftoneForm unhibernate]) > ifTrue: [^ self perform: #copyBits withArguments: #() inSuperclass: > thisContext methodClass]. > > but that's ugly. > > A mechanism that was in the VM would be nice. The state for the > invocation is saved on the stack. So there could be a special failure path > for this kind of recursive invocation problem; another send-back such as > doesNotUnderstand: attemptToReturn:through:. Note (I'm sure you know this > Igor) that there are primitives such as the ThreadedFFIPlugin's call-out > primitive that very much expect to be invoked recursively and have no > problem with it. > > Yes, i know it. But keep in mind, that reentrant FFI callout mechanism means *just* reentrant FFI callout code, it doesn't means that things, it will be calling, automagically become reentrant as well. And the above note about "ClÃ©ment pointed out a really ugly problem" is good example of it :) And since you cannot predict/prevent/pretend/protect every single piece of code, that FFI users are going to call, there's no solution to that, unless users understand what they do and be aware of pitfalls and consequences. It is quite easy to say "meh.. your FFI don't works.. go away, come year later.. i will use other (put other language/software system there)".. mostly because of ignorance, that there's a limits on what FFI can do and what can't. -- Best regards, Igor Stasenko.

March 16, 2017

changing pharo packaging in linux

by Esteban Lorenzano

Hi, Last weeks I was fighting with library dependency problems on linux distributions and at the end I came to the conclusion that the only way to guarantee that our own dependencies will be found first than OS versions (which can have problems for us when we choose to distribute a library by our own) is to add library directory to LD_LIBRARY_PATH before the execution. Now, I added that to zeroconf and thatâs working fine, but now we have the problem of the ânon zeroconfâ distributions. I checked how to add this and well, turns out that âold wayâ of distributions, from the standard builds of os-vm (we changed it like 5 years ago) already have something like that. The osvm for linux has this structure: ./pharo ./lib ./lib/5.0-201703221605 ./lib/5.0-201703221605/* //All binaries and libraries here ./bin ./bin/pharo thing is: here ./pharo is an script who mades all we need. So, instead reinventing the wheel I want to go back to this structureâ¦ I do not think it will imply anything to anyone, but I wanted to let you know :) cheers, Esteban

March 16, 2017

[Pharo6] Issue tracker status: 23 issues open

by Marcus Denker

Hi, Status of the issue tracker: Pharo6: 23 Overall: 581 https://pharo.fogbugz.com/f/filters/1192/6-0-All <https://pharo.fogbugz.com/f/filters/1192/6-0-All> Any help on the 23 is welcome (e.g. some do not look like show-stoppers, so the submitter can think about removing the Pharo6 Milestone tag). Marcus

March 16, 2017

Re: [Pharo-dev] Extra Contents has been modified

by Pavel Krivanek

We have found the source of this issue: https://pharo.fogbugz.com/f/cases/19841/Format-as-you-read-can-produce-conf… -- Pavel 2017-03-15 21:35 GMT+01:00 stepharong <stepharong(a)free.fr>: > Hi > > I'm coding on 60438 and I have a super annoying glitch. When I click on a > method in the method list of a test method I get > systematically a Contents.... validate or cancel. > > I do not have the time to carefully check because I need to commit and > stop and tomorrow is totally crazy (even more). > > Stef > > -- > Using Opera's mail client: http://www.opera.com/mail/ > >

March 16, 2017