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

Re: [Pharo-dev] -= First Visualization Contest with Roassal =-

by Tudor Girba

Great idea! Doru On Fri, Aug 23, 2013 at 8:31 AM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > Dear colleagues and friends, > > We are happy to announce the First Visualization Contest with Roassal. > > What can I win? > - 150 euros, sponsored by ObjectProfile > - a Ã¼ber-cool ObjectProfile T-shirt and some wonderful stickers > - maximum publicity of your work > - a nice award certificate, delivered during ESUG > > How can I win? > - you have to produce a visualization with Roassal. You can use the Pharo, > VisualWorks or VAST version of Roassal. Here is an example of what we > expect http://bit.ly/sunburstDemo > - making a video is mandatory. The video will weight the most in our > decision. The video could be of any length and has to include your name and > say that is was made (partly or completely) with Roassal. No need to talk, > just show off! > - making your code available and easy to install will help you get more > points > > How can I submit? > - send the links of your video and other material (if needed) to > info(a)objectprofile.com Every email you will send to this email will be > acknowledged. If you do not receive a 'Ok' from us, it means we haven't > read it, in that case send your email again after a few days. > - the deadline for submitting is September 4, 2013 > > Mini FAQ? > - Is the object-profile team allowed to participate? No > - Should my visualization or code be open source? No need for this, > whatever license is fine. However your video should be made public. > - How can I get more information? Just comment on the facebook > https://www.facebook.com/ObjectProfile or using Twitter @ObjectProfile or > send email to info(a)objectprofile.com > - What I submit twice? Yes, no problem with that > - How will judge the videos? both the esug community and the object > profile team. The Esug community will have 30% of the final grade, object > profile the remaining 70% > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel > > http://ObjectProfile.com > http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 23, 2013

Re: [Pharo-dev] Pharo VM latest on the Debian 7

by Damien Cassou

On Sun, Aug 11, 2013 at 3:39 PM, Andres Valloud < avalloud(a)smalltalk.comcastbiz.net> wrote: > Ok, thank you. At the risk of being too inquisitive, what do you mean > when you say "add a slave into our build server"? Is the implication that > a release will include N binaries compiled on N Linux versions? the idea is that each linux distribution builds the Pharo VM by itself. I just tried with latest Debian stable and this resulted in the following deb files. Please try them: http://files.pharo.org/vm/pharo/debian/ -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Aug. 23, 2013

Re: [Pharo-dev] Pharo VM latest on the Debian 7

by Damien Cassou

On Thu, Aug 8, 2013 at 11:43 AM, Laszlo Zsolt Kiss <lzskiss(a)dublin.ie>wrote: > The latest Pharo VM isnt working on Debian 7. > could you please try the new deb files? Url is: http://files.pharo.org/vm/pharo/debian/ Thank you -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Aug. 23, 2013

The Pharo Advantage: what is it for you?

by phil＠highoctane.be

Hello, As part of the defense of a budget and technology choices, what would you guys list as a key advantage of using Pharo for creating software solutions? My current stack is: Pharo 2.0 Seaside 3 (including Seaside-REST) Magritte 3 Twitter Bootstrap + a couple of data storage stuff (DBXTalk, Phriak, Voyage) + STOMP + Amber if needed I've been test driving the whole stack for a while and even if there are some quirks, it looks like good enough for what I want to achieve. Now, my question: what is the Pharo advantage you would put forward vs other choices (like LAMP, Java, Rails etc). I am aware of what those could be but I am more looking for what makes you tick when using the technology (like: "it is fun to work with", "no more Java for me, due to ...", "speeds dev time by ...", "not NSA-backdoor-enabled") This is the kind of thing we should have in stock for helping the Consortium members get buy in from people giving a yes on budgets. Thanks in advance for your help! (BTW, I am going to use this on monday morning for defending our position on a significant project). Phil

Aug. 23, 2013

Re: [Pharo-dev] Debugger recursion

by StÃ©phane Ducasse

HI jan we cannot see your code Ideally we would like to have a better handling of deep recursion but we are focusing on more important issues. Stef > Hi, > try this: > > > > This will start opening infinite number of debuggers, because of > A>>doesNotUnderstand: #halt. > Ok, so, if I replace /self halt/ with /Halt signal/, it will do the same, > but now because of A>>doesNotUnderstand: #inspector. > But in both cases, after successfully (before stack is full) interrupting > the recursion with Alt+., only the Process Browser is full of > "Morphic UI > process:MorphicUIManager>>openDebuggerOn:context:label:contents:fullView:" > no real debugger is visible... > > My question: How to debug code inside DNU method? Bug? Feature? > I know, the full stack issue can be solved by a watchdog, is it planned? And > it was discussed before here on mailinglist, but with different code > examples. > Or one can limit the total count of opened... > > > > ----- > Save The World! > -- > View this message in context: http://forum.world.st/Debugger-recursion-tp4704703.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Aug. 23, 2013

-= First Visualization Contest with Roassal =-

by Alexandre Bergel

Dear colleagues and friends, We are happy to announce the First Visualization Contest with Roassal. What can I win? - 150 euros, sponsored by ObjectProfile - a Ã¼ber-cool ObjectProfile T-shirt and some wonderful stickers - maximum publicity of your work - a nice award certificate, delivered during ESUG How can I win? - you have to produce a visualization with Roassal. You can use the Pharo, VisualWorks or VAST version of Roassal. Here is an example of what we expect http://bit.ly/sunburstDemo - making a video is mandatory. The video will weight the most in our decision. The video could be of any length and has to include your name and say that is was made (partly or completely) with Roassal. No need to talk, just show off! - making your code available and easy to install will help you get more points How can I submit? - send the links of your video and other material (if needed) to info(a)objectprofile.com Every email you will send to this email will be acknowledged. If you do not receive a 'Ok' from us, it means we haven't read it, in that case send your email again after a few days. - the deadline for submitting is September 4, 2013 Mini FAQ? - Is the object-profile team allowed to participate? No - Should my visualization or code be open source? No need for this, whatever license is fine. However your video should be made public. - How can I get more information? Just comment on the facebook https://www.facebook.com/ObjectProfile or using Twitter @ObjectProfile or send email to info(a)objectprofile.com - What I submit twice? Yes, no problem with that - How will judge the videos? both the esug community and the object profile team. The Esug community will have 30% of the final grade, object profile the remaining 70% -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://ObjectProfile.com http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 23, 2013

Debugger recursion

by jan.struz

Hi, try this: This will start opening infinite number of debuggers, because of A>>doesNotUnderstand: #halt. Ok, so, if I replace /self halt/ with /Halt signal/, it will do the same, but now because of A>>doesNotUnderstand: #inspector. But in both cases, after successfully (before stack is full) interrupting the recursion with Alt+., only the Process Browser is full of "Morphic UI process:MorphicUIManager>>openDebuggerOn:context:label:contents:fullView:" no real debugger is visible... My question: How to debug code inside DNU method? Bug? Feature? I know, the full stack issue can be solved by a watchdog, is it planned? And it was discussed before here on mailinglist, but with different code examples. Or one can limit the total count of opened... ----- Save The World! -- View this message in context: http://forum.world.st/Debugger-recursion-tp4704703.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 23, 2013

Re: [Pharo-dev] How do diagnose image locks up (cpu 100%) on save?

by Paul DeBruicker

So when you open the image I posted and in the workspace run RFBServer start. Smalltalk snapshot: true andQuit: false. Everything works fine? It doesn't go to 100% cpu use? -- View this message in context: http://forum.world.st/How-do-diagnose-image-locks-up-cpu-100-on-save-tp4704… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 23, 2013

Re: [Pharo-dev] How do diagnose image locks up (cpu 100%) on save?

by Igor Stasenko

