August 2014 - Pharo-dev - lists.pharo.org

New address for the Spec jenkins

by Benjamin

If people are interested having the latest Spec bleeding image, it can now be retrieved at: http://benjamin.is-a-geek.com:8080/job/Spec/ :) Ben

Aug. 10, 2014

mustBeBooleanMagicIn can crash the vm

by Nicolai Hess

There is a certain risk, that the mustBeBooleanMagicIn method rewrite can crash the vm Issue 13805 <https://pharo.fogbugz.com/default.asp?13805> The receiver of the rewritten method is the "nonboolean" value receiving the ifTrue:ifFalse: message. But the rewritten method can include instvar accessor and self sends of the original method. We can include more rewrite rules in mustBeBooleanMagicIn like "rewrite instvar accessing" context receiver class instVarNamesAndOffsetsDo: [ :n :o | RBParseTreeRewriter new replace: n with: ('ThisContext receiver instVarAt: ', o asString); executeTree: methodNode. ]. "rewrite self sends" RBParseTreeRewriter new replace: 'self' with: 'ThisContext receiver'; executeTree: methodNode. But I don't know if this works for all possible situations. Or if there are better ways to do the rewriting.

Aug. 10, 2014

VM crash from triple 'Smalltalk garbageCollect' then forked Transcript stress test

by Ben Coman

Aug. 10, 2014

pillar parser with tokens?

by Tudor Girba

Hi, The Pillar parser does not record the token from the original text. Are there any plans to change this part :)? Doru -- www.tudorgirba.com "Every thing has its own flow"

Aug. 10, 2014

Re: [Pharo-dev] allUnimplementedCalls removed

by stepharo

I know that marcus is cleaning systemNavigation and moving some queries opening UI to AbstractTools. Now someone should have a look at what he is doing and give him feedback. Stef On 10/8/14 08:42, Pavel Krivanek wrote: > Hi Marcus, > > was it appropriate to remove allUnimplementedCalls from the > SystemNavigation? We lost an important message to check the image > health. Is there any replacement? > > Cheers, > -- Pavel > > >

Aug. 10, 2014

Re: [Pharo-dev] Duplicate repositories in fresh Image

by stepharo

Aug. 10, 2014

Re: [Pharo-dev] Submitted Improved Pharo Help (Case 13811) - but couldn't compare it?

by stepharo

On 9/8/14 15:07, Tim Mackinnon wrote: > Guys - Iâve incorporate the feedback from Nicolai from my previous help text submission and I thought I had the submission steps down pat - however I hit a strange problem when I was submitting my slice, and I want to check Iâm doing things right? > > My changes are very simple - 1 class method (to name my help entry) and class comment changes to improve the help text. > > I had been happily making changes and versioning them in my own local MC directory repo. > > When I went to submit my change - I didnât have a dirty package (as I had just versioned it locally) - but I donât think thats a problem right? I just created a +Slice, entered my Fobgugz number and then selected my Package by scrolling through the list of packages. > > However when I wen to compare my change against the Pharo40inbox - it kept saying that there were no changes? I donât understand that - as the inbox has my previous submission 6.mcz and something by Stefan 7.mcx - so I was expecting to see the single class method change as well as the class comment change? Did I do something wrong? You should not compare against the inbox but again the Pharo40 repo. The comparison will show you the diffs with the current Pharo head and not a random file that somebody pushed in the inbox. Because in inbox well this is an inbox. Can you rety and let us know if this solves your problem. > > To make sure, I went back - made a small text change, so that I had a dirty package, and then followed the same steps in the video - and this time it did show me a change against Pharo40Inbox, but it was just my small text change? So Iâm worried that Iâve done something funny - but I canât work out what? > > Could someone just set me straight? > > Tim >

Aug. 10, 2014

Submission problems fixed - ESUG 2014 REMINDER: 11th Innovation Technology Awards

by jdelgado＠lsi.upc.edu

