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

Re: [Pharo-dev] Pharo is cool

by Norbert Hartl

Am 26.02.2014 um 14:38 schrieb Mariano Martinez Peck <marianopeck(a)gmail.com>: > Just be careful 2: "I switched one of my servers to dump to stack with fuel to disk if an exception occurs. " > Once it happened to me the stack I was taking for serializing an error was too big. Too big because it even reached the UI. The UI has lots of sensible objects that change quite frequently. So my graph to serialize was big and the graph changed quite frequently. Result: Fuel throwing error because the graph to serialize changed while being serialized. Oh...exception? Fuel out exception! exception. Oh exception? ... > Good point, thanks! > So yeah..the fact that Fuel was throwing an error causes a loop so be careful of that as well. > If the serialization fails I just consider it an unrecoverable error and proceed. I will add a logging message for that case so I can at least so when something does not working while fueling out the stack. thanks, Norbert > > > On Wed, Feb 26, 2014 at 10:28 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 26.02.2014 um 14:19 schrieb Max Leske <maxleske(a)gmail.com>: > > > Cool! :) > > > > Just be careful: if youâre using a large model the stack can blow up your image with a low space warning / make it inresponsive (because the stack referenes your model and boom, pretty much all of your instances will becom serialized). > > > Yes, I know. But that would be a problem anyway. I think I have time. In the fuel files are 8 (!) contexts. :) > > Norbert > > > FYI weâre actively working on pruning of the serialization graph to solve this. > > > > Max > > > > > > On 26.02.2014, at 14:01, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> The best smalltalk/pharo moments you get if you try things you want to have just in order to see they are already there. > >> > >> Today FileBrowser. > >> I switched one of my servers to dump to stack with fuel to disk if an exception occurs. Today I copied the files from the server to my local machine and opened a workspace starting to write an expression to open them. Then I thought it would be cool if I could use the file browser for it. So I opened it and navigated to the directory with the fuel filesâ¦et voilÃ â¦as soon as I clicked on a fuel file a button âmaterializeâ appeared which showed the stack from the server right away. > >> > >> Just brilliant! Well done! > >> > >> Norbert > > > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com

Feb. 26, 2014

Re: [Pharo-dev] Pharo 3.0 on Windows 8.1

by btc＠openinworld.com

Feb. 26, 2014

Re: [Pharo-dev] expected failures

by btc＠openinworld.com

Feb. 26, 2014

Re: [Pharo-dev] Pharo is cool

by Sebastian Sastre

interesting So far Iâm using the sringify-ed walkbacks in emails, but (if the materializable dump isnât too big) it would definitively be cool to have it. Made me think, thanks for sharing Norbert & friends On Feb 26, 2014, at 11:31 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > Here the code operates on a shared queue > > EventDispatcher>>#consumeQueue > | block | > [ true ] whileTrue: [ > block := queue next. > [ block value ] > on: Error > do: [ :err | > self serializeStackFor: err. > Log error: 'block execution failed. stack saved' ] ] > > EventDispatcher>>#serializeStackFor: anError > [ FuelOutStackDebugAction > serializeTestFailureContext: anError signalerContext > toFileNamed: 'Stack-', (DateAndTime now printString),'.fuel' ] > on: Error > do: [:err| "simply continue...â ] > > Norbert > > > Am 26.02.2014 um 14:40 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com>: > >> Pharo is Cool. Definitely. >> >> How do you set up the "fuel dump"? >> >> This morning I woke up with a "out of memory" crash (the first crash >> in two months), and going through the .log file didn't help much. >> >> Regards! >> >> >> Esteban A. Maringolo >> >> >> 2014-02-26 10:01 GMT-03:00 Norbert Hartl <norbert(a)hartl.name>: >>> The best smalltalk/pharo moments you get if you try things you want to have just in order to see they are already there. >>> >>> Today FileBrowser. >>> I switched one of my servers to dump to stack with fuel to disk if an exception occurs. Today I copied the files from the server to my local machine and opened a workspace starting to write an expression to open them. Then I thought it would be cool if I could use the file browser for it. So I opened it and navigated to the directory with the fuel files...et voilÃ ...as soon as I clicked on a fuel file a button "materialize" appeared which showed the stack from the server right away. >>> >>> Just brilliant! Well done! >>> >>> Norbert >> > >

Feb. 26, 2014

Re: [Pharo-dev] Stepping through with GLORP Proxies

by Eliot Miranda

Hi Esteban, find attached. Let me know of any problems. On Wed, Feb 26, 2014 at 8:32 AM, Esteban A. Maringolo <emaringolo(a)gmail.com>wrote: > Hi Eliot, > > > 2013-11-30 18:30 GMT-03:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > > On Fri, Nov 29, 2013 at 2:22 PM, Esteban A. Maringolo < > emaringolo(a)gmail.com> > > wrote: > >> 2013/11/29 Eliot Miranda <eliot.miranda(a)gmail.com>: > > >> > I'll either prepare a change set or submit. It'll get done. > > >> I can continue stepping into until the change is ready. > > >> Please make it compatible with Pharo 2 (whatever that means in term of > >> code) :) > > > > > > OK, the code is now in Squeak trunk. What image should I use to > integrate > > into Pharo 2? A url please... > > I'm coming back late to this. Because the change wasn't integrated in > Pharo 2. > > Do you have the changeset applied to Squeak Trunk? I'd like to reapply > it in my Pharo 2 image (at my own risk). > Can you send it to may email address? > > Thank you! > > Esteban A. Maringolo > > -- best, Eliot