looks quite healthy to me. image is idle doing nothing. On 22 August 2013 20:21, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Paul DeBruicker wrote > > In this instance, that doesn't output anything. Specifically: > > > > > > $ ps -A | grep pharo > > 6001 pts/0 00:00:45 pharo > > $ kill -s SIGUSR1 6001 > > $ > > > Oh no wait. I'm an idiot. It spits out this in the terminal where the > pharo process is running: > > stack page bytes 4096 available headroom 3300 minimum unused headroom 3504 > > (SIGUSR1) > > SIGUSR1 Thu Aug 22 11:18:58 2013 > > > pharo VM version: 3.9-7 #1 Wed Mar 13 18:22:44 CET 2013 gcc 4.4.3 > Built from: NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 > With: NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 > Revision: git://gitorious.org/cogvm/blessed.git Commit: > 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 > By: > Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 > Build host: Linux linux-ubuntu-10 2.6.32-38-server #83-Ubuntu SMP Wed Jan 4 > 11:26:59 UTC 2012 x86_64 GNU/Linux > plugin path: /home/paul/Downloads/pharo2.0/bin [default: > /home/paul/Downloads/pharo2.0/bin/] > > > C stack backtrace: > /home/paul/Downloads/pharo2.0/bin/pharo[0x80a0c0c] > /home/paul/Downloads/pharo2.0/bin/pharo[0x80a0e67] > [0xf7771410] > /home/paul/Downloads/pharo2.0/bin/vm-display-X11(+0x10d51)[0xf7765d51] > > /home/paul/Downloads/pharo2.0/bin/pharo(ioRelinquishProcessorForMicroseconds+0x14)[0x809e674] > /home/paul/Downloads/pharo2.0/bin/pharo[0x8081a0a] > [0xb7010d11] > /home/paul/Downloads/pharo2.0/bin/pharo(interpret+0x7a6)[0x8094f36] > /home/paul/Downloads/pharo2.0/bin/pharo(main+0x2b3)[0x80a18b3] > /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0xf7554935] > > > All Smalltalk process stacks (active first): > Process 0xb899e15c priority 10 > 0xfff24370 M ProcessorScheduler class>idleProcess 0xb7347240: a(n) > ProcessorScheduler class > 0xfff24390 I [] in ProcessorScheduler class>startUp 0xb7347240: a(n) > ProcessorScheduler class > 0xfff243b0 I [] in BlockClosure>newProcess 0xb899e080: a(n) BlockClosure > > Process 0xb856be14 priority 50 > 0xfff263b0 I WeakArray class>finalizationProcess 0xb7347450: a(n) WeakArray > class > 0xb85ce458 s [] in WeakArray class>restartFinalizationProcess > 0xb856bdb4 s [] in BlockClosure>newProcess > > Process 0xb85ced20 priority 80 > 0xfff29350 M Delay class>handleTimerEvent 0xb7349a3c: a(n) Delay class > 0xfff29370 I Delay class>runTimerEventLoop 0xb7349a3c: a(n) Delay class > 0xfff29390 I [] in Delay class>startTimerEventLoop 0xb7349a3c: a(n) Delay > class > 0xfff293b0 I [] in BlockClosure>newProcess 0xb85cec44: a(n) BlockClosure > > Process 0xb899dc7c priority 60 > 0xfff2a344 I InputEventFetcher>waitForInput 0xb7326fd8: a(n) > InputEventFetcher > 0xfff2a370 I InputEventFetcher>eventLoop 0xb7326fd8: a(n) InputEventFetcher > 0xfff2a390 I [] in InputEventFetcher>installEventLoop 0xb7326fd8: a(n) > InputEventFetcher > 0xfff2a3b0 I [] in BlockClosure>newProcess 0xb899dba0: a(n) BlockClosure > > Process 0xb899df90 priority 60 > 0xfff1c370 I SmalltalkImage>lowSpaceWatcher 0xb764de94: a(n) SmalltalkImage > 0xfff1c390 I [] in SmalltalkImage>installLowSpaceWatcher 0xb764de94: a(n) > SmalltalkImage > 0xfff1c3b0 I [] in BlockClosure>newProcess 0xb899deb4: a(n) BlockClosure > > Process 0xb74c5848 priority 40 > 0xfff282fc M [] in Delay>wait 0xb8ae610c: a(n) Delay > 0xfff2831c M BlockClosure>ifCurtailed: 0xb8ae6348: a(n) BlockClosure > 0xfff28338 M Delay>wait 0xb8ae610c: a(n) Delay > 0xfff28358 M WorldState>interCyclePause: 0xb7182620: a(n) WorldState > 0xfff28374 M WorldState>doOneCycleFor: 0xb7182620: a(n) WorldState > 0xfff28390 M PasteUpMorph>doOneCycle 0xb7173150: a(n) PasteUpMorph > 0xfff283b0 I [] in MorphicUIManager>? 0xb7186a5c: a(n) MorphicUIManager > 0xb74c57e8 s [] in BlockClosure>? > > Most recent primitives > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > relinquishProcessorForMicroseconds: > > stack page bytes 4096 available headroom 3300 minimum unused headroom 3504 > > (SIGUSR1) > > > > > > -- > View this message in context: > http://forum.world.st/How-do-diagnose-image-locks-up-cpu-100-on-save-tp4704… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- Best regards, Igor Stasenko.

Aug. 22, 2013

Re: [Pharo-dev] How do diagnose image locks up (cpu 100%) on save?

by Paul DeBruicker

Sven Van Caekenberghe-2 wrote > On 22 Aug 2013, at 19:34, Paul DeBruicker < > pdebruic@ > > wrote: > >> Hi - >> >> The plain Pharo 20619 + RFB image in my dropbox here: >> https://dl.dropboxusercontent.com/u/4460862/pharo2RFB.zip freezes when >> you save it while the RFB server is running. The freeze occurs in the >> #snapshotPrimitive. >> >> >> This is the VM info I'm using: >> >> 3.9-7 #1 Wed Mar 13 18:22:44 CET 2013 gcc 4.4.3 >> 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 >> git://gitorious.org/cogvm/blessed.git Commit: >> 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 >> By: Esteban Lorenzano < > estebanlm@ > > Jenkins build #14535 >> Linux linux-ubuntu-10 2.6.32-38-server #83-Ubuntu SMP Wed Jan 4 11:26:59 >> UTC 2012 x86_64 GNU/Linux >> plugin path: /home/paul/pharo/pharo2.0/bin [default: >> /home/paul/pharo/pharo2.0/bin/] >> >> >> How can I diagnose/fix what is going wrong? >> >> >> I'm reluctant to make it stop and start the RFB server through the >> snapshot because it will kick off all attached clients. Of which there >> is at most one and its me, so it wouldn't be too bad but its not >> desirable. >> >> It freezes whether there is a client connection or not. > > Paul, > > Zinc HTTP Server are stopped/started on each image save. For HTTP 1.1 that > is OK, protocol wise. I think that RFB should do something similar to > prevent issues like the one you are reporting (and there have been many in > the past as well). > > Consider this: if you save but do not quit, and you later abort the image > hard, you would expect the saved image to work, right. That can only be > with a fresh server socket. > > Sven > >> Thanks >> >> Paul >> I think the 'abort the image hard' problem is taken care of in the #startUp: method on the RFBServer. It checks if the image is resuming and the server is/was running and if so stopping then restarting the RFB server. I don't want to stop and restart the server every time there is a save. I'm fine doing it on startup after a quit or abort as you describe. Anyway, from the stack dump I posted I cannot tell for sure but it seems like a VM bug. -- View this message in context: http://forum.world.st/How-do-diagnose-image-locks-up-cpu-100-on-save-tp4704… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 22, 2013

Re: [Pharo-dev] [Pharo-fuel] Fuel API bug

by StÃ©phane Ducasse

hi henrik do you have an implementation for when:do:for: because I do not see it? https://pharo.fogbugz.com/default.asp?11316 Stef >>>> #when:do: is there already ;) >>> >>> even better then :) >>> >>>> #when:send:to: and #when:do:for: should be added though. >> >> what would be when:do:for: ? > > Its use is to specify a non-standard subscriber. > In VW it is pretty much mandatory when using weak subscription, as VW subscribes the block. > In Pharo it's much less useful, both because the at the moment weak when:do: doesn't work, but also since Pharo subscribes the block's receiver by default, which is what you want in 95% of cases. > Still nice to have around in the edge cases one might still need it though. > > Cheers, > Henry

Aug. 22, 2013

Re: [Pharo-dev] How do diagnose image locks up (cpu 100%) on save?

by Sven Van Caekenberghe

On 22 Aug 2013, at 19:34, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Hi - > > The plain Pharo 20619 + RFB image in my dropbox here: > https://dl.dropboxusercontent.com/u/4460862/pharo2RFB.zip freezes when > you save it while the RFB server is running. The freeze occurs in the > #snapshotPrimitive. > > > This is the VM info I'm using: > > 3.9-7 #1 Wed Mar 13 18:22:44 CET 2013 gcc 4.4.3 > 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 > git://gitorious.org/cogvm/blessed.git Commit: > 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 > Linux linux-ubuntu-10 2.6.32-38-server #83-Ubuntu SMP Wed Jan 4 11:26:59 > UTC 2012 x86_64 GNU/Linux > plugin path: /home/paul/pharo/pharo2.0/bin [default: > /home/paul/pharo/pharo2.0/bin/] > > > How can I diagnose/fix what is going wrong? > > > I'm reluctant to make it stop and start the RFB server through the > snapshot because it will kick off all attached clients. Of which there > is at most one and its me, so it wouldn't be too bad but its not > desirable. > > It freezes whether there is a client connection or not. Paul, Zinc HTTP Server are stopped/started on each image save. For HTTP 1.1 that is OK, protocol wise. I think that RFB should do something similar to prevent issues like the one you are reporting (and there have been many in the past as well). Consider this: if you save but do not quit, and you later abort the image hard, you would expect the saved image to work, right. That can only be with a fresh server socket. Sven > Thanks > > Paul >

Aug. 22, 2013

Re: [Pharo-dev] How do diagnose image locks up (cpu 100%) on save?

by Paul DeBruicker

