April 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Invalid socket handle in Zinc Server after image startup

by StÃ©phane Ducasse

I'm trying to make sven write a chapter :) So I added it to the server section :) Stef > Hi Sven, > > That makes a lot of sense :). > > Perhaps this could be added to the Getting Started section of the website? > > Thanks! > > Mark > > On 8 Apr 2012, at 17:11, Sven Van Caekenberghe wrote: > >> Mark, >> >> On 08 Apr 2012, at 16:11, Mark Smith wrote: >> >>> Hi all, >>> >>> Is anyone else having problems with Zinc servers not starting up correctly when the image is loaded? >>> >>> After the image starts up the server has an invalid socket handle. >>> >>> To reproduce, evaluate the following in a workspace, then save and quit the image. >>> >>> aServer := ZnServer on: 8080. >>> aServer delegate: ((ZnMonticelloServerDelegate new) >>> directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). >>> aServer start >>> >>> Any ideas? >>> >>> Mark >> >> Only the default server (ZnServer default) is sent #register on #start so that it will be sent #start/#stop on System #startUp/#shutDown. >> Have a look at ZnSingleThreadedServer>>#start and/or follow ZnServer>>#register. >> >> To make this work, either change your example to >> >> aServer := ZnServer defaultOn: 8080. >> aServer delegate: ((ZnMonticelloServerDelegate new) >> directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). >> aServer start >> >> or to >> >> aServer := ZnServer on: 8080. >> aServer delegate: ((ZnMonticelloServerDelegate new) >> directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). >> aServer register. >> aServer start >> >> It is by design that not every server is registered (as not everyone needs this behavior). >> The default server is an exception because it is used for first time and more casual usage and many people expect this behavior in Smalltalk. >> >> HTH, >> >> Sven >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> > >

April 8, 2012

[Pharo-project] Milestone reached :-)

by Pavel Krivanek

Hi, I created an experimental CI build that loads Fuel into the Pharo Kernel, unloads Compiler and uses an special launcher that expects a binary package name as command line argument. https://ci.lille.inria.fr/pharo/view/Pharo-Kernel/job/Pharo%20Kernel%20Fuel/ You can test it with something like (see attachment): CogVM PharoKernel-Fuel-1.4.image testingPackage.fuel Following code exports a fuel binary package from the image: FileStream forceNewFileNamed: 'testingPackage.fuel' do: [:aStream | aStream binary. FLPackageStore new storeOn: aStream packageNamed: 'TestingPackage'.]. As you can see from the output of the testing class, there is no Compiler class in the image. Cheers, -- Pavel

April 8, 2012

Re: [Pharo-project] Invalid socket handle in Zinc Server after image startup

by Mark Smith

Hi Sven, That makes a lot of sense :). Perhaps this could be added to the Getting Started section of the website? Thanks! Mark On 8 Apr 2012, at 17:11, Sven Van Caekenberghe wrote: > Mark, > > On 08 Apr 2012, at 16:11, Mark Smith wrote: > >> Hi all, >> >> Is anyone else having problems with Zinc servers not starting up correctly when the image is loaded? >> >> After the image starts up the server has an invalid socket handle. >> >> To reproduce, evaluate the following in a workspace, then save and quit the image. >> >> aServer := ZnServer on: 8080. >> aServer delegate: ((ZnMonticelloServerDelegate new) >> directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). >> aServer start >> >> Any ideas? >> >> Mark > > Only the default server (ZnServer default) is sent #register on #start so that it will be sent #start/#stop on System #startUp/#shutDown. > Have a look at ZnSingleThreadedServer>>#start and/or follow ZnServer>>#register. > > To make this work, either change your example to > > aServer := ZnServer defaultOn: 8080. > aServer delegate: ((ZnMonticelloServerDelegate new) > directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). > aServer start > > or to > > aServer := ZnServer on: 8080. > aServer delegate: ((ZnMonticelloServerDelegate new) > directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). > aServer register. > aServer start > > It is by design that not every server is registered (as not everyone needs this behavior). > The default server is an exception because it is used for first time and more casual usage and many people expect this behavior in Smalltalk. > > HTH, > > Sven > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill >

April 8, 2012

Re: [Pharo-project] Invalid socket handle in Zinc Server after image startup

by Sven Van Caekenberghe

