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

Re: [Pharo-project] Networking change in Pharo 1.2?

by Marcus Denker

On Apr 17, 2011, at 10:48 PM, Chris Muller wrote: > I was able to work on getting Magma 1.2 going in Pharo. It was quite > easy to get the code loaded and functioning in Pharo 1.1.1, Pharo 1.2, > and Pharo 1.3. > > But something seems to have changed in Pharo's networking from 1.1.1 > to 1.2. All Magma functionality seems to work fine for low-volume > activity. However, when the test-suite gets to the HA test cases (at > the end), one of the images performing heavy networking activity, > consistently gets very slow and bogged down for some reason; causing > the clients to timeout and disrupting the test suite. Fortunately, it > happens in the same place in the test-suite every time. > > The UI of the image in question becomes VERY sluggish, but > MessageTally spyAllOn: didn't reveal anything useful. What is it > doing? I did verify that the Magma server in that image is still > functioning; clients were committing, but I had to increase their > timeouts from 10 to 45 seconds to avoid timeouts.. > Oh... this could be related to finalization / weak references in some way? > Unfortunately, two days of wrangling in Pharo (because I'm an old > Squeak dog) I could not nail the problem down; but I have one > suspect.. A couple of times, I caught a process seemingly hung up in > NetworkNameResolver; trying to resolve an IP from 'localhost'. > The only change to NetNameResolver was this: http://code.google.com/p/pharo/issues/detail?id=1853 Socket in general did not see many changes: http://code.google.com/p/pharo/issues/list?can=1&q=milestone%3D1.2+Socket > This exact set of Magma packages is rock-solid on Pharo 1.1.1 and > Squeak, but that doesn't mean the problem for sure lies in Pharo 1.2; > maybe a networking bug in 1.1.1 is allowing Magma to "misuse" the > network and get away with it and Pharo 1.2 is now more strict? I > don't know, I would just like to ask the experts here for help who > know all what went into Pharo 1.2 so hopefully we can get to the > bottom of it. > > Thanks, > Chris > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 18, 2011

Re: [Pharo-project] [COTDC] 49 - ClassFactoryWithOrganization

by Alexandre Bergel

I am similar to ClassFactoryForTestCase (i.e., I can be used in place of a ClassFactoryForTestCase), expect that classes may be created on a specific class category. Alexandre On 17 Apr 2011, at 15:36, StÃ©phane Ducasse wrote: > I'm a class to create classes with a category. I'm only used by Tests. > > > On Apr 17, 2011, at 9:26 PM, laurent laffont wrote: > >> ClassFactoryWithOrganization > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 18, 2011

Re: [Pharo-project] Networking change in Pharo 1.2?

by Elliot Finley

On Sun, Apr 17, 2011 at 2:48 PM, Chris Muller <ma.chris.m(a)gmail.com> wrote: > Unfortunately, two days of wrangling in Pharo (because I'm an old > Squeak dog) I could not nail the problem down; but I have one > suspect.. Â A couple of times, I caught a process seemingly hung up in > NetworkNameResolver; trying to resolve an IP from 'localhost'. probably related to this: http://lists.squeakfoundation.org/pipermail/magma/2010-September/001594.html

April 17, 2011

Re: [Pharo-project] OSProcess and CommandShell

by Mariano Martinez Peck

Can you try evaluating ConfigurationOfMetacello project latestVersion load. And then Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfOSProcess'; load. ((Smalltalk at: #ConfigurationOfOSProcess) project version: #stable) load. if it works, I explain you what it was. On Sun, Apr 17, 2011 at 8:18 PM, sourav roy <sourav_pharo(a)in.com> wrote: > hi.... > while loading i m getting some error. Please advice... > > c the attachment > > Thanks > Sourav > > > ---------- Original message ---------- > From:"Miguel CobÃ¡"< miguel.coba(a)gmail.com > > Date: 14 Apr 11 01:59:21 > Subject: Re: [Pharo-project] OSProcess and CommandShell > To: Pharo-project(a)lists.gforge.inria.fr > > OSProcess is supported and all tests are green in Pharo 1.1 and Pharo > 1.2. > > The stable version for Pharo 1.2 is the 4.4.0 but you can also load and > run 4.3.11 and 4.3.12 (although if you don't disable deprecations > warnings a lot of pop ups will show). 4.4.0 doesn't have problems with > deprecated methods. > > To load: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfOSProcess'; > load. > > ((Smalltalk at: #ConfigurationOfOSProcess) project version: #stable) > load. > > C ommandShell hasn't a configuration so you'll have to load it from the > > monticello repository following the documentation of it somewhere in the > wiki. > > Cheers > > El miÃ©, 13-04-2011 a las 15:23 -0300, Casimiro de Almeida Barreto > escribiÃ³: > > I'd like to know the state of: > > > > OSProcess > > and > > CommandShell > > > > under pharo. > > > > There's a ConfigurationOfOSProcess but there's no > > ConfigurationOfCommandShell. > > > > What's working and what's not working? > > > > Best regards > > > > CdAB > > > > -- > Miguel CobÃ¡ > http://twitter.com/MiguelCobaMtz > http://miguel.leugim.com.mx > > > > > > > Get Your self a cool, short *(a)in.com* Email ID now!<http://mail.in.com/mails/new_reg.php?utm_source=invite&utm_medium=outgoing> > -- Mariano http://marianopeck.wordpress.com

April 17, 2011

Re: [Pharo-project] Networking change in Pharo 1.2?

by Schwab,Wilhelm K

Two thoughts: (1) Gary recently mentioned a delay fix that IIRC was in Squeak but had not yet made it into Pharo. It might be central to the problem?? (2) Not to say that the test should take so long to run, the but network layer should not be timing out at all. Decisions of when to give up should be left to the application and indirectly the user - assuming the machine is attended (the app will "know" that, which the network layer cannot). Attempts to connect or do I/O should do just that until they are told to stop. Servers should listen and accept connections until they are stopped. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Chris Muller [ma.chris.m(a)gmail.com] Sent: Sunday, April 17, 2011 4:48 PM To: Pharo-project(a)lists.gforge.inria.fr; magma Subject: [Pharo-project] Networking change in Pharo 1.2? I was able to work on getting Magma 1.2 going in Pharo. It was quite easy to get the code loaded and functioning in Pharo 1.1.1, Pharo 1.2, and Pharo 1.3. But something seems to have changed in Pharo's networking from 1.1.1 to 1.2. All Magma functionality seems to work fine for low-volume activity. However, when the test-suite gets to the HA test cases (at the end), one of the images performing heavy networking activity, consistently gets very slow and bogged down for some reason; causing the clients to timeout and disrupting the test suite. Fortunately, it happens in the same place in the test-suite every time. The UI of the image in question becomes VERY sluggish, but MessageTally spyAllOn: didn't reveal anything useful. What is it doing? I did verify that the Magma server in that image is still functioning; clients were committing, but I had to increase their timeouts from 10 to 45 seconds to avoid timeouts.. Unfortunately, two days of wrangling in Pharo (because I'm an old Squeak dog) I could not nail the problem down; but I have one suspect.. A couple of times, I caught a process seemingly hung up in NetworkNameResolver; trying to resolve an IP from 'localhost'. This exact set of Magma packages is rock-solid on Pharo 1.1.1 and Squeak, but that doesn't mean the problem for sure lies in Pharo 1.2; maybe a networking bug in 1.1.1 is allowing Magma to "misuse" the network and get away with it and Pharo 1.2 is now more strict? I don't know, I would just like to ask the experts here for help who know all what went into Pharo 1.2 so hopefully we can get to the bottom of it. Thanks, Chris

April 17, 2011

[Pharo-project] Networking change in Pharo 1.2?

by Chris Muller

I was able to work on getting Magma 1.2 going in Pharo. It was quite easy to get the code loaded and functioning in Pharo 1.1.1, Pharo 1.2, and Pharo 1.3. But something seems to have changed in Pharo's networking from 1.1.1 to 1.2. All Magma functionality seems to work fine for low-volume activity. However, when the test-suite gets to the HA test cases (at the end), one of the images performing heavy networking activity, consistently gets very slow and bogged down for some reason; causing the clients to timeout and disrupting the test suite. Fortunately, it happens in the same place in the test-suite every time. The UI of the image in question becomes VERY sluggish, but MessageTally spyAllOn: didn't reveal anything useful. What is it doing? I did verify that the Magma server in that image is still functioning; clients were committing, but I had to increase their timeouts from 10 to 45 seconds to avoid timeouts.. Unfortunately, two days of wrangling in Pharo (because I'm an old Squeak dog) I could not nail the problem down; but I have one suspect.. A couple of times, I caught a process seemingly hung up in NetworkNameResolver; trying to resolve an IP from 'localhost'. This exact set of Magma packages is rock-solid on Pharo 1.1.1 and Squeak, but that doesn't mean the problem for sure lies in Pharo 1.2; maybe a networking bug in 1.1.1 is allowing Magma to "misuse" the network and get away with it and Pharo 1.2 is now more strict? I don't know, I would just like to ask the experts here for help who know all what went into Pharo 1.2 so hopefully we can get to the bottom of it. Thanks, Chris

April 17, 2011

Re: [Pharo-project] [COTDC] 49 - ClassFactoryWithOrganization

by StÃ©phane Ducasse

I'm a class to create classes with a category. I'm only used by Tests. On Apr 17, 2011, at 9:26 PM, laurent laffont wrote: > ClassFactoryWithOrganization

April 17, 2011

[Pharo-project] [COTDC] 49 - ClassFactoryWithOrganization

by laurent laffont

Today: ClassFactoryWithOrganization Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

April 17, 2011

Re: [Pharo-project] OSProcess and CommandShell

by sourav roy

hi....while loading i m getting some error. Please advice...c the attachmentThanksSourav Original message From:"Miguel CobÃ¡"< miguel.coba(a)gmail.com >Date: 14 Apr 11 01:59:21Subject: Re: [Pharoproject] OSProcess and CommandShellTo: Pharoproject(a)lists.gforge.inria.frOSProcess is supported and all tests are green in Pharo 1.1 and Pharo1.2.The stable version for Pharo 1.2 is the 4.4.0 but you can also load andrun 4.3.11 and 4.3.12 (although if you don't disable deprecationswarnings a lot of pop ups will show). 4.4.0 doesn't have problems withdeprecated methods.To load:Gofer newsqueaksource: 'MetacelloRepository';package: 'ConfigurationOfOSProcess';load.((Smalltalk at: #ConfigurationOfOSProcess) project version: #stable)load.CommandShell hasn't a configuration so you'll have to load it from themonticello repository following the documentation of it somewhere in thewiki.CheersEl miÃ©, 13042011 a las 15:23 0300, Casimiro de Almeida BarretoescribiÃ³:> I'd like to know the state of:> > OSProcess> and> CommandShell> > under pharo.> > There's a ConfigurationOfOSProcess but there's no> ConfigurationOfCommandShell.> > What's working and what's not working?> > Best regards> > CdAB> Miguel CobÃ¡http://twitter.com/MiguelCobaMtzhttp://miguel.leugim.com.mxGet Yourself a cool, short @in.com Email ID now!

April 17, 2011

[Pharo-project] Status of Magma on Pharo 1.2

by Miguel CobÃ¡

Hi all, a lot of messages have been sent asking about the status of Magma on Pharo and in particular on Pharo 1.2. Here is it. Magma latest version (1.2) isn't working on Pharo 1.2. This is due to some changes that Pharo 1.2 have and some changes that Magma 1.2 uses that only were on Squeak 4.2. As they are very difficult to integrate now that Pharo 1.2 is out, they are targetted to Pharo 1.3. So, Magma 1.2 (or greater) will only be available to Pharo 1.3. Now, what if I want to use Magma in Pharo 1.2 right now. Well, your only option is Magma 1.1r1. Is that bad, I don't think so, as the new releases of magma are mostly about performance and not about new functionality. So for a OO database, 1.1r1 is as good as 1.2. So mind not about it. Now, to load it, evaluate in a workspace: Deprecation raiseWarning: false. Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMagma'; load. ((Smalltalk at: #ConfigurationOfMagma) project version: #stable) load: 'Tester'. Currenty 1.1r1 is the stable version for Pharo 1.2.x. Then create a directory for the repo (magma in this case) and evaluate: MagmaRepositoryController create: 'magma/' root: Dictionary new. Start the magma server MagmaServerConsole new open: 'magma/'; processOn: 51969; inspect. Connect to magma (MagmaSession host: 'localhost' port: 51969) connectAs: 'miguel'; inspect. In the window opened by the last doit (the connection window) evaluate: self root inspect and then self root at #miguel put: OrderedCollection new and then again: self root inspect. add some value: (self root at: #miguel) add: 'Hello world' read that value (print it) (self root at: #miguel) first "-> 'Hello world' Chris Muller is kindly working on the issues found in order to make latest Magma working in Pharo. When he publishes a new version I will update the ConfiguratioOfMagma, pointing #stable to the new version. Until then, 1.1r1 should work. Cheers -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

April 17, 2011