October 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Unwind error during termination

by Goubier Thierry

Le 24/10/2013 16:28, btc(a)openinworld.com a Ã©crit : > ClÃ©ment Bera wrote: >> Ok I have the error too. >> >> Strangely enough, the error is triggered because the third >> BlockClosure>>#on:do: context has 2 temporaries instead of 3. >> >> Igor / Esteban do you have a clue ? Why a context would have less >> temporaries than expected ? Problem from context creation out of the stack ? >> >> I will try to find some time to look at this problem. Though it is not an >> easy one it will take some time to be fixed. >> > > Hi ClÃ©ment, I really appreciate you having a look but perhaps it would > be worthwhile to gather some more use cases before spending too much > time on it - unless the challenge is particularly appealing :) . Partly > I was checking the wider awareness of this particular error. Even though > I've seen it a few times, if no-one else has, then perhaps I should > ensure I'm on the latest VM and see if it occurs again. Then might be a > better time to attack it. I see that error sometimes when debugging failed or buggy tests. I'll try to find a way to reproduce. Thierry > cheers -ben > >> >> 2013/10/24<btc(a)openinworld.com> >> >> >>> ** >>> ClÃ©ment Bera wrote: >>> >>> Hello, >>> >>> I'm interested. >>> >>> Please send me the image in private mail not to overload the mailing list >>> with large attachment. >>> Alternatively, give me a place where I can download it. >>> >>> >>> http://files.openinworld.com/Pharo/PharoLauncher-Unwind-Error.zip >>> >>> The steps to reproduce are: open the image, execute 1halt, close debugger ? >>> >>> >>> There are three debuggers already open. Just close them. The third >>> close generates the error. >>> A confounding factor may be your running this on a different VM. This is >>> mine... >>> >>> http://files.openinworld.com/Pharo/PharoLauncher-Unwind-Error-VM.zip >>> >>> Win32 built on Mar 13 2013 18:49:42 Compiler: 4.6.2 >>> VMMaker versionString git://gitorious.org/cogvm/blessed.git Commit: >>> 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 >>> By: Esteban Lorenzano<estebanlm(a)gmail.com> <estebanlm(a)gmail.com> Jenkins >>> build #14535 >>> NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: >>> a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 >>> NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: >>> a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 >>> >>> The error still occurs if I try the image on the latest VM, but then again >>> the effect may already be in effect. >>> >>> btw, Its not directly causing me pain since I can continue in the image, >>> but still thanks for checking it out for general improvements. >>> >>> cheers -ben >>> >>> Best, >>> >>> >>> >>> 2013/10/22<btc(a)openinworld.com> <btc(a)openinworld.com> >>> >>> ** >>> For a while now, every now and then when closing a debugger I have been >>> getting an "Unwind error during termination" >>> >>> >>> >>> I happened to have saved the image moments before it just occurred again. >>> >From opening that save error can be reliably triggered in three clicks. >>> I can provide this image if anyone is interested in it. >>> >>> cheers -ben >>> >>> >>> >>> >>> >>> >> >> > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Oct. 24, 2013

Re: [Pharo-dev] Startup Preferences: An Alternative

by phil＠highoctane.be