Paul DeBruicker wrote > In this instance, that doesn't output anything. Specifically: > > > $ ps -A | grep pharo > 6001 pts/0 00:00:45 pharo > $ kill -s SIGUSR1 6001 > $ Oh no wait. I'm an idiot. It spits out this in the terminal where the pharo process is running: stack page bytes 4096 available headroom 3300 minimum unused headroom 3504 (SIGUSR1) SIGUSR1 Thu Aug 22 11:18:58 2013 pharo VM version: 3.9-7 #1 Wed Mar 13 18:22:44 CET 2013 gcc 4.4.3 Built from: NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 With: NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 Revision: git://gitorious.org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 Build host: Linux linux-ubuntu-10 2.6.32-38-server #83-Ubuntu SMP Wed Jan 4 11:26:59 UTC 2012 x86_64 GNU/Linux plugin path: /home/paul/Downloads/pharo2.0/bin [default: /home/paul/Downloads/pharo2.0/bin/] C stack backtrace: /home/paul/Downloads/pharo2.0/bin/pharo[0x80a0c0c] /home/paul/Downloads/pharo2.0/bin/pharo[0x80a0e67] [0xf7771410] /home/paul/Downloads/pharo2.0/bin/vm-display-X11(+0x10d51)[0xf7765d51] /home/paul/Downloads/pharo2.0/bin/pharo(ioRelinquishProcessorForMicroseconds+0x14)[0x809e674] /home/paul/Downloads/pharo2.0/bin/pharo[0x8081a0a] [0xb7010d11] /home/paul/Downloads/pharo2.0/bin/pharo(interpret+0x7a6)[0x8094f36] /home/paul/Downloads/pharo2.0/bin/pharo(main+0x2b3)[0x80a18b3] /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0xf7554935] All Smalltalk process stacks (active first): Process 0xb899e15c priority 10 0xfff24370 M ProcessorScheduler class>idleProcess 0xb7347240: a(n) ProcessorScheduler class 0xfff24390 I [] in ProcessorScheduler class>startUp 0xb7347240: a(n) ProcessorScheduler class 0xfff243b0 I [] in BlockClosure>newProcess 0xb899e080: a(n) BlockClosure Process 0xb856be14 priority 50 0xfff263b0 I WeakArray class>finalizationProcess 0xb7347450: a(n) WeakArray class 0xb85ce458 s [] in WeakArray class>restartFinalizationProcess 0xb856bdb4 s [] in BlockClosure>newProcess Process 0xb85ced20 priority 80 0xfff29350 M Delay class>handleTimerEvent 0xb7349a3c: a(n) Delay class 0xfff29370 I Delay class>runTimerEventLoop 0xb7349a3c: a(n) Delay class 0xfff29390 I [] in Delay class>startTimerEventLoop 0xb7349a3c: a(n) Delay class 0xfff293b0 I [] in BlockClosure>newProcess 0xb85cec44: a(n) BlockClosure Process 0xb899dc7c priority 60 0xfff2a344 I InputEventFetcher>waitForInput 0xb7326fd8: a(n) InputEventFetcher 0xfff2a370 I InputEventFetcher>eventLoop 0xb7326fd8: a(n) InputEventFetcher 0xfff2a390 I [] in InputEventFetcher>installEventLoop 0xb7326fd8: a(n) InputEventFetcher 0xfff2a3b0 I [] in BlockClosure>newProcess 0xb899dba0: a(n) BlockClosure Process 0xb899df90 priority 60 0xfff1c370 I SmalltalkImage>lowSpaceWatcher 0xb764de94: a(n) SmalltalkImage 0xfff1c390 I [] in SmalltalkImage>installLowSpaceWatcher 0xb764de94: a(n) SmalltalkImage 0xfff1c3b0 I [] in BlockClosure>newProcess 0xb899deb4: a(n) BlockClosure Process 0xb74c5848 priority 40 0xfff282fc M [] in Delay>wait 0xb8ae610c: a(n) Delay 0xfff2831c M BlockClosure>ifCurtailed: 0xb8ae6348: a(n) BlockClosure 0xfff28338 M Delay>wait 0xb8ae610c: a(n) Delay 0xfff28358 M WorldState>interCyclePause: 0xb7182620: a(n) WorldState 0xfff28374 M WorldState>doOneCycleFor: 0xb7182620: a(n) WorldState 0xfff28390 M PasteUpMorph>doOneCycle 0xb7173150: a(n) PasteUpMorph 0xfff283b0 I [] in MorphicUIManager>? 0xb7186a5c: a(n) MorphicUIManager 0xb74c57e8 s [] in BlockClosure>? Most recent primitives relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: relinquishProcessorForMicroseconds: stack page bytes 4096 available headroom 3300 minimum unused headroom 3504 (SIGUSR1) -- View this message in context: http://forum.world.st/How-do-diagnose-image-locks-up-cpu-100-on-save-tp4704… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 22, 2013

Re: [Pharo-dev] How do diagnose image locks up (cpu 100%) on save?

by Paul DeBruicker

In this instance, that doesn't output anything. Specifically: $ ps -A | grep pharo 6001 pts/0 00:00:45 pharo $ kill -s SIGUSR1 6001 $ Mariano Martinez Peck wrote > If you run the VM from command line and you send a kill -s SIGUSR1 ... it > should display the stacktrace of the VM in the console. > See http://marianopeck.wordpress.com/2012/05/19/pharo-tips-and-tricks/ > item "Send kill signal:" > > hope this help. > > Cheers, > > > > On Thu, Aug 22, 2013 at 2:34 PM, Paul DeBruicker < > pdebruic@ > > wrote: > >> Hi - >> >> The plain Pharo 20619 + RFB image in my dropbox here: >> https://dl.dropboxusercontent.com/u/4460862/pharo2RFB.zip freezes when >> you save it while the RFB server is running. The freeze occurs in the >> #snapshotPrimitive. >> >> >> This is the VM info I'm using: >> >> 3.9-7 #1 Wed Mar 13 18:22:44 CET 2013 gcc 4.4.3 >> 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 >> git://gitorious.org/cogvm/blessed.git Commit: >> 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 >> By: Esteban Lorenzano < > estebanlm@ > > Jenkins build #14535 >> Linux linux-ubuntu-10 2.6.32-38-server #83-Ubuntu SMP Wed Jan 4 11:26:59 >> UTC 2012 x86_64 GNU/Linux >> plugin path: /home/paul/pharo/pharo2.0/bin [default: >> /home/paul/pharo/pharo2.0/bin/] >> >> >> How can I diagnose/fix what is going wrong? >> >> >> I'm reluctant to make it stop and start the RFB server through the >> snapshot because it will kick off all attached clients. Of which there >> is at most one and its me, so it wouldn't be too bad but its not >> desirable. >> >> It freezes whether there is a client connection or not. >> >> >> Thanks >> >> Paul >> >> > > > -- > Mariano > http://marianopeck.wordpress.com -- View this message in context: http://forum.world.st/How-do-diagnose-image-locks-up-cpu-100-on-save-tp4704… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 22, 2013

new Cog VMs available

by Eliot Miranda

http://www.mirandabanda.org/files/Cog/VM/VM.r2776/ CogVM binaries as per VMMaker.oscog-eem.333/r2776 * Speed-up Newspeak significantly (e.g. -28% in one compile-intensive benchmark) by maintaining unpaired methods (compilations of anonymous accessors) on a linked list instead of searching the entire method zone. * Make primitiveObjectAtPut fail if changing the header word and the new header has a different literal count. Avoids crashing the VM when inadvertently changing the header, as a Newspeak bootstrap did recently. * Implement frameless inst var store from arguments, so e.g. Point>>setX:Y: is frameless. * Add Cogit support for clean blocks by scanning literals looking for BlockClosures on the current method. -- best, Eliot

Aug. 22, 2013

Re: [Pharo-dev] How do diagnose image locks up (cpu 100%) on save?

by Mariano Martinez Peck

If you run the VM from command line and you send a kill -s SIGUSR1 ... it should display the stacktrace of the VM in the console. See http://marianopeck.wordpress.com/2012/05/19/pharo-tips-and-tricks/ item "Send kill signal:" hope this help. Cheers, On Thu, Aug 22, 2013 at 2:34 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Hi - > > The plain Pharo 20619 + RFB image in my dropbox here: > https://dl.dropboxusercontent.com/u/4460862/pharo2RFB.zip freezes when > you save it while the RFB server is running. The freeze occurs in the > #snapshotPrimitive. > > > This is the VM info I'm using: > > 3.9-7 #1 Wed Mar 13 18:22:44 CET 2013 gcc 4.4.3 > 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 > git://gitorious.org/cogvm/blessed.git Commit: > 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 > Linux linux-ubuntu-10 2.6.32-38-server #83-Ubuntu SMP Wed Jan 4 11:26:59 > UTC 2012 x86_64 GNU/Linux > plugin path: /home/paul/pharo/pharo2.0/bin [default: > /home/paul/pharo/pharo2.0/bin/] > > > How can I diagnose/fix what is going wrong? > > > I'm reluctant to make it stop and start the RFB server through the > snapshot because it will kick off all attached clients. Of which there > is at most one and its me, so it wouldn't be too bad but its not > desirable. > > It freezes whether there is a client connection or not. > > > Thanks > > Paul > > -- Mariano http://marianopeck.wordpress.com

Aug. 22, 2013

How do diagnose image locks up (cpu 100%) on save?

by Paul DeBruicker

Hi - The plain Pharo 20619 + RFB image in my dropbox here: https://dl.dropboxusercontent.com/u/4460862/pharo2RFB.zip freezes when you save it while the RFB server is running. The freeze occurs in the #snapshotPrimitive. This is the VM info I'm using: 3.9-7 #1 Wed Mar 13 18:22:44 CET 2013 gcc 4.4.3 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 git://gitorious.org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 Linux linux-ubuntu-10 2.6.32-38-server #83-Ubuntu SMP Wed Jan 4 11:26:59 UTC 2012 x86_64 GNU/Linux plugin path: /home/paul/pharo/pharo2.0/bin [default: /home/paul/pharo/pharo2.0/bin/] How can I diagnose/fix what is going wrong? I'm reluctant to make it stop and start the RFB server through the snapshot because it will kick off all attached clients. Of which there is at most one and its me, so it wouldn't be too bad but its not desirable. It freezes whether there is a client connection or not. Thanks Paul