Mark, On 08 Apr 2012, at 16:11, Mark Smith wrote: > Hi all, > > Is anyone else having problems with Zinc servers not starting up correctly when the image is loaded? > > After the image starts up the server has an invalid socket handle. > > To reproduce, evaluate the following in a workspace, then save and quit the image. > > aServer := ZnServer on: 8080. > aServer delegate: ((ZnMonticelloServerDelegate new) > directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). > aServer start > > Any ideas? > > Mark Only the default server (ZnServer default) is sent #register on #start so that it will be sent #start/#stop on System #startUp/#shutDown. Have a look at ZnSingleThreadedServer>>#start and/or follow ZnServer>>#register. To make this work, either change your example to aServer := ZnServer defaultOn: 8080. aServer delegate: ((ZnMonticelloServerDelegate new) directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). aServer start or to aServer := ZnServer on: 8080. aServer delegate: ((ZnMonticelloServerDelegate new) directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). aServer register. aServer start It is by design that not every server is registered (as not everyone needs this behavior). The default server is an exception because it is used for first time and more casual usage and many people expect this behavior in Smalltalk. HTH, Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

April 8, 2012

Re: [Pharo-project] Invalid socket handle in Zinc Server after image startup

by StÃ©phane Ducasse

On Apr 8, 2012, at 4:11 PM, Mark Smith wrote: > aServer := ZnServer on: 8080. > aServer delegate: ((ZnMonticelloServerDelegate new) > directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). > aServer start I changed the path and in my browser I get the list of mcz file. I saved and restarted my image and I got the same

April 8, 2012

[Pharo-project] Invalid socket handle in Zinc Server after image startup

by Mark Smith

Hi all, Is anyone else having problems with Zinc servers not starting up correctly when the image is loaded? After the image starts up the server has an invalid socket handle. To reproduce, evaluate the following in a workspace, then save and quit the image. aServer := ZnServer on: 8080. aServer delegate: ((ZnMonticelloServerDelegate new) directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). aServer start Any ideas? Mark

April 8, 2012

Re: [Pharo-project] tail-like

by drush66

Tudor Girba-2 wrote > > Thanks. I will take a look. > I think that dearly missed Dolphin Smalltalk had implementation for Windows, so you could also grab Dolphin Community Edition and take a look how it is implemented there. Davorin Rusevljan http://www.cloud208.com/ ----- http://www.cloud208.com/ -- View this message in context: http://forum.world.st/tail-like-tp4535899p4540785.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 8, 2012

Re: [Pharo-project] tail-like

by drush66

Tudor Girba-2 wrote > > Thanks. I will take a look. > I think that dearly missed Dolphin Smalltalk had implementation for Windows, so you could also grab Dolphin Community Edition and take a look how it is implemented there. Davorin Rusevljan http://www.cloud208.com/ ----- http://www.cloud208.com/ -- View this message in context: http://forum.world.st/tail-like-tp4535899p4540784.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 8, 2012

Re: [Pharo-project] Issue 5445: Broken command-line arguments in 1.4

by StÃ©phane Ducasse

On Apr 7, 2012, at 10:11 PM, Michael Roberts wrote: > Cool! ...have been offline for a bit but will definitely test any fixes out. Need to dig out my debugger test harness as well. we will look at your description and tests :) Esteban is pushing us he wants opal debugger fixe event fixes spec removing old tools â¦ PharoCore better management with metacelloâ¦. and fast :) So this is cool. Stef > > Mike > > On Saturday, April 7, 2012, StÃ©phane Ducasse wrote: > Thanks michael > > BTW esteban will work on the debugger bugs :) > > Stef > > On Apr 7, 2012, at 2:33 PM, Michael Roberts wrote: > > > Hi, i tested the fix in 1.4 and it seemed to work fine. > > > > http://code.google.com/p/pharo/issues/detail?id=5445 > > > > > > thanks, > > Mike > > > >

April 7, 2012

Re: [Pharo-project] Issue 5445: Broken command-line arguments in 1.4

by Michael Roberts

Cool! ...have been offline for a bit but will definitely test any fixes out. Need to dig out my debugger test harness as well. Mike On Saturday, April 7, 2012, StÃ©phane Ducasse wrote: > Thanks michael > > BTW esteban will work on the debugger bugs :) > > Stef > > On Apr 7, 2012, at 2:33 PM, Michael Roberts wrote: > > > Hi, i tested the fix in 1.4 and it seemed to work fine. > > > > http://code.google.com/p/pharo/issues/detail?id=5445 > > > > > > thanks, > > Mike > > > > >

April 7, 2012