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

[pharo-project/pharo-core] dd2506: 40145

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: dd2506740c3f98ea33b4c8684fbf6da8b346c702 https://github.com/pharo-project/pharo-core/commit/dd2506740c3f98ea33b4c868… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-07-31 (Thu, 31 Jul 2014) Changed paths: M Announcements-Tests-Core.package/AnnouncerTest.class/instance/testing/testNoArgBlock.st M Announcements-Tests-Core.package/AnnouncerTest.class/instance/testing/testTwoArgBlock.st A Monticello.package/MCFileBasedRepository.class/class/settings/monticelloSettingsOn_.st R Nautilus.package/AbstractNautilusUI.class/instance/accessing/cachedHierarchy.st R Nautilus.package/AbstractNautilusUI.class/instance/accessing/cachedHierarchy_.st M Nautilus.package/AbstractNautilusUI.class/instance/accessing/showGroups_.st M Nautilus.package/AbstractNautilusUI.class/instance/accessing/showPackages_.st R Nautilus.package/AbstractNautilusUI.class/instance/accessing/toggleShowComment.st R Nautilus.package/AbstractNautilusUI.class/instance/accessing/toggleShowFullComment.st R Nautilus.package/AbstractNautilusUI.class/instance/accessing/toggleShowGroups.st R Nautilus.package/AbstractNautilusUI.class/instance/accessing/toggleShowPackages.st A Nautilus.package/AbstractNautilusUI.class/instance/build ui buttons/buildHierarchyButton.st R Nautilus.package/AbstractNautilusUI.class/instance/build ui buttons/buildToggleButton.st M Nautilus.package/AbstractNautilusUI.class/instance/build ui lists/buildFirstColumn_.st A Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/hierarchyButtonAction.st A Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/hierarchyButtonEnabled.st A Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/hierarchyButtonLabel.st A Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/hierarchyButtonState.st R Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/showByteCodeButtonLabel.st R Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/showClassVarsButtonLabel.st R Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/showInstanceVarsButtonLabel.st R Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/showSourceCodeButtonLabel.st R Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/toggleButtonAction.st R Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/toggleButtonEnabled.st R Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/toggleButtonLabel.st R Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/toggleButtonState.st A Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/toggleShowComment.st A Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/toggleShowFullComment.st A Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/toggleShowGroups.st A Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/toggleShowPackages.st R Nautilus.package/AbstractNautilusUI.class/instance/icon/rebuildIconicButtonFrom_.st M Nautilus.package/AbstractNautilusUI.class/instance/initialization/initialize.st R Nautilus.package/AbstractNautilusUI.class/instance/private/getPackagesList.st R Nautilus.package/AbstractNautilusUI.class/instance/private/getPackagesList2.st R Nautilus.package/AbstractNautilusUI.class/instance/private/instanceLabel.st R Nautilus.package/AbstractNautilusUI.class/instance/private/rootsOfGroup_.st R Nautilus.package/AbstractNautilusUI.class/instance/private/rootsOf_.st R Nautilus.package/Nautilus.class/instance/private/classesInTheSelectedPackage.st R Nautilus.package/NautilusUI.class/instance/events handling/keyPressedOnList2_shifted_.st M Nautilus.package/NautilusUI.class/instance/private/updateOnClassSelection.st M Nautilus.package/PackageTreeNautilusUI.class/instance/accessing/showPackages_.st M Nautilus.package/PackageTreeNautilusUI.class/instance/build ui lists/buildFirstColumn_.st R Nautilus.package/PackageTreeTagNodeModel.class/class/accessing/rootText.st M Ring-Core-Containers.package/RGContainer.class/instance/adding%2Fremoving/addClassNamed_.st M Ring-Core-Containers.package/RGContainer.class/instance/adding%2Fremoving/addTraitNamed_.st M Ring-Core-Containers.package/extension/RGFactory/instance/createNamespaceNamed_.st M Ring-Core-Containers.package/extension/RGFactory/instance/createPackageNamed_.st M Ring-Core-Kernel.package/RGFactory.class/instance/factory-variable/createClassInstanceVariableNamed_.st M Ring-Core-Kernel.package/RGFactory.class/instance/factory-variable/createClassVariableNamed_.st M Ring-Core-Kernel.package/RGFactory.class/instance/factory-variable/createGlobalVariableNamed_.st M Ring-Core-Kernel.package/RGFactory.class/instance/factory-variable/createInstanceVariableNamed_.st M Ring-Core-Kernel.package/RGFactory.class/instance/factory-variable/createInstanceVariableNamed_parent_.st M Ring-Core-Kernel.package/RGFactory.class/instance/factory-variable/createPoolVariableNamed_.st M Ring-Core-Kernel.package/RGFactory.class/instance/factory-variable/createSharedPoolNamed_.st M Ring-Core-Kernel.package/RGFactory.class/instance/factory/createClassNamed_.st M Ring-Core-Kernel.package/RGFactory.class/instance/factory/createClassNamed_subclassOf_.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory/createMetatraitNamed_.st M Ring-Core-Kernel.package/RGFactory.class/instance/factory/createMethodNamed_.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory/createTraitNamed_.st R Ring-Core-Kernel.package/RGFactory.class/instance/private/createInstanceOfClass_named_.st M Ring-Core-Kernel.package/extension/Class/instance/asRingDefinition.st M Ring-Core-Kernel.package/extension/Trait/instance/asRingDefinition.st M Ring-Monticello.package/extension/MCClassDefinition/instance/asRingDefinition.st M Ring-Monticello.package/extension/MCClassTraitDefinition/instance/asRingDefinition.st M Ring-Tests-Containers.package/RGSliceTest.class/instance/testing/testAddingClasses.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testAddingMethods.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testExistingClass.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testNonExistingClass.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testRemovingMethods.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testWithCategory.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testWithClassInstanceVariables.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testWithClassVariables.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testWithComment.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testWithDefaultNamespace.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testWithInstanceVariables.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testWithPoolDictionaries.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testWithProtocols.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testWithSuperclass.st M Ring-Tests-Kernel.package/RGGlobalDefinitionTest.class/instance/testing/testPoolDefinition.st M Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/testing/testExistingMethodWithClass.st M Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/testing/testExtensionMethod.st M Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/testing/testMethodEquality.st M Ring-Tests-Kernel.package/RGTraitDefinitionTest.class/instance/testing/testAddingMethods.st M Ring-Tests-Kernel.package/RGTraitDefinitionTest.class/instance/testing/testExistingTrait.st M Ring-Tests-Kernel.package/RGTraitDefinitionTest.class/instance/testing/testNonExistingClass.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script145.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40145.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Settings-Monticello.package/MCSystemSettings.class/README.md R Settings-Monticello.package/MCSystemSettings.class/class/settings/monticelloSettingsOn_.st R Settings-Monticello.package/MCSystemSettings.class/definition.st Log Message: ----------- 40145 13743 tiny clean in AnnounceMentTests https://pharo.fogbugz.com/f/cases/13743 13739 Nautilus Refactoring 5: intermediate code cleanup (remove unused methods) https://pharo.fogbugz.com/f/cases/13739 13693 Monticello Settings --> move to Monticello https://pharo.fogbugz.com/f/cases/13693 13741 Another small Ring refactoring https://pharo.fogbugz.com/f/cases/13741 http://files.pharo.org/image/40/40145.zip