Aug. 22, 2013

[update 3.0] #30339

by Esteban Lorenzano

30339 ----- 11443 Icon for explicitRequirement methods https://pharo.fogbugz.com/f/cases/11443 11147 FileReference(Object)>>doesNotUnderstand: #other https://pharo.fogbugz.com/f/cases/11147 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-EstebanLore… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-EstebanLorenzano.517… http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Tests-Core-Esteban… http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Core-EstebanLorenz…

Aug. 22, 2013

Re: [Pharo-dev] Updating the Pharo Contributors listing

by Sven Van Caekenberghe

Alex, On 19 Aug 2013, at 13:41, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > PharoContributor new > name: 'Alexandre Bergel'; > id: 'abergel'; > email: 'alexandre.bergel(a)me.com'; > website: 'http://bergel.eu'; > description: 'Use Pharo for research in software engineering, quality and understanding at the University of Chile. Contribute to Roassal, Moose, Spy and many more.'; > image: 'http://bergel.eu/pictures/web4.jpg'; > yourself Your entry was updated: http://contributors.pharo.org/#alexandrebergel However, your image cannot be parsed in Pharo: ZnEasy getJpeg: 'http://bergel.eu/pictures/web4.jpg'. Either try re-exporting it until the parsing works, or set up a gravatar.com entry. Thanks, Sven > On Aug 19, 2013, at 3:24 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> PharoContributor new >> name: 'Esteban Lorenzano'; >> id: 'estebanlm'; >> email: 'estebanlm(a)gmail.com'; >> website: 'http://smallworks.eu'; >> description: 'Pharo core team. Contributor of several projects, including Kernel, DBXTalk, Voyage, Mars, etc. Also I work on the VM.'; >> image: 'http://www.gravatar.com/avatar/193af464509ae8fbcc04abad70b72fc0?s=120'; >> yourself >> >> >> >> On Aug 18, 2013, at 12:39 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> Hi Jannik, >>> >>> On 16 Aug 2013, at 21:23, jannik.laval <jannik.laval(a)gmail.com> wrote: >>> >>>> PharoContributor new >>>> name: 'Jannik Laval'; >>>> id: 'jannik.laval'; >>>> email: 'jannik.laval(a)gmail.com'; >>>> website: 'http://www.jannik-laval.eu'; >>>> description: 'Software Researcher at Mines Douai'; >>>> image: 'http://www.jannik-laval.eu/assets/images/DSC02023%20-%20Version%202.jpg'; >>>> yourself >>> >>> Updated: >>> >>> http://contributors.pharo.org#janniklaval >>> >>> Thanks. >>> >>> Sven >>> >>>> On Aug 12, 2013, at 5:12 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>>> Dear Fellow Pharoers, >>>>> >>>>> As some of you may know, we have a page listing Pharo Contributors >>>>> >>>>> http://www.pharo-project.org/community/contributors >>>>> >>>>> This page was manually constructed and urgently needs an update. >>>>> Based on the code behind the Pharo Consultants page >>>>> >>>>> http://consultants.pharo.org >>>>> >>>>> we want a similar data driven, statically generated page for Pharo Contributors >>>>> >>>>> http://contributors.pharo.org >>>>> >>>>> the new page is based on some of the old data, but needs updating. Many people are missing as well. So please, please, edit the template and send me your new or up to date information. >>>>> >>>>> PharoContributor new >>>>> name: 'StÃ©phane Ducasse'; >>>>> id: 'stephaneducasse'; >>>>> email: 'stephane.ducasse(a)inria.fr'; >>>>> website: 'http://stephane.ducasse.free.fr/'; >>>>> description: 'Research director at INRIA Lille leading the RMoD Team. Pharo board member and president of ESUG.'; >>>>> image: 'http://stephane.ducasse.free.fr/StefFingerOnNose128.jpg'; >>>>> yourself >>>>> >>>>> PharoContributor new >>>>> name: 'Camillo Bruni'; >>>>> email: 'camillobruni(a)gmail.com'; >>>>> description: 'Cosmopolitan Swiss Hacker, currently at INRIA'; >>>>> yourself >>>>> >>>>> Some notes: >>>>> >>>>> - id is only needed when your name contains non-ascii characters >>>>> - email will default to pharo-dev(a)lists.pharo.org if missing >>>>> - website will default to a Google search for your name if a URL is missing >>>>> - image can be omitted if you have a Gravatar, else it becomes a smiley >>>>> - images will be rescaled to fit in 128x128, the URL needs to remain accessible >>>>> - description is a pure text String, no markup is allowed >>>>> - the description does not have to be too formal >>>>> - the page is statically generated, only then do changes take effect >>>>> >>>>> Regards, >>>>> >>>>> Sven, on behalf of the Pharo Board. >>>>> >>>>> PS: If you are curious, the code for generating this page can be found at >>>>> >>>>> http://www.smalltalkhub.com/#!/~Pharo/PharoPeople >>>>> >>>>> >>>> >>> >>> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Aug. 22, 2013

Re: [Pharo-dev] Updating the Pharo Contributors listing

by Clara Allende

Great, my gravatar image is fine :) Thanks a lot! On 22 August 2013 11:54, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Clara, > > On 19 Aug 2013, at 14:13, Clara Allende <clari.allende(a)gmail.com> wrote: > > > PharoContributor new > > name: 'Clara Allende'; > > id: 'ClaraAllende'; > > email: 'clari.allende(a)gmail.com'; > > website: 'http://clariallende.wordpress.com'; > > description: 'student for GSoC 2013, using Pharo for teaching at > National Technological University in Buenos Aires'; > > image: ' > https://dl.dropboxusercontent.com/u/31270395/Im%C3%A1genes/fb.jpg'; > > yourself > > I added your entry: http://contributors.pharo.org/#claraallende > > The JPEG parser in Pharo had trouble parsing your image, so I did not use > it. It took your gravatar.com image instead. I know the picture loads in > a browser, maybe you have to re-export it. This should work, but doesn't > > ZnEasy getJpeg: ' > https://dl.dropboxusercontent.com/u/31270395/Im%C3%A1genes/fb.jpg'. > > Thanks! > > Sven > > > On 19 August 2013 08:41, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > PharoContributor new > > name: 'Alexandre Bergel'; > > id: 'abergel'; > > email: 'alexandre.bergel(a)me.com'; > > website: 'http://bergel.eu'; > > description: 'Use Pharo for research in software engineering, > quality and understanding at the University of Chile. Contribute to > Roassal, Moose, Spy and many more.'; > > image: 'http://bergel.eu/pictures/web4.jpg'; > > yourself > > > > > > > > On Aug 19, 2013, at 3:24 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > > > > PharoContributor new > > > name: 'Esteban Lorenzano'; > > > id: 'estebanlm'; > > > email: 'estebanlm(a)gmail.com'; > > > website: 'http://smallworks.eu'; > > > description: 'Pharo core team. Contributor of several projects, > including Kernel, DBXTalk, Voyage, Mars, etc. Also I work on the VM.'; > > > image: ' > http://www.gravatar.com/avatar/193af464509ae8fbcc04abad70b72fc0?s=120'; > > > yourself > > > > > > > > > > > > On Aug 18, 2013, at 12:39 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > > > > >> Hi Jannik, > > >> > > >> On 16 Aug 2013, at 21:23, jannik.laval <jannik.laval(a)gmail.com> > wrote: > > >> > > >>> PharoContributor new > > >>> name: 'Jannik Laval'; > > >>> id: 'jannik.laval'; > > >>> email: 'jannik.laval(a)gmail.com'; > > >>> website: 'http://www.jannik-laval.eu'; > > >>> description: 'Software Researcher at Mines Douai'; > > >>> image: ' > http://www.jannik-laval.eu/assets/images/DSC02023%20-%20Version%202.jpg'; > > >>> yourself > > >> > > >> Updated: > > >> > > >> http://contributors.pharo.org#janniklaval > > >> > > >> Thanks. > > >> > > >> Sven > > >> > > >>> On Aug 12, 2013, at 5:12 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > >>> > > >>>> Dear Fellow Pharoers, > > >>>> > > >>>> As some of you may know, we have a page listing Pharo Contributors > > >>>> > > >>>> http://www.pharo-project.org/community/contributors > > >>>> > > >>>> This page was manually constructed and urgently needs an update. > > >>>> Based on the code behind the Pharo Consultants page > > >>>> > > >>>> http://consultants.pharo.org > > >>>> > > >>>> we want a similar data driven, statically generated page for Pharo > Contributors > > >>>> > > >>>> http://contributors.pharo.org > > >>>> > > >>>> the new page is based on some of the old data, but needs updating. > Many people are missing as well. So please, please, edit the template and > send me your new or up to date information. > > >>>> > > >>>> PharoContributor new > > >>>> name: 'StÃ©phane Ducasse'; > > >>>> id: 'stephaneducasse'; > > >>>> email: 'stephane.ducasse(a)inria.fr'; > > >>>> website: 'http://stephane.ducasse.free.fr/'; > > >>>> description: 'Research director at INRIA Lille leading the RMoD > Team. Pharo board member and president of ESUG.'; > > >>>> image: 'http://stephane.ducasse.free.fr/StefFingerOnNose128.jpg'; > > >>>> yourself > > >>>> > > >>>> PharoContributor new > > >>>> name: 'Camillo Bruni'; > > >>>> email: 'camillobruni(a)gmail.com'; > > >>>> description: 'Cosmopolitan Swiss Hacker, currently at INRIA'; > > >>>> yourself > > >>>> > > >>>> Some notes: > > >>>> > > >>>> - id is only needed when your name contains non-ascii characters > > >>>> - email will default to pharo-dev(a)lists.pharo.org if missing > > >>>> - website will default to a Google search for your name if a URL is > missing > > >>>> - image can be omitted if you have a Gravatar, else it becomes a > smiley > > >>>> - images will be rescaled to fit in 128x128, the URL needs to > remain accessible > > >>>> - description is a pure text String, no markup is allowed > > >>>> - the description does not have to be too formal > > >>>> - the page is statically generated, only then do changes take effect > > >>>> > > >>>> Regards, > > >>>> > > >>>> Sven, on behalf of the Pharo Board. > > >>>> > > >>>> PS: If you are curious, the code for generating this page can be > found at > > >>>> > > >>>> http://www.smalltalkhub.com/#!/~Pharo/PharoPeople > > >>>> > > >>>> > > >>> > > >> > > >> > > > > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > >

