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

[Solved] Pharo image corruption and fatal VM error with Roassal
by Blondeau Vincent Aug. 9, 2014

Aug. 9, 2014

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] 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] 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.

4 6

building vm on OSX 10.9: 'features.h' not found
by Max Leske Aug. 9, 2014

Aug. 9, 2014

Apparently stuff has changed since I last built a VM. Now I canât get past this annoying error: -- Generating done -- Build files have been written to: /Users/theseion/devel/git/pharo-vm/build Scanning dependencies of target SqueakSSL [ 1%] Building C object SqueakSSL/CMakeFiles/SqueakSSL.dir/Users/theseion/devel/git/pharo-vm/src/plugins/SqueakSSL/SqueakSSL.c.o In file included from /Users/theseion/devel/git/pharo-vm/src/plugins/SqueakSSL/SqueakSSL.c:21: In file included from /Users/theseion/devel/git/pharo-vm/platforms/Cross/vm/sqVirtualMachine.h:24: In file included from /Users/theseion/devel/git/pharo-vm/platforms/Cross/vm/sqMemoryAccess.h:18: In file included from /Users/theseion/devel/git/pharo-vm/build/config.h:141: /Users/theseion/devel/git/pharo-vm/platforms/unix/vm/glibc.h:1:10: fatal error: 'features.h' file not found #include <features.h> ^ 1 error generated. make[2]: *** [SqueakSSL/CMakeFiles/SqueakSSL.dir/Users/theseion/devel/git/pharo-vm/src/plugins/SqueakSSL/SqueakSSL.c.o] Error 1 make[1]: *** [SqueakSSL/CMakeFiles/SqueakSSL.dir/all] Error 2 make: *** [all] Error 2 Iâve done everything suggested by the readme on github and Iâve symlinked /usr/include to /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk/usr/include just in case, but no luck so far. Any ideas? Cheers, Max

3 6

[GTInspector] Showing object state using a tree
by Tudor Girba Aug. 9, 2014

Aug. 9, 2014

Hi, The GTInspector now shows the state of an object in a tree view (screenshots below). This tree view focuses on the internal structure of an object. For example, when looking at a dictionary object you will see the "array" and the "tally" attributes and not the key value pairs. Those can be accessed from another presentation of a dictionary object. So the tree is meant to be used together with the finder and the other presentations of on object. Let us know what you think. Cheers, Andrei & Doru [image: Inline image 1] [image: Inline image 2] -- www.tudorgirba.com "Every thing has its own flow"

5 9

Imminent change to Spur image format
by Eliot Miranda Aug. 8, 2014

Aug. 8, 2014

Hi All, as part of the Newspeak infrastructure we use at Cadence I implemented multiple bytecode set support and a lifting of the limits in a method on the number of literals and the span of branches about two years ago. This work involved adding a second interpretation to the bits in a method header, providing 16 bits of literal count. This was done by moving the primitive number out of the method header and into an optional callPrimitive bytecode, being the first bytecode of methods that have primitives. Now in Spur I have the opportunity to use this expanded format for the exsting bytecode set as well. The SqueakV3 set does not use bytecode 139, which is convenient to use for its callPrimitiveBytecode. The advantage is that when and if a new bytecode set is added, as is planned for the Sista VMs, the VM will not have to test method headers to decide which format they're in, because there will only be one. Alas I only just realised this last night, and implementing this for Spur now means that any existing Spur images will be invalid. But better I do this now than later, when Spur is in wide-spread use. So this message is to warn you that any existing Spur images will have to be discarded and rebuilt soon, once I release new VMs. Apologies for the inconvenience. I do plan for the VMs to exit with a useful error message when loading Spur images with the old method header format, rather than just crashing. So I hope the transition won't be too painful. -- best, Eliot

2 1

Re: [Pharo-dev] Komitter in 30852?
by Stephan Eggermont Aug. 8, 2014

Aug. 8, 2014

Works for me. Thank you Thierry! Stephan

2 1

Only one week left!! - ESUG 2014 REMINDER: 11th Innovation Technology Awards
by jdelgado＠lsi.upc.edu Aug. 8, 2014

Aug. 8, 2014

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

1 0

[Remainder] Call for participation to the Second Visualization Contest with Roassal
by Alexandre Bergel Aug. 8, 2014

Aug. 8, 2014

