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

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