July 31, 2014

[pharo-project/pharo-core]

by GitHub

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

July 31, 2014

Re: [Pharo-dev] Smalltalkhub not serving any mcz files?

by Max Leske

On 31.07.2014, at 14:01, pieter(a)nagel.co.za wrote: > Hi, > > It seems that www.smalltalkhub.com is not serving up any mcz files > anymore. For example, all of the links from > http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main just > lead to "not found" error pages. > > Same with http://www.smalltalkhub.com/mc/smaass/Pharo3Sounds/main and > http://www.smalltalkhub.com/mc/zeroflag/Teapot/main (projects chosen at > random from www.smalltalkhub.com front page). > > Apologies if this is the wrong list; based on the archives this list seems > to be the place where smalltalkhub errors have been reported in the past. > > Youâre at the right place :) Youâre right, the urls are wrong. Fixable by appending â/main/â to the url befor the .mcz name. Max

July 31, 2014

Smalltalkhub not serving any mcz files?

by pieter＠nagel.co.za

Hi, It seems that www.smalltalkhub.com is not serving up any mcz files anymore. For example, all of the links from http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main just lead to "not found" error pages. Same with http://www.smalltalkhub.com/mc/smaass/Pharo3Sounds/main and http://www.smalltalkhub.com/mc/zeroflag/Teapot/main (projects chosen at random from www.smalltalkhub.com front page). Apologies if this is the wrong list; based on the archives this list seems to be the place where smalltalkhub errors have been reported in the past.

July 31, 2014

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

by Usman Bhatti

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

July 31, 2014

Re: [Pharo-dev] Should nested mutexes work in Pharo 3.0?

by Jan Vrany

On 31/07/14 10:45, Marcel Taeumel wrote: > Hi! :) > > I am playing around with Animations [1] in the Moose 5.0/Pharo 3.0 image > [2]. Nested use of the same mutex seems to freeze the image. Should that > work? No, it should not :-) Use Monitor instead. Jan > > Best, > Marcel > > [1] https://github.com/marceltaeumel/animations > [2] > https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-… > > > > -- > View this message in context: http://forum.world.st/Should-nested-mutexes-work-in-Pharo-3-0-tp4771110.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

July 31, 2014

Should nested mutexes work in Pharo 3.0?

by Marcel Taeumel

Hi! :) I am playing around with Animations [1] in the Moose 5.0/Pharo 3.0 image [2]. Nested use of the same mutex seems to freeze the image. Should that work? Best, Marcel [1] https://github.com/marceltaeumel/animations [2] https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-… -- View this message in context: http://forum.world.st/Should-nested-mutexes-work-in-Pharo-3-0-tp4771110.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 31, 2014

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

by Blondeau Vincent

Yes it is. But I will not do TRMorph allInstances do: #delete In command line every dayâ¦ 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<mailto:vincent.blondeau@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 : [cid:image001.png@01CFACAF.C4370C70] 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<http://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: [cid:image002.png@01CFACAF.C4370C70] 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.

July 31, 2014

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

by Blondeau Vincent

The Eliot VM doesn't comes with libCairo and Roassal doesn't work into. But it's helpful to reopen the image to retrieve the work done ! -----Message d'origine----- De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Hilaire EnvoyÃ© : jeudi 31 juillet 2014 10:54 Ã : pharo-dev(a)lists.pharo.org Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error with Roassal Looks like Cairo can't be loaded. Does the Eliot VM comes with libCairo? Hilaire Le 31/07/2014 16:50, Blondeau Vincent a Ã©crit : > 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 : > > 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: > > 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. -- Dr. Geo - http://drgeo.eu iStoa - http://istao.drgeo.eu 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.

July 31, 2014

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

by Usman Bhatti

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

July 31, 2014