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

could you try to run...

by StÃ©phane Ducasse

curl get.pharo.org/30+vmLatest | bash Load Unreloader latest from Pharo/SystemConfigurations Close all Nautilus save image :) run UnReloader new unload Iâm curious know whether it crashes the VM. Stef

Jan. 5, 2014

Re: [Pharo-dev] issue 12506 Vm crashes vm when testing updates [A-L]

by StÃ©phane Ducasse

Marcus I could not get it crashed with the latest vm and latest image. Now Iâm confident that on linux it should crash. Pavel? could you try? I will ask damien. Stef > I tried to take the latest + latestVM and run my unreloader and now it never finishes but no crash. > I have to investigate. > > Stef > > On 05 Jan 2014, at 12:51, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 05 Jan 2014, at 12:37, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >>> But what of these changes were responsible for that you have to >>> have the sources file in your vm directory? (and only in 30664 and 30665!) >>> >> >> Or maybe because I did do a âSmalltalk cleanUpâ before uploading the recompiled image? >> >>> What are the exact steps for recompiling the image, you did? (just OpalCompiler recompileAll) >>> >>> >>> >>> 2014/1/5 Marcus Denker <marcus.denker(a)inria.fr> >>> >>> On 05 Jan 2014, at 12:08, Nicolai Hess <nicolaihess(a)web.de> wrote: >>> >>>> My observations for issue 12506 >>>> >>>> - I can reproduce it on linux >>>> - segfault happens in primtiveNextInstance >>>> - tests A-L worked in 30663 >>>> - tests A-L segfault since 30664 >>>> - doesn't segfaults anymore if you open the image, change some code, save and close the image >>>> - it segfaults if you just run a subset of the A-L tests >>>> (pharo --nodisplay Pharo.image test --junit-xml-output 'FileSystem-Tests-Core' 'FreeTypeTests' 'FileSystem-Tests-Disk' 'FuelTests' 'FileSystem-Tests-Memory' 'KernelTests') >>>> - this "fail"-subset is different for the different images (30664, 30665, ...) >>>> - it does not segfault if you omit the junit-xml-output option >>>> >>> >>> -> Opal Regression Tests do run all tests (after recompiling) â> no problem ever >>> -> Monkey runs all tests for all âFix review neededâ â> no problem >>> >>>> And someone knows what happened with the image between version >>>> 30663 and 30666, because only >>>> 30664 and 30665 need the PharoV20.sources in the same directory as the VM, >>>> for all other versions it suffices if the sources are where the image file is. >>>> (Same as in http://forum.world.st/pharo-3-0-image-td4732890.html) >>>> >>> >>> These are the changes: >>> >>> 30663: >>> full diff: https://github.com/pharo-project/pharo-core/commit/c6adb033b0a42acbfe451955… >>> >>> >>> 12510 NautilusHistory entry for class methods loads instance methods >>> https://pharo.fogbugz.com/f/cases/12510 >>> >>> 12502 FileList MNU FileSystemPermission>><= >>> https://pharo.fogbugz.com/f/cases/12502 >>> >>> 12429 MessageBrowser loses changes >>> https://pharo.fogbugz.com/f/cases/12429 >>> >>> 12451 Error on Browse Full in Nautilus from class in group view >>> https://pharo.fogbugz.com/f/cases/12451 >>> >>> 30664 >>> full diff: https://github.com/pharo-project/pharo-core/commit/b84651feddc39d4336329e22… >>> >>> >>> 12517 SystemNavigation methodHierarchyBrowserForClass:selector: discards package information >>> https://pharo.fogbugz.com/f/cases/12517 >>> >>> 12476 Undeclared >>> https://pharo.fogbugz.com/f/cases/12476 >>> (remove Athens Tutorial as it introduces an Undeclared and was not in the image before) >>> >>> (in addition, I downloaded the image, recompiled and uploaded a new seed image as latest.zip). >>> >>> >>> 30665 >>> full diff: https://mail.google.com/mail/u/0/#search/30665/1435265c4bcdb3c2 >>> >>> - do not call #cleanUpForRelease on update >>> >>> (to check if this was the reason for the crash, it was not) >>> >>> >>> >> >

Jan. 5, 2014

Re: [Pharo-dev] what happened with RectangleMorph?

by StÃ©phane Ducasse