Feb. 26, 2014

Re: [Pharo-dev] access to CI debug info Re: test failures in downloaded image 30733

by Max Leske

On 26.02.2014, at 17:47, btc(a)openInWorld.com wrote: > Thanks for that info Max. I can see "Files to archive" in the PharoLauncher configuration that I have access to. I don't have access to the configuration of Pharo-3.0-Issue-Validator to check, but I guess it should have an entry... > **/*/*.fuel > to gather fuel files from the subdirectories of the workspace. Thatâs right. Althoug I think that one â/*â is enough (the double asterisk should take care of subdirectories. see http://ant.apache.org/manual/Types/fileset.html) > > I have observed from running Pharo-3.0-Issue-Tracker-Image locally that Fuel files are created, that on the build server would located as follows... > /builds/workspace/Pharo-3.0-Issue-Validator/3570607022163494/Pharo-3.-2.0.fuel Cool that they are being generated, not so cool that nobody knew :) > > cheers -ben > > Max Leske wrote: >> >> Take a look at the Fuel job. Just put the file into the working directory (same directory as the image is in) and add a rule to archive Fuel files: **/*.fuel >> >> >> On 25.02.2014, at 17:35, btc(a)openInWorld.com wrote: >> >>> btc(a)openinworld.com wrote: >>>> >>>> btc(a)openinworld.com wrote: >>>>> >>>>> Marcus Denker wrote: >>>>>> >>>>>> >>>>>> On the ci server this is already done: failing tests are serialise with Fuel for debugging. In addition, the image is save and can be downloaded (in the state after the test run). >>>>> >>>> How do I find the fuel files and saved image for this validation report? >>>> https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/11185//artifact/val… >>> >>> Hi Camillo, >>> >>> I am interested by your comment on Case 12957 that "I think we can/should add this code to the standard CI project" >>> regarding my ImageWorker hack to try getting hold of the test failure fuel file. What was it you liked? >>> >>> Its not suitable for integration in its current form since its a very specific hack hardcoding the target folder, that would leave rubbish on the CI server if I didn't pay attention to manually clean up afterward. Also getting the fuel file back to my local machine is awkward using scp to bounce a copy through the inria ssh gateway. Ideally the fuel file would just end up as an artifact of the Jenkins job. What needs doing? I'd be interested in helping out - though I wouldn't want to risk breaking anything prior to Pharo 3 release. >>> >>> cheers -ben >> >

Feb. 26, 2014

Re: [Pharo-dev] New methods for the String class

by phil＠highoctane.be

Which Ruby guru an Python guru is going to give it a shot? [I am a Tcl guy... hey, that's an everything is a string language... ] Oh well, I started something: http://www.smalltalkhub.com/#!/~philippeback/StringTclShim So, who is taking StringRubyShim and StringPythonShim :-p ? Phil On Wed, Feb 26, 2014 at 5:09 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > > On 2014-02-26, at 03:53, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> > wrote: > > > > > > > > > 2014-02-25 8:49 GMT-03:00 phil(a)highoctane.be <phil(a)highoctane.be>: > > Yes but... in Pharo strings are collections and a ton of things can be > done with collections already. > > Other languages have more "basic" strings and are cutting them in all > ways possible but not as collections. > > > > things like detect, inject etc are not really in the repertoire of other > languages. Okay, there are chop, split, ... but these are pretty basic > things. > > > > Why not have a test suite with a test for demonstrating how to do these > things with the platform we do have? > > > > e.g. testChomp, testSplit, ...all put in a Tests-Strings-RubyStyle or > Tests-Strings-PythonStyle packages? > > > > And like there are Seaside-Pharo-XXX packages, why not a > String-Ruby-XXXX thing ? > > > > > > Yes, that is a really good idea. > > indeed, we can do it in two steps: > > 1. create the ruby / pythonic compatibility packages (blindly ignoring any > pharo conventions) > 2. see which methods (if any) actually make sense to steal >

Feb. 26, 2014

Re: [Pharo-dev] access to CI debug info Re: test failures in downloaded image 30733

by btc＠openinworld.com

Feb. 26, 2014

Re: [Pharo-dev] In Praise of Small Commits | Dr Dobb's

by Pharo4Stef

+1 000000 S On 26 Feb 2014, at 09:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > http://www.drdobbs.com/architecture-and-design/in-praise-of-small-commits/2… > > << With smaller commits, teams accelerate code reviews and builds, while shrinking the delay between committing and feedback. That's a lot of payback for a simple practice. >> > > From an integration standpoint, I love small and clean Slices. > > Sven > > > >

Feb. 26, 2014

Re: [Pharo-dev] Stepping through with GLORP Proxies

by Esteban A. Maringolo

Hi Eliot, 2013-11-30 18:30 GMT-03:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > On Fri, Nov 29, 2013 at 2:22 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> > wrote: >> 2013/11/29 Eliot Miranda <eliot.miranda(a)gmail.com>: >> > I'll either prepare a change set or submit. It'll get done. >> I can continue stepping into until the change is ready. >> Please make it compatible with Pharo 2 (whatever that means in term of >> code) :) > > > OK, the code is now in Squeak trunk. What image should I use to integrate > into Pharo 2? A url please... I'm coming back late to this. Because the change wasn't integrated in Pharo 2. Do you have the changeset applied to Squeak Trunk? I'd like to reapply it in my Pharo 2 image (at my own risk). Can you send it to may email address? Thank you! Esteban A. Maringolo

Feb. 26, 2014