We're sorry but we realized that there was a misconfiguration that prevented the submission of award candidates. It has been fixed and now it works fine. ESUG 2014 REMINDER: 11th Innovation Technology Awards http://www.esug.org/Conferences/2014/Innovation-Technology-Awards Have you written innovative Smalltalk? The developers of any Smalltalk-based software can enter by submitting a 3-5min video of their software. Entrants demo their systems in a session at the end of Monday August 18th 2014, after which the conference attendees vote. (A vote consists in providing a sorted list of 3 preferred pieces of software.) The top 3 teams with the most innovative software will receive, respectively, 500 Euros, 300 Euros and 200 Euros. The results are announced in the Awards ceremony that is held during the social event. Applicants should provide the following information on the conference registration server. Once you have registered your personal info, an 'Awards' menu allows submitting your software. You can provide this information when you first register, or login again later and update your details. The registration server will open soon. You can start preparing your software right now though. Info to provide: Name of the software Licence information (free, shareware, or commercial) Name of the Smalltalk dialect used Name, Affiliation and Country of developers Besides, it would be great if the submission could include: URL for a video (3-5 min) showing a screencast / demo of the software URL for downloading the software or at least a runnable demo Deadline: *August 15th* Any Smalltalker can apply (students, companies, ...). The presented piece of code/software should be written in Smalltalk or directly support Smalltalk (e.g. Smalltalk VM). All Smalltalk dialects are accepted. The applicant should be "strongly related" to the presented code, be it as an author, as owner of the copyright/copyleft, or as an official representative of the copyright/copyleft owner. Bests Jordi

Aug. 10, 2014

allUnimplementedCalls removed

by Pavel Krivanek

Hi Marcus, was it appropriate to remove allUnimplementedCalls from the SystemNavigation? We lost an important message to check the image health. Is there any replacement? Cheers, -- Pavel

Aug. 10, 2014

Re: [Pharo-dev] [Moose-dev] [Solved] Pharo image corruption and fatal VM error with Roassal

by Nicolai Hess