> grrrr > > one of this days we should write the âmetacello compendiumâ, and create agreements in ways to do things :P + 1 I would love to have a list of metacello patterns. Stef > > > > On 05 Jan 2014, at 12:41, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> I added a development version to point to the baseline :) >> >> Cheers, >> Doru >> >> >> On Sun, Jan 5, 2014 at 12:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> and you added a baseline 3.2 but not a version (not cool, doru, not cool :) >> >> On 05 Jan 2014, at 12:07, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> MAElementRow was still depending on RectangleMorph. >>> But it was more a problem of the #stable release: it was not updated. >>> >>> Esteban >>> >>> On 05 Jan 2014, at 11:42, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>>> Hi Esteban, >>>> >>>> I fixed this issue in Magritte-Morph a long time ago when we ported Moose to Pharo 3.0. What exactly is the issue? >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> >>>> >>>> On Sun, Jan 5, 2014 at 11:34 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>> On 05 Jan 2014, at 11:33, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>>> >>>> > >>>> > On 05 Jan 2014, at 11:30, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> > >>>> >> â¦ is not there anymore. >>>> >> And Magritte-Morph requires it :( >>>> >> >>>> >> my guess: I was another victim of Stef compulsion of giving us a better and cleaning system :) >>>> >> >>>> > >>>> > The thing was that it had no state nor behaviour different to Morphâ¦ everywhere where it was used >>>> > (and especially subclassed), one could just put Morph. One concept lessâ¦ >>>> >>>> coolâ¦ :) >>>> >>>> > >>>> >> But it should be replaced by what? >>>> >> >>>> > Morph >>>> > >>>> > Marcus >>>> > >>>> > >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Every thing has its own flow" >>> >> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >

Jan. 5, 2014

Re: [Pharo-dev] [Moose-dev] Concerts of Iron Maiden Analyzed

by StÃ©phane Ducasse

On 05 Jan 2014, at 15:26, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> alex >> >> did you see the idea I send to use a nearly similar âlinearâ block based aligned on the left visualziaion >> to display procedural code? > > Not sure what you mean. > Any example? xxxx xxxx fgfg gggg gggg gggg hhhh hhhh hhhh hhhhh And we could have links between them in a nice way. Imagine that hhhh is a procedure and that the arrows are the calls it does. > > Alexandre > >> >> On 05 Jan 2014, at 00:40, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> >>> Load Roassal to enjoy Dowser, a relational tower visualization. >>> The following expression relates the year and locations of Iron Maidenâs concerts: >>> RODowserExample new example10 >>> >>> <Screen Shot 2014-01-04 at 8.40.07 PM.png> >>> >>> More Screenshots available on: >>> >>> https://www.facebook.com/media/set/?set=a.567893596630575.1073741840.340543… >>> >>> Thanks Ricardo for this excellent piece of work! >>> >>> Cheers, >>> Alexandre >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >> >> _______________________________________________ >> 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 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Jan. 5, 2014

Re: [Pharo-dev] FogBugz (Case [Issue]12566) Kernel - Added Behavior>>#dependentClasses

by Benjamin

If you check the report, you see your code broke a test. According to the test name, I would say that your method should be added to TBehavior, and not Behavior directly. :) Ben On 05 Jan 2014, at 09:56, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > I have proposed a method Behavior>>dependentClasses, but apparently the Monkey is not really happy about it. I doubt the error in the generated report stems from this change. > https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/6734//artifact/vali… > > No idea how to proceed from there. > > Cheers, > Alexandre > > On Jan 5, 2014, at 6:42 AM, Pharo Issue Tracker <do-not-reply(a)pharo.fogbugz.com> wrote: > >> >> Ulysse The Galactic Monkey From Outer Spaceedited Case 12566: Added Behavior>>#dependentClasses: >> >> Bug in Kernel: 1. Pharo Image >> >> Issue Validation Failed: https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/6734//artifact/vali… >> Errors: 1 | Warnings: 1 | >> >> Status changed: >> Resolved (Monkey is checking) Work Needed (Failing Test) >> >> Priority: 5 â Fix If Time Status: Work Needed (Failing Test) >> Assigned to: Alexandre Bergel Milestone: Pharo3.0 >> >> >> Go to Case >> >> Don't want FogBugz notifications anymore? Update your preferences. >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Jan. 5, 2014

[pharo-project/pharo-core]

by GitHub

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

Jan. 5, 2014

