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

Re: [Pharo-dev] where the...

by Eliot Miranda

never mind... On Thu, Jul 31, 2014 at 1:36 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > *&^% do I find build artifacts for > https://ci.inria.fr/pharo/job/Pharo-4.0/lastSuccessfulBuild/? There's no > pointer to an image/changes combo I can see. > -- > Aloha, > Eliot > -- best, Eliot

July 31, 2014

where the...

by Eliot Miranda

*&^% do I find build artifacts for https://ci.inria.fr/pharo/job/Pharo-4.0/lastSuccessfulBuild/? There's no pointer to an image/changes combo I can see. -- Aloha, Eliot

July 31, 2014

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

by Alexandre Bergel

Ohâ¦ We should not only check the session for the surface? Wowâ¦ this is rather heavy then... Alexandre On Jul 31, 2014, at 5:03 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > Is is not that easy :) > TRMorph already checks for a new session. > TRCanvas not, but could be done the same way - maybe. It is difficult as TRCanvas are shared by different objects. > And it is more difficult for TRShape. > > I know Igors argument against a session management in Athens for > recreating cairo resources on image start up. It is not the job of Athens. > > But it is a bit different for resources created through Athens core api. > How can the user (TRShape for example) know, that a path created by > an Athens surface referes to an external resource? > > The attached changeset implements a simple check for TRCanvas and > resets paths if the canvas changes. This solves the crash on > image start up.But it is not a good solution. > > > > > 2014-07-31 16:23 GMT+02:00 Igor Stasenko <siguctua(a)gmail.com>: > The recipe is simple: isolate the code in your application in a way that if certain feature not available (line nativeboost), it won't put your image into endless exception throwing loop. > > > That's another story. The projects I have seen, using athens, do this with an explicit use > on AthensCairoSurface. Is there already a way to instantiate an AthensSurface depending on the > available libraries? And AthensBalloon and AthensCairo don't differ only in rendering quality, so there > is no real fallback option. > > > > > > On 31 July 2014 16:09, Alexandre Bergel <alexandre.bergel(a)me.com> 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 > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > -- > Best regards, > Igor Stasenko. > > <fix_trachel_athens_session.cs>_______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 31, 2014

Re: [Pharo-dev] [Esug-list] Android VM Status

by Jean Baptiste Arnaud

Couple a things still to do: If you want jannik when I will have my first Beta, I give a version, but for a jenkins I will need some work on the configuration generator. On 31 Jul 2014, at 21:09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Well done JB! > This is great to see this fork realigned and to identify the changes. > Thanks for your constant push. > > Stef > > On 31 Jul 2014, at 16:33, Jean Baptiste Arnaud <jbaptiste.arnaud(a)gmail.com> wrote: > >> Hi, >> I made some advance on Android StackVM (using the standard unix sources). >> >> :-) >> >> Last Unix Stack VM with last 40Pharo image (a little bit modified cause au no-NativeBoost and some constraint from the Android Sandboxing ). >> Content: >> - Somes lines of code change in SqUnixMain.c (using if define android, but not a lot, just for allow to load external lib :-). >> - 1 communication with java / C files, (will be split in two or three file one for printing debugging, one or two for core). >> - 1 external graphical plugins. vm-display-android, really short but for android, because the rendering is done by Android. >> >> >> All these plugins are includes (not deeply tested yet, but most of them should work): >> AndroidPlugin (for now I just allow to do debug printing from the image in the logCat), BitBltPlugin, B2DPlugin, BMPReadWriterPlugin, CroquetPlugin, DSAPrims, FFTPlugin, FileCopyPlugin, FilePlugin, FloatArrayPlugin, FloatMathPlugin, JoystickTabletPlugin, JPEGReaderPlugin, LargeIntegers,Matrix2x3Plugin, RePlugin, SecurityPlugin, JPEGReadWriter2Plugin, SocketPlugin, MiscPrimitivePlugin, ZipPlugin. >> >> And a lot of debugging. :-). >> >> Next step: >> - fixing all the Event. >> - Do a real Configuration generator to be able to generate from Jenkins using the NDK. >> - Then merge in the main PharoVM Git :-). >> - Do a configuration to allow older pharo image to run on it. Maybe older but I not convince yet. >> - And obviously a job for allow anybody to create a android package with it's own image :-) >> >> See you soon :-) >> >> <IMG_3934.jpeg> >> >> Best Regards >> Dr Arnaud >> jbaptiste.arnaud(a)gmail.com >> >> >> >> >> >> >> >> >> _______________________________________________ >> Esug-list mailing list >> Esug-list(a)lists.esug.org >> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org Best Regards Dr Arnaud jbaptiste.arnaud(a)gmail.com

July 31, 2014

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

by Nicolai Hess

Is is not that easy :) TRMorph already checks for a new session. TRCanvas not, but could be done the same way - maybe. It is difficult as TRCanvas are shared by different objects. And it is more difficult for TRShape. I know Igors argument against a session management in Athens for recreating cairo resources on image start up. It is not the job of Athens. But it is a bit different for resources created through Athens core api. How can the user (TRShape for example) know, that a path created by an Athens surface referes to an external resource? The attached changeset implements a simple check for TRCanvas and resets paths if the canvas changes. This solves the crash on image start up.But it is not a good solution. 2014-07-31 16:23 GMT+02:00 Igor Stasenko <siguctua(a)gmail.com>: > The recipe is simple: isolate the code in your application in a way that > if certain feature not available (line nativeboost), it won't put your > image into endless exception throwing loop. > > That's another story. The projects I have seen, using athens, do this with an explicit use on AthensCairoSurface. Is there already a way to instantiate an AthensSurface depending on the available libraries? And AthensBalloon and AthensCairo don't differ only in rendering quality, so there is no real fallback option. > > On 31 July 2014 16:09, Alexandre Bergel <alexandre.bergel(a)me.com> 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 >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> > > > -- > Best regards, > Igor Stasenko. >

July 31, 2014

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

by kilon alios

yeap i can confirm that too On Fri, Aug 1, 2014 at 12:00 AM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > Pieter, note that for some reason (?) gmail identified your mail as > phishing... > > > 2014-07-31 14:09 GMT+02:00 Max Leske <maxleske(a)gmail.com>: > > >> 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

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

by Nicolas Cellier

Pieter, note that for some reason (?) gmail identified your mail as phishing... 2014-07-31 14:09 GMT+02:00 Max Leske <maxleske(a)gmail.com>: > > 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

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

by stepharo

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

July 31, 2014

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

by stepharo

You should report it to the Pharo mailing-list with a reproducible case because else it will get unnoticed. Not all the Pharo people are reading the Moose mailing-list. Stef On 31/7/14 11:17, Blondeau Vincent wrote: > > 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 : > > 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: > > 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 stepharo

vincent you can take an image/change copy your change as the change of the new image and do recovery last changes and you get all your changes back. Now before concluding that this is pharo's fault... we should check cairo and roassal's athens usage. Stef On 31/7/14 10:50, Blondeau Vincent 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