Dear colleagues and friends, We are happy to announce the Second Visualization Contest with Roassal. What can I win? - 150 euros, sponsored by ObjectProfile - a Ã¼ber-cool ObjectProfile T-shirt and some wonderful stickers - maximum publicity of your work - a nice award certificate, delivered during ESUG How can I win? - you have to produce a visualization with Roassal. You can use the Pharo, VisualWorks, Amber or VAST version of Roassal. Here is an example of what we expect http://bit.ly/sunburstDemo http://bit.ly/GraphET https://vimeo.com/96091089 about smartbrowser https://vimeo.com/94724841 about GraphBuilder http://www.youtube.com/watch?v=uOmox7NgRAg&feature=youtu.be on AspectMaps, by Johan Fabry, the winner of the contest last year - making a video is mandatory. The video will weight the most in our decision. The video could be of any length and has to include your name and say that is was made (partly or completely) with Roassal. No need to talk, just show off! - making your code available and easy to install will help you get more points How can I submit? - send the links of your video and other material (if needed) to info(a)objectprofile.com Every email you will send to this email will be acknowledged. If you do not receive a 'Ok' from us, it means we haven't read it, in that case send your email again after a few days. - the deadline for submitting is August 11, 2014 Mini FAQ? - Is the object-profile team allowed to participate? No - I know nothing about Roassal, how can I start? Roassal comes with a large set of examples. On Pharo, just use the example browser available from the world menu. The book http://www.deepintopharo.com also contains chapter on Roassal 1 and Mondrian. You are also very welcome to ask question to the Pharo or Moose mailing lists about Roassal. Or simply send email to info(a)objectprofile.com . We will help you. - Iâve heard about Roassal2, Roassal3d, Roassal1. I feel lost in all these keywords! Wellâ¦ Roassal1 is available on VisualWorks and VAST. Roassal2 works on Pharo and Amber. Roassal2 is a major revamp of Roassal1. The documentation on Roassal1 may be easily adapted to Roassal2. - Should my visualization or code be open source? No need for this, whatever license is fine. However your video has to be public. - How can I get more information? Just comment on the facebook https://www.facebook.com/ObjectProfile or using Twitter @ObjectProfile or send email to info(a)objectprofile.com or the pharo or moose mailing list - What I submit two different videos? Yes, no problem with that. As many as you are productive. - Who won last year? Johan Fabry with AspectMaps made a nice video about visualizing aspects. - How will judge the videos? both the esug community and the object profile team. The Esug community will have 30% of the final grade, object profile the remaining 70% Cheers, The profilers

1 1

Metacello Projects: one canonical config/repo for all platforms
by Sean P. DeNigris Aug. 8, 2014

Aug. 8, 2014

There are two things that have bothered me about our use of Metacello, but I couldn't explain exactly why until now. These are two guidelines that I think are important: 1. ConfigurationOfMyProject should live at repoOfMyProject. Any MetaRepoForXyz should only be a copy of this config 2. Platform-specific config sections are not optional Without these two things, we're back in Babbel. Here's why... I wrote a configuration that depended on several well-known projects. Someone had very generously updated the configs and placed them in metaReposForXyz (e.g. http://squeaksource.com/MetacelloRepository) so that's the repo I referenced in my config. In the meantime, the same was done for later Pharo versions (MetaRepoFor30, etc). Now I'm stuck - either I have to manually manage platform variations of project dependencies myself, or settle to only ever have my config work in latest Pharo - but I'll still have to update the repo url for each new version which is a pain. Of course I understand that editing directly in a MetaRepo is very tempting (and I've done it myself), it is a quick and dirty hack that subverts much of the value of Metacello. Of course, there are limits to our ability to follow #1, like where we don't have access to the repo, but it doesn't even seem like we're trying. And there are limits to #2 like maybe we don't know how to get it to work in Squeak, but we can at least keep Pharo versions working. I have been using Mariano's workflow of using latest Pharo as the reference implementation and adding compatibility shims for previous versions. If we don't take an extra moment to do it right, we simply push this work onto users. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Metacello-Projects-one-canonical-config-repo-for-all-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

4 7

[pharo-project/pharo-core]
by GitHub Aug. 8, 2014

Aug. 8, 2014

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

1 0

[pharo-project/pharo-core] 927b5e: 30853
by GitHub Aug. 8, 2014

Aug. 8, 2014

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 927b5e4504064636faa83109b74ecb54dae1add1 https://github.com/pharo-project/pharo-core/commit/927b5e4504064636faa83109… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-08-08 (Fri, 08 Aug 2014) Changed paths: M Kernel.package/SelectorException.class/class/signaling/signalFor_in_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script115.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30853.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Inspector.package/EyeInspector.class/instance/accessing/selectedElement.st M Text-Edition.package/SmalltalkEditor.class/instance/menu messages/fileItIn.st Log Message: ----------- 30853 13796 DNU ReadWriteStream>>fileIn in SmalltalkEditor>>fileItIn https://pharo.fogbugz.com/f/cases/13796 13658 backport 3.0: 13654 Pressing Enter in EyeInspector gives MNU: TextModel>>asText https://pharo.fogbugz.com/f/cases/13658 13626 SelectorException>>signalFor:In: does not understand object: https://pharo.fogbugz.com/f/cases/13626 http://files.pharo.org/image/30/30853.zip

1 0