[pharo-project/pharo-core] c01a1a: 30672

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: c01a1a1b7aaeefa47df79071a6b67052f8a735b0 https://github.com/pharo-project/pharo-core/commit/c01a1a1b7aaeefa47df79071… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-05 (Sun, 05 Jan 2014) Changed paths: M Kernel.package/CompiledMethod.class/instance/literals/literalStrings.st M Kernel.package/CompiledMethod.class/instance/literals/sendsSelector_.st M Komitter.package/extension/MCPatch/instance/initializeWithTarget_.st M NewList.package/NewList.class/instance/protocol/cacheAt_.st M NewList.package/NewListAdapter.class/instance/accessing/separatorSelector.st M NewList.package/NewListAdapter.class/instance/list protocol/separatorAfter_at_.st M OpalCompiler-Core.package/OpalCompiler.class/instance/public access/evaluate.st A Polymorph-TaskbarIcons.package/extension/MorphicWindowAdapter/instance/taskbarIcon.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script325.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30672.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30672 12571 #evaluate should always #generateWithSource https://pharo.fogbugz.com/f/cases/12571 12562 NewList separatorAt bug fix https://pharo.fogbugz.com/f/cases/12562 12556 debugger is not showing correct icon in taskbar https://pharo.fogbugz.com/f/cases/12556 12563 Comments in CompiledMethod https://pharo.fogbugz.com/f/cases/12563 12564 Error in #initializeWithTarget: https://pharo.fogbugz.com/f/cases/12564 http://files.pharo.org/image/30/30672.zip

Jan. 5, 2014

Re: [Pharo-dev] what happened with RectangleMorph?

by Esteban Lorenzano