Aug. 22, 2013

Re: [Pharo-dev] Updating the Pharo Contributors listing

by Sven Van Caekenberghe

Clara, On 19 Aug 2013, at 14:13, Clara Allende <clari.allende(a)gmail.com> wrote: > PharoContributor new > name: 'Clara Allende'; > id: 'ClaraAllende'; > email: 'clari.allende(a)gmail.com'; > website: 'http://clariallende.wordpress.com'; > description: 'student for GSoC 2013, using Pharo for teaching at National Technological University in Buenos Aires'; > image: 'https://dl.dropboxusercontent.com/u/31270395/Im%C3%A1genes/fb.jpg'; > yourself I added your entry: http://contributors.pharo.org/#claraallende The JPEG parser in Pharo had trouble parsing your image, so I did not use it. It took your gravatar.com image instead. I know the picture loads in a browser, maybe you have to re-export it. This should work, but doesn't ZnEasy getJpeg: 'https://dl.dropboxusercontent.com/u/31270395/Im%C3%A1genes/fb.jpg'. Thanks! Sven > On 19 August 2013 08:41, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > PharoContributor new > name: 'Alexandre Bergel'; > id: 'abergel'; > email: 'alexandre.bergel(a)me.com'; > website: 'http://bergel.eu'; > description: 'Use Pharo for research in software engineering, quality and understanding at the University of Chile. Contribute to Roassal, Moose, Spy and many more.'; > image: 'http://bergel.eu/pictures/web4.jpg'; > yourself > > > > On Aug 19, 2013, at 3:24 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > PharoContributor new > > name: 'Esteban Lorenzano'; > > id: 'estebanlm'; > > email: 'estebanlm(a)gmail.com'; > > website: 'http://smallworks.eu'; > > description: 'Pharo core team. Contributor of several projects, including Kernel, DBXTalk, Voyage, Mars, etc. Also I work on the VM.'; > > image: 'http://www.gravatar.com/avatar/193af464509ae8fbcc04abad70b72fc0?s=120'; > > yourself > > > > > > > > On Aug 18, 2013, at 12:39 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> Hi Jannik, > >> > >> On 16 Aug 2013, at 21:23, jannik.laval <jannik.laval(a)gmail.com> wrote: > >> > >>> PharoContributor new > >>> name: 'Jannik Laval'; > >>> id: 'jannik.laval'; > >>> email: 'jannik.laval(a)gmail.com'; > >>> website: 'http://www.jannik-laval.eu'; > >>> description: 'Software Researcher at Mines Douai'; > >>> image: 'http://www.jannik-laval.eu/assets/images/DSC02023%20-%20Version%202.jpg'; > >>> yourself > >> > >> Updated: > >> > >> http://contributors.pharo.org#janniklaval > >> > >> Thanks. > >> > >> Sven > >> > >>> On Aug 12, 2013, at 5:12 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >>> > >>>> Dear Fellow Pharoers, > >>>> > >>>> As some of you may know, we have a page listing Pharo Contributors > >>>> > >>>> http://www.pharo-project.org/community/contributors > >>>> > >>>> This page was manually constructed and urgently needs an update. > >>>> Based on the code behind the Pharo Consultants page > >>>> > >>>> http://consultants.pharo.org > >>>> > >>>> we want a similar data driven, statically generated page for Pharo Contributors > >>>> > >>>> http://contributors.pharo.org > >>>> > >>>> the new page is based on some of the old data, but needs updating. Many people are missing as well. So please, please, edit the template and send me your new or up to date information. > >>>> > >>>> PharoContributor new > >>>> name: 'StÃ©phane Ducasse'; > >>>> id: 'stephaneducasse'; > >>>> email: 'stephane.ducasse(a)inria.fr'; > >>>> website: 'http://stephane.ducasse.free.fr/'; > >>>> description: 'Research director at INRIA Lille leading the RMoD Team. Pharo board member and president of ESUG.'; > >>>> image: 'http://stephane.ducasse.free.fr/StefFingerOnNose128.jpg'; > >>>> yourself > >>>> > >>>> PharoContributor new > >>>> name: 'Camillo Bruni'; > >>>> email: 'camillobruni(a)gmail.com'; > >>>> description: 'Cosmopolitan Swiss Hacker, currently at INRIA'; > >>>> yourself > >>>> > >>>> Some notes: > >>>> > >>>> - id is only needed when your name contains non-ascii characters > >>>> - email will default to pharo-dev(a)lists.pharo.org if missing > >>>> - website will default to a Google search for your name if a URL is missing > >>>> - image can be omitted if you have a Gravatar, else it becomes a smiley > >>>> - images will be rescaled to fit in 128x128, the URL needs to remain accessible > >>>> - description is a pure text String, no markup is allowed > >>>> - the description does not have to be too formal > >>>> - the page is statically generated, only then do changes take effect > >>>> > >>>> Regards, > >>>> > >>>> Sven, on behalf of the Pharo Board. > >>>> > >>>> PS: If you are curious, the code for generating this page can be found at > >>>> > >>>> http://www.smalltalkhub.com/#!/~Pharo/PharoPeople > >>>> > >>>> > >>> > >> > >> > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Aug. 22, 2013

Re: [Pharo-dev] Updating the Pharo Contributors listing

by Sven Van Caekenberghe

Martin, On 19 Aug 2013, at 18:16, Martin Dias <tinchodias(a)gmail.com> wrote: > PharoContributor new > id: 'tinchodias' > name: 'MartÃn Dias'; > email: 'tinchodias(a)gmail.com'; > description: 'Master at UBA. PhD student at INRIA. Contributor in Fuel project and in Pharo in general.'; > yourself > > I guess my gravatar is fine. Thanks. > > MartÃn Done: http://contributors.pharo.org#martindias Thank you, Sven > > On Mon, Aug 19, 2013 at 2:13 PM, Clara Allende <clari.allende(a)gmail.com> wrote: > PharoContributor new > name: 'Clara Allende'; > id: 'ClaraAllende'; > email: 'clari.allende(a)gmail.com'; > website: 'http://clariallende.wordpress.com'; > description: 'student for GSoC 2013, using Pharo for teaching at National Technological University in Buenos Aires'; > image: 'https://dl.dropboxusercontent.com/u/31270395/Im%C3%A1genes/fb.jpg'; > yourself > > > On 19 August 2013 08:41, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > PharoContributor new > name: 'Alexandre Bergel'; > id: 'abergel'; > email: 'alexandre.bergel(a)me.com'; > website: 'http://bergel.eu'; > description: 'Use Pharo for research in software engineering, quality and understanding at the University of Chile. Contribute to Roassal, Moose, Spy and many more.'; > image: 'http://bergel.eu/pictures/web4.jpg'; > yourself > > > > On Aug 19, 2013, at 3:24 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > PharoContributor new > > name: 'Esteban Lorenzano'; > > id: 'estebanlm'; > > email: 'estebanlm(a)gmail.com'; > > website: 'http://smallworks.eu'; > > description: 'Pharo core team. Contributor of several projects, including Kernel, DBXTalk, Voyage, Mars, etc. Also I work on the VM.'; > > image: 'http://www.gravatar.com/avatar/193af464509ae8fbcc04abad70b72fc0?s=120'; > > yourself > > > > > > > > On Aug 18, 2013, at 12:39 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> Hi Jannik, > >> > >> On 16 Aug 2013, at 21:23, jannik.laval <jannik.laval(a)gmail.com> wrote: > >> > >>> PharoContributor new > >>> name: 'Jannik Laval'; > >>> id: 'jannik.laval'; > >>> email: 'jannik.laval(a)gmail.com'; > >>> website: 'http://www.jannik-laval.eu'; > >>> description: 'Software Researcher at Mines Douai'; > >>> image: 'http://www.jannik-laval.eu/assets/images/DSC02023%20-%20Version%202.jpg'; > >>> yourself > >> > >> Updated: > >> > >> http://contributors.pharo.org#janniklaval > >> > >> Thanks. > >> > >> Sven > >> > >>> On Aug 12, 2013, at 5:12 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >>> > >>>> Dear Fellow Pharoers, > >>>> > >>>> As some of you may know, we have a page listing Pharo Contributors > >>>> > >>>> http://www.pharo-project.org/community/contributors > >>>> > >>>> This page was manually constructed and urgently needs an update. > >>>> Based on the code behind the Pharo Consultants page > >>>> > >>>> http://consultants.pharo.org > >>>> > >>>> we want a similar data driven, statically generated page for Pharo Contributors > >>>> > >>>> http://contributors.pharo.org > >>>> > >>>> the new page is based on some of the old data, but needs updating. Many people are missing as well. So please, please, edit the template and send me your new or up to date information. > >>>> > >>>> PharoContributor new > >>>> name: 'StÃ©phane Ducasse'; > >>>> id: 'stephaneducasse'; > >>>> email: 'stephane.ducasse(a)inria.fr'; > >>>> website: 'http://stephane.ducasse.free.fr/'; > >>>> description: 'Research director at INRIA Lille leading the RMoD Team. Pharo board member and president of ESUG.'; > >>>> image: 'http://stephane.ducasse.free.fr/StefFingerOnNose128.jpg'; > >>>> yourself > >>>> > >>>> PharoContributor new > >>>> name: 'Camillo Bruni'; > >>>> email: 'camillobruni(a)gmail.com'; > >>>> description: 'Cosmopolitan Swiss Hacker, currently at INRIA'; > >>>> yourself > >>>> > >>>> Some notes: > >>>> > >>>> - id is only needed when your name contains non-ascii characters > >>>> - email will default to pharo-dev(a)lists.pharo.org if missing > >>>> - website will default to a Google search for your name if a URL is missing > >>>> - image can be omitted if you have a Gravatar, else it becomes a smiley > >>>> - images will be rescaled to fit in 128x128, the URL needs to remain accessible > >>>> - description is a pure text String, no markup is allowed > >>>> - the description does not have to be too formal > >>>> - the page is statically generated, only then do changes take effect > >>>> > >>>> Regards, > >>>> > >>>> Sven, on behalf of the Pharo Board. > >>>> > >>>> PS: If you are curious, the code for generating this page can be found at > >>>> > >>>> http://www.smalltalkhub.com/#!/~Pharo/PharoPeople > >>>> > >>>> > >>> > >> > >> > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >

Aug. 22, 2013

Re: [Pharo-dev] [rmod] Jenkins slaves

by Christophe Demarey

We can also add a mac slave in our offices. We just have one for pharo / pharo-contribution / rmod. Le 22 aoÃ»t 2013 Ã 16:24, StÃ©phane Ducasse a Ã©crit : > Could we not use on of the mac machine lying around to have our own space? > > On Aug 22, 2013, at 2:15 PM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > >> Hi all, >> >> An hypervisor used to host slaves for the continuous integration service is reaching its maximum storage capacity (primary storage used for running Virtual Machines). >> To avoid VM corruptions, we preventively stopped VMs running on this hypervisor. >> For the pharo ecosystem, following VMs are impacted: >> pharo >> linux-ubuntu-10-04 >> test2 >> pharo-contribution >> linux64-2 74 >> rmod >> windows-7-32 >> >> They will be restarted once the storage will be extended (probably in the beginning of the next week). >> If really needed, it is possible to create new slaves to substitute to these ones since they will be hosted on another hypervisor. >> >> Apologies for the inconvenience, >> Christophe. >

Aug. 22, 2013

Re: [Pharo-dev] Updating the Pharo Contributors listing

by Sven Van Caekenberghe

Esteban, On 19 Aug 2013, at 13:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > PharoContributor new > name: 'Esteban Lorenzano'; > id: 'estebanlm'; > email: 'estebanlm(a)gmail.com'; > website: 'http://smallworks.eu'; > description: 'Pharo core team. Contributor of several projects, including Kernel, DBXTalk, Voyage, Mars, etc. Also I work on the VM.'; > image: 'http://www.gravatar.com/avatar/193af464509ae8fbcc04abad70b72fc0?s=120'; > yourself Done: http://contributors.pharo.org#estebanlorenzano Thank you, Sven > > On Aug 18, 2013, at 12:39 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> Hi Jannik, >> >> On 16 Aug 2013, at 21:23, jannik.laval <jannik.laval(a)gmail.com> wrote: >> >>> PharoContributor new >>> name: 'Jannik Laval'; >>> id: 'jannik.laval'; >>> email: 'jannik.laval(a)gmail.com'; >>> website: 'http://www.jannik-laval.eu'; >>> description: 'Software Researcher at Mines Douai'; >>> image: 'http://www.jannik-laval.eu/assets/images/DSC02023%20-%20Version%202.jpg'; >>> yourself >> >> Updated: >> >> http://contributors.pharo.org#janniklaval >> >> Thanks. >> >> Sven >> >>> On Aug 12, 2013, at 5:12 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>>> Dear Fellow Pharoers, >>>> >>>> As some of you may know, we have a page listing Pharo Contributors >>>> >>>> http://www.pharo-project.org/community/contributors >>>> >>>> This page was manually constructed and urgently needs an update. >>>> Based on the code behind the Pharo Consultants page >>>> >>>> http://consultants.pharo.org >>>> >>>> we want a similar data driven, statically generated page for Pharo Contributors >>>> >>>> http://contributors.pharo.org >>>> >>>> the new page is based on some of the old data, but needs updating. Many people are missing as well. So please, please, edit the template and send me your new or up to date information. >>>> >>>> PharoContributor new >>>> name: 'StÃ©phane Ducasse'; >>>> id: 'stephaneducasse'; >>>> email: 'stephane.ducasse(a)inria.fr'; >>>> website: 'http://stephane.ducasse.free.fr/'; >>>> description: 'Research director at INRIA Lille leading the RMoD Team. Pharo board member and president of ESUG.'; >>>> image: 'http://stephane.ducasse.free.fr/StefFingerOnNose128.jpg'; >>>> yourself >>>> >>>> PharoContributor new >>>> name: 'Camillo Bruni'; >>>> email: 'camillobruni(a)gmail.com'; >>>> description: 'Cosmopolitan Swiss Hacker, currently at INRIA'; >>>> yourself >>>> >>>> Some notes: >>>> >>>> - id is only needed when your name contains non-ascii characters >>>> - email will default to pharo-dev(a)lists.pharo.org if missing >>>> - website will default to a Google search for your name if a URL is missing >>>> - image can be omitted if you have a Gravatar, else it becomes a smiley >>>> - images will be rescaled to fit in 128x128, the URL needs to remain accessible >>>> - description is a pure text String, no markup is allowed >>>> - the description does not have to be too formal >>>> - the page is statically generated, only then do changes take effect >>>> >>>> Regards, >>>> >>>> Sven, on behalf of the Pharo Board. >>>> >>>> PS: If you are curious, the code for generating this page can be found at >>>> >>>> http://www.smalltalkhub.com/#!/~Pharo/PharoPeople >>>> >>>> >>> >> >> >

Aug. 22, 2013

Re: [Pharo-dev] [rmod] Jenkins slaves

by StÃ©phane Ducasse

Could we not use on of the mac machine lying around to have our own space? On Aug 22, 2013, at 2:15 PM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > Hi all, > > An hypervisor used to host slaves for the continuous integration service is reaching its maximum storage capacity (primary storage used for running Virtual Machines). > To avoid VM corruptions, we preventively stopped VMs running on this hypervisor. > For the pharo ecosystem, following VMs are impacted: > pharo > linux-ubuntu-10-04 > test2 > pharo-contribution > linux64-2 74 > rmod > windows-7-32 > > They will be restarted once the storage will be extended (probably in the beginning of the next week). > If really needed, it is possible to create new slaves to substitute to these ones since they will be hosted on another hypervisor. > > Apologies for the inconvenience, > Christophe.

Aug. 22, 2013

Jenkins slaves

by Christophe Demarey

Hi all, An hypervisor used to host slaves for the continuous integration service is reaching its maximum storage capacity (primary storage used for running Virtual Machines). To avoid VM corruptions, we preventively stopped VMs running on this hypervisor. For the pharo ecosystem, following VMs are impacted: pharo linux-ubuntu-10-04 test2 pharo-contribution linux64-2 74 rmod windows-7-32 They will be restarted once the storage will be extended (probably in the beginning of the next week). If really needed, it is possible to create new slaves to substitute to these ones since they will be hosted on another hypervisor. Apologies for the inconvenience, Christophe.

Aug. 22, 2013

Re: [Pharo-dev] The future of SqueakSource

by Frank Shearar

On 21 August 2013 18:00, Andrei Vasile Chis <chisvasileandrei(a)gmail.com> wrote: > Hi all, > > We will shut down the SqueakSource image at the end of next week (30 August > 2013). > The current system will be replaced by a simple view of the file system > containing just the publicly visible projects. As meta-data, each project > will have it's overview page attached (showing the licence and its author). > > Please forward this email to other mailing lists. I've forwarded this mail to squeak-dev and vm-dev. Thanks for the warning, Andrei! frank

Aug. 21, 2013

Re: [Pharo-dev] Failing Pharo 2.0 test case (new)

by StÃ©phane Ducasse