How , what caches ? 2014-08-09 0:37 GMT+02:00 Igor Stasenko <siguctua(a)gmail.com>: > Just use the canvas'es cache. It will ensure that you won't have problems > with session. > > > On 6 August 2014 23:52, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> In the solution I posted on the list, only TRCanvas holds the session and >> if >> it changes all attached Shapes resets its path. >> >> >> >> 2014-08-06 21:43 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: >> >> Thanks Vincent! >>> It seems to work well. >>> >>> Included in Roassal! >>> >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> On Aug 6, 2014, at 12:29 PM, Blondeau Vincent < >>> vincent.blondeau(a)worldline.com> wrote: >>> >>> Solved ! >>> >>> You will found the changes in the attached .mcz. >>> >>> I added some sessions guards where some Athens external objects are >>> used. Stef you were right ;) >>> Particularly for checking the IV TRCanvas>>canvas and on TRShape>>path >>> that relies on Athens external objects. >>> >>> It seems to works for me. If it is the case for you, it we be nice to >>> integrate it quickly to be able to work fine :) >>> >>> Thanks >>> >>> Vincent >>> >>> -----Message d'origine----- >>> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org >>> <pharo-dev-bounces(a)lists.pharo.org>] De la part de stepharo >>> EnvoyÃ© : jeudi 31 juillet 2014 22:58 >>> Ã : Pharo Development List >>> Objet : Re: [Pharo-dev] [Moose-dev] Pharo image corruption and fatal VM >>> error with Roassal >>> >>> Alexandre >>> >>> may be you should try to understand what is a session. >>> Because this is about 2 lines of code. >>> >>> When you open an image you save 2 min ago or 2 years ago, how the system >>> knows that an OS ressources is valid? >>> By checking the session id... >>> >>> Stef >>> >>> On 31/7/14 16:09, Alexandre Bergel wrote: >>> >>> Yes, and this is a mess. >>> I've spent quite some time in getting the session working with Roassal2 >>> and it still does not work. I would appreciate help on this. >>> >>> Alexandre >>> >>> >>> On Jul 31, 2014, at 8:58 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: >>> >>> It looks like Trachel does not recreate athens external resources. >>> There is an example in AthensSceneView, on how to check and reload an >>> AthensSurface. >>> >>> >>> 2014-07-31 12:51 GMT+02:00 Usman Bhatti <usman.bhatti(a)gmail.com>: >>> >>> >>> >>> On Thu, Jul 31, 2014 at 11:17 AM, Blondeau Vincent < >>> vincent.blondeau(a)worldline.com> wrote: >>> Yes it is. But I will not do >>> >>> TRMorph allInstances do: #delete >>> >>> In command line every day... >>> >>> >>> It is only intended to recover your lost work in the image not for >>> everyday use :). >>> >>> >>> >>> >>> Vincent >>> >>> >>> >>> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org >>> <pharo-dev-bounces(a)lists.pharo.org>] De la part >>> de Usman Bhatti EnvoyÃ© : jeudi 31 juillet 2014 10:59 Ã : Pharo >>> Development List Cc : Moose-related development >>> >>> >>> Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error >>> with Roassal >>> >>> >>> >>> This may be related to this known issue reported a few days back. >>> >>> https://code.google.com/p/moose-technology/issues/detail?id=1084 >>> >>> >>> >>> And there is a possible solution to recover your image. >>> >>> >>> >>> usman >>> >>> >>> >>> On Thu, Jul 31, 2014 at 10:50 AM, Blondeau Vincent < >>> vincent.blondeau(a)worldline.com> wrote: >>> >>> Hi, >>> >>> >>> >>> Yesterday, I was using GraphET (a part of Roassal) to do some charts >>> and, today, when I wanted to reopen the image. >>> >>> And I got that : >>> >>> <image001.png> >>> >>> It is *very* unpleasant... >>> >>> >>> >>> To reproduce the bug: >>> >>> 1 - You can do either: >>> >>> | builder | >>> >>> builder := GET2Line data: (0 to: 100) . >>> >>> builder >>> >>> y: [ :x | x*x ]. >>> >>> >>> >>> builder open. >>> >>> Or >>> >>> WorldMenu -> Roassal examples -> choose an item -> click on a graph . A >>> TRMorph should be opened. >>> >>> 2 - don't close the graph and save the pharo image. >>> >>> 3 - Close the pharo image >>> >>> 4 - Reopen it >>> >>> >>> >>> I am under W7 x64 with the latest moose image and the VM available on >>> the pharo.org website (http://files.pharo.org/platform/Pharo3.0-win.zip) >>> from the 10 july. >>> >>> You will find the crash dump attached. >>> >>> >>> >>> >>> >>> Thankfully, I managed to open the image with a latest VM ( >>> http://www.mirandabanda.org/files/Cog/VM/VM.r3056/cogwin-14.29.3056.zip >>> ). >>> >>> Thanks a lot Eliot ! :) >>> >>> >>> >>> And I got this: >>> >>> <image002.png> >>> >>> >>> >>> Thanks in advance >>> >>> >>> >>> Cheers, >>> >>> Vincent BLONDEAU >>> >>> >>> >>> >>> >>> >>> Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã >>> l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par >>> le secret professionnel. Si vous recevez ce message par erreur, merci d'en >>> avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du >>> message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de >>> Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien >>> que les meilleurs efforts soient faits pour maintenir cette transmission >>> exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et >>> sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant >>> d'un virus transmis. >>> >>> This e-mail and the documents attached are confidential and intended >>> solely for the addressee; it may also be privileged. If you receive this >>> e-mail in error, please notify the sender immediately and destroy it. As >>> its integrity cannot be secured on the Internet, the Worldline liability >>> cannot be triggered for the message content. Although the sender endeavours >>> to maintain a computer virus-free network, the sender does not warrant that >>> this transmission is virus-free and will not be liable for any damages >>> resulting from any virus transmitted. >>> >>> >>> >>> >>> >>> Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã >>> l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par >>> le secret professionnel. Si vous recevez ce message par erreur, merci d'en >>> avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du >>> message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de >>> Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien >>> que les meilleurs efforts soient faits pour maintenir cette transmission >>> exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et >>> sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant >>> d'un virus transmis. >>> >>> This e-mail and the documents attached are confidential and intended >>> solely for the addressee; it may also be privileged. If you receive this >>> e-mail in error, please notify the sender immediately and destroy it. As >>> its integrity cannot be secured on the Internet, the Worldline liability >>> cannot be triggered for the message content. Although the sender endeavours >>> to maintain a computer virus-free network, the sender does not warrant that >>> this transmission is virus-free and will not be liable for any damages >>> resulting from any virus transmitted. >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >>> >>> >>> >>> Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã >>> l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par >>> le secret professionnel. Si vous recevez ce message par erreur, merci d'en >>> avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du >>> message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de >>> Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien >>> que les meilleurs efforts soient faits pour maintenir cette transmission >>> exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et >>> sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant >>> d'un virus transmis. >>> >>> This e-mail and the documents attached are confidential and intended >>> solely for the addressee; it may also be privileged. If you receive this >>> e-mail in error, please notify the sender immediately and destroy it. As >>> its integrity cannot be secured on the Internet, the Worldline liability >>> cannot be triggered for the message content. Although the sender endeavours >>> to maintain a computer virus-free network, the sender does not warrant that >>> this transmission is virus-free and will not be liable for any damages >>> resulting from any virus transmitted. >>> <Trachel-VincentBlondeau.180.mcz> >>> _______________________________________________ >>> >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >>> >> > > > -- > Best regards, > Igor Stasenko. >

Aug. 9, 2014