On 05 Jan 2014, at 12:51, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > > On Sun, Jan 5, 2014 at 12:44 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > anyway, I added a 3.2 version, so I can reference it in my projects > > Thanks. > > (is *really* not good to reference to a baseline of an external project in your ownâ¦ that just leads to a lot of pain :) > > Not true. Moose is developed on the latest of Pharo, latest of Magritte, latest of PetitParser etc. For custom analysis purposes, my code runs on the latest of Moose. And it works. In fact, with this setup we can spot problems sooner than in any other environment exactly because. And, contrary to the expectations, we can react to these problems faster and cheaper, too. the fact that moose is a complex project that has many subprojects associated that has to be updated frequently makes a case for using bleeding edge *in your case*. But common usage is not like that: common usage is you start a project and want to rely in stable versions of other artefacts you use. the standard should be for common usage, not special casesâ¦ and btw, we probably would need a special way of handling âsubprojectsâ, with special semantics (like âfollowing symbolic versionâ or something that is able to load #stable, #development, etc. also in subprojects). something like #subproject:with: instead the current one that does not allows the subtle difference between external dependence and internal submodule. Esteban > > I will say it again: in our environment, in most cases it is better to stay on top of the latest baseline, than stuck on some previous version. The incremental choice of going from hardcoded version to hardcoded version does not scale for our tools. It can work for Pharo because it is at the bottom of the chain. but as you go up, the problem explodes exponentially. > > Doru > > > Esteban > > > On 05 Jan 2014, at 12:42, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> grrrr >> >> one of this days we should write the âmetacello compendiumâ, and create agreements in ways to do things :P >> >> >> >> On 05 Jan 2014, at 12:41, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> I added a development version to point to the baseline :) >>> >>> Cheers, >>> Doru >>> >>> >>> On Sun, Jan 5, 2014 at 12:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> and you added a baseline 3.2 but not a version (not cool, doru, not cool :) >>> >>> On 05 Jan 2014, at 12:07, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>>> MAElementRow was still depending on RectangleMorph. >>>> But it was more a problem of the #stable release: it was not updated. >>>> >>>> Esteban >>>> >>>> On 05 Jan 2014, at 11:42, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>>> Hi Esteban, >>>>> >>>>> I fixed this issue in Magritte-Morph a long time ago when we ported Moose to Pharo 3.0. What exactly is the issue? >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>> >>>>> >>>>> On Sun, Jan 5, 2014 at 11:34 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>>> >>>>> On 05 Jan 2014, at 11:33, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>>>> >>>>> > >>>>> > On 05 Jan 2014, at 11:30, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>>> > >>>>> >> â¦ is not there anymore. >>>>> >> And Magritte-Morph requires it :( >>>>> >> >>>>> >> my guess: I was another victim of Stef compulsion of giving us a better and cleaning system :) >>>>> >> >>>>> > >>>>> > The thing was that it had no state nor behaviour different to Morphâ¦ everywhere where it was used >>>>> > (and especially subclassed), one could just put Morph. One concept lessâ¦ >>>>> >>>>> coolâ¦ :) >>>>> >>>>> > >>>>> >> But it should be replaced by what? >>>>> >> >>>>> > Morph >>>>> > >>>>> > Marcus >>>>> > >>>>> > >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "Every thing has its own flow" >>>> >>> >>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >> > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Jan. 5, 2014

Re: [Pharo-dev] issue 12506 Vm crashes vm when testing updates [A-L]

by StÃ©phane Ducasse

I tried to take the latest + latestVM and run my unreloader and now it never finishes but no crash. I have to investigate. Stef On 05 Jan 2014, at 12:51, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 05 Jan 2014, at 12:37, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> But what of these changes were responsible for that you have to >> have the sources file in your vm directory? (and only in 30664 and 30665!) >> > > Or maybe because I did do a âSmalltalk cleanUpâ before uploading the recompiled image? > >> What are the exact steps for recompiling the image, you did? (just OpalCompiler recompileAll) >> >> >> >> 2014/1/5 Marcus Denker <marcus.denker(a)inria.fr> >> >> On 05 Jan 2014, at 12:08, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >>> My observations for issue 12506 >>> >>> - I can reproduce it on linux >>> - segfault happens in primtiveNextInstance >>> - tests A-L worked in 30663 >>> - tests A-L segfault since 30664 >>> - doesn't segfaults anymore if you open the image, change some code, save and close the image >>> - it segfaults if you just run a subset of the A-L tests >>> (pharo --nodisplay Pharo.image test --junit-xml-output 'FileSystem-Tests-Core' 'FreeTypeTests' 'FileSystem-Tests-Disk' 'FuelTests' 'FileSystem-Tests-Memory' 'KernelTests') >>> - this "fail"-subset is different for the different images (30664, 30665, ...) >>> - it does not segfault if you omit the junit-xml-output option >>> >> >> -> Opal Regression Tests do run all tests (after recompiling) â> no problem ever >> -> Monkey runs all tests for all âFix review neededâ â> no problem >> >>> And someone knows what happened with the image between version >>> 30663 and 30666, because only >>> 30664 and 30665 need the PharoV20.sources in the same directory as the VM, >>> for all other versions it suffices if the sources are where the image file is. >>> (Same as in http://forum.world.st/pharo-3-0-image-td4732890.html) >>> >> >> These are the changes: >> >> 30663: >> full diff: https://github.com/pharo-project/pharo-core/commit/c6adb033b0a42acbfe451955… >> >> >> 12510 NautilusHistory entry for class methods loads instance methods >> https://pharo.fogbugz.com/f/cases/12510 >> >> 12502 FileList MNU FileSystemPermission>><= >> https://pharo.fogbugz.com/f/cases/12502 >> >> 12429 MessageBrowser loses changes >> https://pharo.fogbugz.com/f/cases/12429 >> >> 12451 Error on Browse Full in Nautilus from class in group view >> https://pharo.fogbugz.com/f/cases/12451 >> >> 30664 >> full diff: https://github.com/pharo-project/pharo-core/commit/b84651feddc39d4336329e22… >> >> >> 12517 SystemNavigation methodHierarchyBrowserForClass:selector: discards package information >> https://pharo.fogbugz.com/f/cases/12517 >> >> 12476 Undeclared >> https://pharo.fogbugz.com/f/cases/12476 >> (remove Athens Tutorial as it introduces an Undeclared and was not in the image before) >> >> (in addition, I downloaded the image, recompiled and uploaded a new seed image as latest.zip). >> >> >> 30665 >> full diff: https://mail.google.com/mail/u/0/#search/30665/1435265c4bcdb3c2 >> >> - do not call #cleanUpForRelease on update >> >> (to check if this was the reason for the crash, it was not) >> >> >> >

Jan. 5, 2014

Re: [Pharo-dev] [Moose-dev] Concerts of Iron Maiden Analyzed

by Alexandre Bergel

> alex > > did you see the idea I send to use a nearly similar âlinearâ block based aligned on the left visualziaion > to display procedural code? Not sure what you mean. Any example? Alexandre > > On 05 Jan 2014, at 00:40, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> Load Roassal to enjoy Dowser, a relational tower visualization. >> The following expression relates the year and locations of Iron Maidenâs concerts: >> RODowserExample new example10 >> >> <Screen Shot 2014-01-04 at 8.40.07 PM.png> >> >> More Screenshots available on: >> >> https://www.facebook.com/media/set/?set=a.567893596630575.1073741840.340543… >> >> Thanks Ricardo for this excellent piece of work! >> >> Cheers, >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 5, 2014