thanks richard. I will forawrd your mail to the pharo mailing-list. Stef On Aug 21, 2013, at 6:34 PM, Richard Sargent <richard.sargent(a)gemtalksystems.com> wrote: > Hi Stephane, > > I was looking at some of the Pharo code and discovered a gap in the logic. (But is is perhaps a gap in my understanding of the underlying specification.) The same error may well be found in 3.0 (I have not checked). > > Try the following. > > UrlTest>>#testUsernameEncodedWithoutPassword2 > "Sometimes, weird usernames or passwords are necessary in applications, and, thus, we might receive them in a Url. The @ and the : are the kind of critical ones." > > #( "('user' 'pword' 'host' port 'path')" > ('StÃ©phane rst PÃ¼ckler' '' 'cottbus.brandenburg' 80 'mein/Zuhause') > ('Jeannde.d''Arc' '' 'orleans' 8080 'une/deux/trois') > ('HaXor@roxor:fnac' '' 'cbase' 42 'do/not_try') > ) do: [:urlParts | |theUrl| > theUrl := ('http://{1}@{3}:{4}/{5}' format: { > (urlParts at: 1) encodeForHTTP. > (urlParts at: 2) encodeForHTTP. > urlParts at: 3. urlParts at: 4. urlParts at: 5. > }) asUrl. > self assert: (theUrl schemeName = 'http'). > self assert: (theUrl username = (urlParts at: 1)). > self assert: (theUrl password = (urlParts at: 2)). > self assert: (theUrl authority = (urlParts at: 3)). > self assert: (theUrl port = (urlParts at: 4)). > self assert: theUrl path first = ((urlParts at: 5) copyUpTo: $/ )] > > -- > Richard Sargent > Business Development Manager > richard.sargent(a)gemtalksystems.com GemTalk Systems > 15220 NW Greenbrier Parkway #240 > Beaverton, OR 97006

Aug. 21, 2013

The future of SqueakSource

by Andrei Vasile Chis

Hi all, We will shut down the SqueakSource image at the end of next week (30 August 2013). The current system will be replaced by a simple view of the file system containing just the publicly visible projects. As meta-data, each project will have it's overview page attached (showing the licence and its author). Please forward this email to other mailing lists. Cheers, The SCG Team

Aug. 21, 2013

Re: [Pharo-dev] [update 3.0] #30338

by Camillo Bruni

On 2013-08-21, at 17:59, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Aug 21, 2013, at 5:44 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> On 2013-08-21, at 17:37, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>>> There are some problems in NativeBoost if a method does not belong to the >>>>> class itself, i don't understand the problem very well but that is what >>>>> Igor and Stef told me. >>> >>> >>> Some methods are placeholder for generated code and the placeholder cannot be avoided and there is nothing wrong in the design. >>> >>> This is why such system wide tests should be replaced by rules that each package declare as false positive and adapt to the package own >>> practice. >> >> but that doesn't justify that the methods have the same contents, AFAIK this is what the test compares. > > so do you think that we should generate method > value > 'foo1' > > value > 'foo2' > > value > 'foo3' > > just to satisfy a test that does not apply? I guess we can find another more creative solution, but yes, if it is in the kernel, I would suggest that we apply the same sane logics: - no/little code duplication - no/little use of #perform: / #doesNotUnderstand: magic If I see code that repeats the same method in it superclass I get confused since it breaks my assumptions about Pharo code.

Aug. 21, 2013

Re: [Pharo-dev] [update 3.0] #30338

by StÃ©phane Ducasse

On Aug 21, 2013, at 5:44 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > On 2013-08-21, at 17:37, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> There are some problems in NativeBoost if a method does not belong to the >>>> class itself, i don't understand the problem very well but that is what >>>> Igor and Stef told me. >> >> >> Some methods are placeholder for generated code and the placeholder cannot be avoided and there is nothing wrong in the design. >> >> This is why such system wide tests should be replaced by rules that each package declare as false positive and adapt to the package own >> practice. > > but that doesn't justify that the methods have the same contents, AFAIK this is what the test compares. so do you think that we should generate method value 'foo1' value 'foo2' value 'foo3' just to satisfy a test that does not apply? > > And I still think form a outside viewpoint duplicated methods do not make sense at all, NativeBoost should be no exception there. > >

Aug. 21, 2013

Re: [Pharo-dev] reflection examples

by StÃ©phane Ducasse

http://st-www.cs.illinois.edu/users/hanmer/PLoP-97/Proceedings.ps/auer.ps On Aug 21, 2013, at 9:46 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > > On Tue, Aug 20, 2013 at 10:40 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Aug 20, 2013, at 10:29 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> I am preparing a set of talks that have reflection at the center. >> >> Obviously, I want to use Pharo to demonstrate reflection. I am now looking for examples that can be explained to programmer newbies (actually, managers). I am particularly looking for examples that include adaptation (not just inspection) and that can show that reflection is valuable. >> >> I already have some examples in mind, but they might not appear particularly valuable. For example: >> - inspecting a class: Object methods. >> - adapting a class: Object compile: 'answer ^ 42'. > > Scaffolding patterns (read them) > Increase productivity when brainstorming. > > What patterns are you referring to specifically? Any link? > > Use DNU to compile on the fly some methods or to copy methods when you are designing a new piece of functionality > > Yes, that is a nice path, and I am looking for specific scenarios that can be used for a short demo. Any ideas? > > Proxy how to implement them nicely > > Proxies are indeed interesting and not difficult to explain, but the examples I think of (such as a facade, or a logger) do not really show adaptation. Does anyone have other examples? > > Cheers, > Doru > > > > >> Any suggestions? >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Aug. 21, 2013

Re: [Pharo-dev] [update 3.0] #30338

by Camillo Bruni

On 2013-08-21, at 17:37, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> There are some problems in NativeBoost if a method does not belong to the >>> class itself, i don't understand the problem very well but that is what >>> Igor and Stef told me. > > > Some methods are placeholder for generated code and the placeholder cannot be avoided and there is nothing wrong in the design. > > This is why such system wide tests should be replaced by rules that each package declare as false positive and adapt to the package own > practice. but that doesn't justify that the methods have the same contents, AFAIK this is what the test compares. And I still think form a outside viewpoint duplicated methods do not make sense at all, NativeBoost should be no exception there.

Aug. 21, 2013

Re: [Pharo-dev] [update 3.0] #30338

by StÃ©phane Ducasse

>> There are some problems in NativeBoost if a method does not belong to the >> class itself, i don't understand the problem very well but that is what >> Igor and Stef told me. Some methods are placeholder for generated code and the placeholder cannot be avoided and there is nothing wrong in the design. This is why such system wide tests should be replaced by rules that each package declare as false positive and adapt to the package own practice. Stef

Aug. 21, 2013

broken update

by Camillo Bruni

the last update fails https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/… what changed?

Aug. 21, 2013

Re: [Pharo-dev] default of completion

by Alexandre Bergel

Really? I will want to see that at esug :-) Alexandre On Aug 21, 2013, at 5:35 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > +100 > > On Aug 21, 2013, at 3:19 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Completion should always be on. If it is perceived to be not useful, it means the completion identification mechanism must be improved. Turning the completion off will not make it likely to improve the mechanism behind. >> >> Doru >> >> >> On Wed, Aug 21, 2013 at 3:02 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> use startup preferences and your done. >> @rmod we prefer it on. >> >> On 2013-08-21, at 15:00, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> >> > Hi! >> > >> > Should it not be better to have the automatic code completion turned off? >> > 90% of the time I do not want to see it. Am I the only one to experience this? >> > >> > I know this has been discussed some times ago, but this is really annoying. >> > >> > Alexandre >> > -- >> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> > Alexandre Bergel http://www.bergel.eu >> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> > >> > >> > >> > >> >> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 21, 2013

Re: [Pharo-dev] Pharo CI ConfigurationOfCI problem

by Camillo Bruni

there should be an /mc, I updated the configuration On 2013-08-21, at 17:09, Erwan Douaille <douailleerwan(a)gmail.com> wrote: > Hi, > > > 2013/8/21 Tommaso Dal Sasso <tommaso.dal.sasso(a)usi.ch> > >> Hi all, >> >> I'm playing with come ConfigurationOf for my project, but I am having >> troubles loading the Pharo CI project from SmallTalkHub at >> http://smalltalkhub.com/#!/~Pharo/ci >> When I try to load the project, an exception occurs, complaining that the >> ConfigurationOfXMLWriter cannot be found. >> >> Weird, i just tested it and its working. Did you load the latest > ConfigurationOfCI-ErwanDouaille.143 ? > > And then ConfigurationOfCI loadBleedingEdge. > > The problem seems to be in ConfigurationOfCI>>#xmlWriter, where the >> repository address is >> >> 'http://smalltalkhub.com/PharoExtras/XMLWriter/main' >> >> instead of >> >> 'http://smalltalkhub.com/mc/PharoExtras/XMLWriter/main' >> >> Still weird because mine is : > > repository: 'http://smalltalkhub.com/PharoExtras/XMLWriter/main'; > and its working :s > > >> With this correction I am able to complete the installation. >> Is it a typo or am I missing something? >> >> Thank you >> Tommaso Dal Sasso > > > -- > Best regards, > > Douaille Erwan <douaille.erwan(a)gmail.com>

Aug. 21, 2013

Re: [Pharo-dev] Pharo CI ConfigurationOfCI problem

by Erwan Douaille