Ah ah yeah sure is cool. Now I was explaining some Seaside stuff to a friend who is doing .Net and he had a hard time grasping the thing. Phil , October 24, 2013, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 24 October 2013 14:42, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> And to save on parenthesis, you could also write >> >> Compiler evaluate: 'http://my.url.with.script.st' asZnUrl retrieveContents. >> >> CodeImporter evaluateString: 'http://my.url.with.script.st' asUrl retrieveContents. >> > this is why i love smalltalk: that you can express highly complex stuff (there's a lot > of stuff happens under the hood) by single line expression. > > Comparing to most examples of C frameworks, where you had to manually allocate buffers, > initialize some data structures, and pass several options and flags here and there, which at the end > does what you need, but floods your mind with hundreds of tiny irrelevant details.. > >> >> With #asUrl and #asZnUrl soon to be 100% the same thing. >> >> On 24 Oct 2013, at 14:32, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> > you mean: >> > >> > CodeImporter evaluateString: (ZnEasy get: 'my-url') contents. >> > >> > :) >> > >> > On Oct 23, 2013, at 11:17 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> > >> >> >> >> On 23 October 2013 20:21, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> This is really cool, is that in the image already ? >> >> What about plain HTTP repos ? >> >> >> >> >> >> indeed, what could be simpler than: >> >> >> >> Compiler evaluate: (ZnEasy get: 'http://my.url.with.script.st') >> >> >> >> and you can, of course place it on github, if you need version control, like: >> >> >> >> https://raw.github.com/pharo-project/pharo-vm/master/codegen-scripts/LoadVM… >> >> >> >> >> >> On 23 Oct 2013, at 20:04, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >> >> >> > philippeback wrote >> >> >> Would be great to have a logout, in order to give images to other people >> >> >> without leaving credentials around. >> >> > >> >> > Done, added to world menu under the individual repo login options >> >> > >> >> > The way the logins work is that a file named .mcconfig is expected in the >> >> > general preferences folder with the format: >> >> > >> >> > [squeaksource] >> >> > user := 'me'. >> >> > password := 'pwd'. >> >> > [squeaksource3] >> >> > user := 'me'. >> >> > password = 'pwd'. >> >> > [smalltalkhub] >> >> > user := 'me'. >> >> > password := 'pwd'. >> >> > >> >> > >> >> > >> >> > ----- >> >> > Cheers, >> >> > Sean >> >> > -- >> >> > View this message in context: http://forum.world.st/Startup-Preferences-An-Alternative-tp4713968p4716686.… >> >> > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> >> > >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> Best regards, >> >> Igor Stasenko. >> > >> >> > > > > -- > Best regards, > Igor Stasenko. -- --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Pharo Consortium Member - http://consortium.pharo.org/ Featured on the Software Process and Measurement Cast - http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller

Oct. 24, 2013

Re: [Pharo-dev] Unwind error during termination

by btc＠openinworld.com

Oct. 24, 2013

Smalltalkhub commit dates broken?

by Stephan Eggermont

Commit dates seem to be wrong. I committed a few packages in Moose/PetitDelphi today, and find them back as 17/05/2013 Stephan

Oct. 24, 2013

Re: [Pharo-dev] Release mails and update summary

by Damien Cassou

On Wed, Oct 23, 2013 at 10:54 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > "Pharo launcher" [1] has the ability to download and run images. It really > helps avoiding chaos on the hard disk and I can only recommend to others > to give it a try. I agree! -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 24, 2013

Re: [Pharo-dev] Use #shouldnt:raise: only with specific errors, or evaluate the given expression directly

by Philippe Marschall

On 24.10.13 15:24, Igor Stasenko wrote: > > > > On 24 October 2013 08:17, Philippe Marschall > <philippe.marschall(a)netcetera.ch > <mailto:philippe.marschall@netcetera.ch>> wrote: > > On 22.10.13 00:08, Camillo Bruni wrote: > > see my long explanation here > https://pharo.fogbugz.com/__default.asp?11876#87218 > <https://pharo.fogbugz.com/default.asp?11876#87218> > it looks unsuspicous until the moment you try understand such a > failing assertion. > > > This isn't moving Pharo foward. This doesn't make the system any > more flexible, adaptable, modular or malleable. This doesn't make > the system any easier to maintain. This doesn't make the system any > smaller, faster, scalable or secure. This doesn't make the system > any easier to maintain. This doesn't make life easier for anybody > developing Pharo or using Pharo. This doesn't improve Pharo in any way. > > This only adds code who's sole purpose is to break people's existing > code. > > If you disagree with such a way of writing tests then the right > solution IMHO is to write a SLint rule. > > > Running SLint over tests? I could agree the working code should be > checked for rules.. but tests? Yes. Test should have the same quality standards as the rest of the code because you'll have to maintain them just the same. Our tests have to be portable like the rest of our code. Cheers Philippe

Oct. 24, 2013

Re: [Pharo-dev] Issue #11876 (Do not allow shouldnt:raise: Error) and Seaside dev. on Pharo 3.0

by Philippe Marschall

On 24.10.13 11:59, Norbert Hartl wrote: > > Am 24.10.2013 um 10:47 schrieb Philippe Marschall > <philippe.marschall(a)netcetera.ch > <mailto:philippe.marschall@netcetera.ch>>: > >> On 24.10.13 08:05, Marcus Denker wrote: >>> >>> On 23 Oct 2013, at 23:07, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr >>> <mailto:stephane.ducasse@inria.fr>> wrote: >>> >>>> >>>>> Hi, >>>>> >>>>> just as info: looks like already fixed Pharo issue #11876 makes >>>>> problem for Seaside in 3.0: >>>>> >>>>> http://lists.squeakfoundation.org/pipermail/seaside-dev/2013-October/005509… >>>>> http://lists.squeakfoundation.org/pipermail/seaside-dev/2013-October/005540… >>>> >>>> >>>> It would be a bit sad that Seaside does not work in Pharo3.0 >>>> I imagine that Philippe is tired. >>>> >>>> I would revert the change and add a rule that check that the >>>> argument of shouldnt:raise: should not be an Error >>>> >>> >>> yes, people are not willing to change code all the timeâ¦ >> >> We are willing to change the code where there is a clear benefit. For >> example it's hard to argue that the new filesystem is an improvement >> over FileDirectory. We have a partically working Spec based UI for the >> servers. We would happily change the walkback to a new context API >> should it fix the bugs in the existing one. However this isn't the >> case with this change. To sole and only purpose of this change is to >> break code. This is what annoys me. >> > Personally I think the new filesystem is way better than the old one. Yeah, I meant it's better. I guess I should proof read my mails more. Cheers Philippe

Oct. 24, 2013

Re: [Pharo-dev] Use #shouldnt:raise: only with specific errors, or evaluate the given expression directly

by Igor Stasenko

On 24 October 2013 08:17, Philippe Marschall < philippe.marschall(a)netcetera.ch> wrote: > On 22.10.13 00:08, Camillo Bruni wrote: > >> see my long explanation here https://pharo.fogbugz.com/** >> default.asp?11876#87218<https://pharo.fogbugz.com/default.asp?11876#87218> >> it looks unsuspicous until the moment you try understand such a failing >> assertion. >> > > This isn't moving Pharo foward. This doesn't make the system any more > flexible, adaptable, modular or malleable. This doesn't make the system any > easier to maintain. This doesn't make the system any smaller, faster, > scalable or secure. This doesn't make the system any easier to maintain. > This doesn't make life easier for anybody developing Pharo or using Pharo. > This doesn't improve Pharo in any way. > > This only adds code who's sole purpose is to break people's existing code. > > If you disagree with such a way of writing tests then the right solution > IMHO is to write a SLint rule. > > Running SLint over tests? I could agree the working code should be checked for rules.. but tests? Useful, to some pedantic souls i guess , but not me :) But anyways, i agree with you, we should not dictate what is 'best' rules and 'how you should do the coding', we shall let people discover own and let them shoot into their own foot, if they insisting to. > Cheers > Philippe > > > -- Best regards, Igor Stasenko.

Oct. 24, 2013

[pharo-project/pharo-core]

by GitHub

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

Oct. 24, 2013

[pharo-project/pharo-core] 9e1723: 30520

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 9e1723ff19630cd7c4ffda1634be0f3200e2ba64 https://github.com/pharo-project/pharo-core/commit/9e1723ff19630cd7c4ffda16… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-24 (Thu, 24 Oct 2013) Changed paths: R Compiler.package/Compiler.class/class/utilities/recompileAllFrom_.st A Kernel.package/Behavior.class/instance/accessing/localSelectors.st M KernelTests.package/BehaviorTest.class/instance/tests/testBehaviorRespectsPolymorphismWithTraitBehavior.st M Morphic-Base.package/MorphTreeMorph.class/instance/column handling/headerBounds.st M Morphic-Base.package/MorphTreeMorph.class/instance/submorphs-add%2Fremove/addMorphsAfter_fromCollection_.st M Morphic-Base.package/MorphTreeNodeMorph.class/instance/accessing/spacerWidth.st M Morphic-Base.package/MorphTreeNodeMorph.class/instance/layout/layoutBounds.st R OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/meta data/ruleCodeCruftLeftInMethodsRuleV1FalsePositive.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script175.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30520.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30520 11982 testExplicitRequirementMethodsShouldBeImp... https://pharo.fogbugz.com/f/cases/11982 11991 remove #recompileAllFrom: https://pharo.fogbugz.com/f/cases/11991 11988 MorphTreeMorph incorrect bounds https://pharo.fogbugz.com/f/cases/11988 http://files.pharo.org/image/30/30520.zip

Oct. 24, 2013