Hi, 2013/8/21 Tommaso Dal Sasso <tommaso.dal.sasso(a)usi.ch> > Hi all, > > I'm playing with come ConfigurationOf for my project, but I am having > troubles loading the Pharo CI project from SmallTalkHub at > http://smalltalkhub.com/#!/~Pharo/ci > When I try to load the project, an exception occurs, complaining that the > ConfigurationOfXMLWriter cannot be found. > > Weird, i just tested it and its working. Did you load the latest ConfigurationOfCI-ErwanDouaille.143 ? And then ConfigurationOfCI loadBleedingEdge. The problem seems to be in ConfigurationOfCI>>#xmlWriter, where the > repository address is > > 'http://smalltalkhub.com/PharoExtras/XMLWriter/main' > > instead of > > 'http://smalltalkhub.com/mc/PharoExtras/XMLWriter/main' > > Still weird because mine is : repository: 'http://smalltalkhub.com/PharoExtras/XMLWriter/main'; and its working :s > With this correction I am able to complete the installation. > Is it a typo or am I missing something? > > Thank you > Tommaso Dal Sasso -- Best regards, Douaille Erwan <douaille.erwan(a)gmail.com>

Aug. 21, 2013

Pharo CI ConfigurationOfCI problem

by Tommaso Dal Sasso

Hi all, I'm playing with come ConfigurationOf for my project, but I am having troubles loading the Pharo CI project from SmallTalkHub at http://smalltalkhub.com/#!/~Pharo/ci When I try to load the project, an exception occurs, complaining that the ConfigurationOfXMLWriter cannot be found. The problem seems to be in ConfigurationOfCI>>#xmlWriter, where the repository address is 'http://smalltalkhub.com/PharoExtras/XMLWriter/main' instead of 'http://smalltalkhub.com/mc/PharoExtras/XMLWriter/main' With this correction I am able to complete the installation. Is it a typo or am I missing something? Thank you Tommaso Dal Sasso

Aug. 21, 2013

Re: [Pharo-dev] Sticky Morph ?

by Erwan Douaille

i will do it manually, whenMoved, if an other widget is close to 5 pixel then alignment. Thanks 2013/8/21 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > Not existing as far as I know :s > > On the other hand, it shouldn't be that complicated to have a manager for > that > > Ben > > On Aug 20, 2013, at 2:44 PM, Erwan Douaille <douailleerwan(a)gmail.com> > wrote: > > Hi, > > I'm looking for "sticky" morph. I means, i would like an automatic > alignment when 2 morphs are close both of them. > > There is already something existing ? > > I need it for the UIPainter canvas to make alignment more easier than > trying to move mouse when moprh are close to 1 pixel. > > Thanks for helping :) > > -- > Best regards, > > Douaille Erwan <douaille.erwan(a)gmail.com> > > > -- Best regards, Douaille Erwan <douaille.erwan(a)gmail.com>

Aug. 21, 2013

Re: [Pharo-dev] default of completion

by Esteban Lorenzano

+100 On Aug 21, 2013, at 3:19 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Completion should always be on. If it is perceived to be not useful, it means the completion identification mechanism must be improved. Turning the completion off will not make it likely to improve the mechanism behind. > > Doru > > > On Wed, Aug 21, 2013 at 3:02 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > use startup preferences and your done. > @rmod we prefer it on. > > On 2013-08-21, at 15:00, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > Hi! > > > > Should it not be better to have the automatic code completion turned off? > > 90% of the time I do not want to see it. Am I the only one to experience this? > > > > I know this has been discussed some times ago, but this is really annoying. > > > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Aug. 21, 2013

Re: [Pharo-dev] default of completion

by Tudor Girba

Completion should always be on. If it is perceived to be not useful, it means the completion identification mechanism must be improved. Turning the completion off will not make it likely to improve the mechanism behind. Doru On Wed, Aug 21, 2013 at 3:02 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > use startup preferences and your done. > @rmod we prefer it on. > > On 2013-08-21, at 15:00, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > Hi! > > > > Should it not be better to have the automatic code completion turned off? > > 90% of the time I do not want to see it. Am I the only one to experience > this? > > > > I know this has been discussed some times ago, but this is really > annoying. > > > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 21, 2013

Re: [Pharo-dev] default of completion

by Camillo Bruni

use startup preferences and your done. @rmod we prefer it on. On 2013-08-21, at 15:00, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > Should it not be better to have the automatic code completion turned off? > 90% of the time I do not want to see it. Am I the only one to experience this? > > I know this has been discussed some times ago, but this is really annoying. > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Aug. 21, 2013

default of completion

by Alexandre Bergel

Hi! Should it not be better to have the automatic code completion turned off? 90% of the time I do not want to see it. Am I the only one to experience this? I know this has been discussed some times ago, but this is really annoying. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 21, 2013

Re: [Pharo-dev] build times

by Camillo Bruni

More details of which test package consumed how much time: 30322 https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/405/label=… 30323 https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/406/label=… could it be, that the superclass method check causes so much more overhead? I definitely see 250 newly executed tests, but that accounts for ~2% of the tests... On 2013-08-21, at 14:36, Camillo Bruni <camillobruni(a)gmail.com> wrote: > The current build times for pharo are 3mins slower than when I left on holidays, what happened? > > https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/… > > => between august 5 and 6, we got 2.5 minutes slower under the mac slave! > > I assume it's update 30323 > https://github.com/pharo-project/pharo-core/commit/acf125b589ee03bef1d028dd…

Aug. 21, 2013

build times

by Camillo Bruni

The current build times for pharo are 3mins slower than when I left on holidays, what happened? https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/… => between august 5 and 6, we got 2.5 minutes slower under the mac slave! I assume it's update 30323 https://github.com/pharo-project/pharo-core/commit/acf125b589ee03bef1d028dd…

Aug. 21, 2013

Re: [Pharo-dev] reflection examples

by Dennis Schetinin

Wouldn't cooperative remote programing (when two or more developers are connected to the same image from local ones) require such (dynamic) adaptation? I mean, local proxies would have to reflect remote changes on-the-fly to reflect objects in browsers, inspectors etc. â¦Or, what do you mean by adaptation here? Any links to formally definitions will be appreciated. -- Best regards, Dennis Schetinin 2013/8/21 Tudor Girba <tudor(a)tudorgirba.com> > Hi, > > > On Tue, Aug 20, 2013 at 10:40 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> >> On Aug 20, 2013, at 10:29 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> I am preparing a set of talks that have reflection at the center. >> >> Obviously, I want to use Pharo to demonstrate reflection. I am now >> looking for examples that can be explained to programmer newbies (actually, >> managers). I am particularly looking for examples that include adaptation >> (not just inspection) and that can show that reflection is valuable. >> >> I already have some examples in mind, but they might not appear >> particularly valuable. For example: >> - inspecting a class: Object methods. >> - adapting a class: Object compile: 'answer ^ 42'. >> >> >> Scaffolding patterns (read them) >> Increase productivity when brainstorming. >> > > What patterns are you referring to specifically? Any link? > > >> Use DNU to compile on the fly some methods or to copy methods when you >> are designing a new piece of functionality >> > > Yes, that is a nice path, and I am looking for specific scenarios that can > be used for a short demo. Any ideas? > > >> Proxy how to implement them nicely >> > > Proxies are indeed interesting and not difficult to explain, but the > examples I think of (such as a facade, or a logger) do not really show > adaptation. Does anyone have other examples? > > Cheers, > Doru > > > >> >> >> Any suggestions? >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Aug. 21, 2013

Re: [Pharo-dev] [update 3.0] #30338

by Camillo Bruni

Thanks Sebastian, Stef/Igor more details please? On 2013-08-21, at 13:54, Sebastian Tleye <stleye(a)gmail.com> wrote: > There are some problems in NativeBoost if a method does not belong to the > class itself, i don't understand the problem very well but that is what > Igor and Stef told me. > > > 2013/8/21 Camillo Bruni <camillobruni(a)gmail.com> > >> On 2013-08-21, at 09:36, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> 30338 >>> ----- >>> >>> 11428 Remove a buggy redundant test in FuelTests >>> https://pharo.fogbugz.com/f/cases/11428 >>> >>> 11417 Test for checking repeated code in superclasses must not watch in >> nativeBoost classes >>> https://pharo.fogbugz.com/f/cases/11417 >> >> why do we exclude NativeBoost from this sanity check? >>

Aug. 21, 2013

Re: [Pharo-dev] [update 3.0] #30338

by Sebastian Tleye

There are some problems in NativeBoost if a method does not belong to the class itself, i don't understand the problem very well but that is what Igor and Stef told me. 2013/8/21 Camillo Bruni <camillobruni(a)gmail.com> > On 2013-08-21, at 09:36, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > 30338 > > ----- > > > > 11428 Remove a buggy redundant test in FuelTests > > https://pharo.fogbugz.com/f/cases/11428 > > > > 11417 Test for checking repeated code in superclasses must not watch in > nativeBoost classes > > https://pharo.fogbugz.com/f/cases/11417 > > why do we exclude NativeBoost from this sanity check? >

Aug. 21, 2013

Re: [Pharo-dev] [update 3.0] #30338

by Camillo Bruni

On 2013-08-21, at 09:36, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 30338 > ----- > > 11428 Remove a buggy redundant test in FuelTests > https://pharo.fogbugz.com/f/cases/11428 > > 11417 Test for checking repeated code in superclasses must not watch in nativeBoost classes > https://pharo.fogbugz.com/f/cases/11417 why do we exclude NativeBoost from this sanity check?

Aug. 21, 2013