- Pharo-dev - lists.pharo.org

[Pharo-project] citezen-pier broken
by Tudor Girba Aug. 15, 2011

Aug. 15, 2011

Hi, Citezen-Pier does not seem to work anymore. The first thing I noticed is that it still relies on Rio for accessing the bib file. I guess we should update it to work with Filesystem. Anyone happens to have an interest to work on it? Cheers, Doru -- www.tudorgirba.com "Some battles are better lost than fought."

2 1

[Pharo-project] Fwd: [Vm-dev] Socket's readSemaphore is losing signals with Cog on Linux
by StÃ©phane Ducasse Aug. 14, 2011

Aug. 14, 2011

can be a valuable information for some of you. Would be good to fix it for real. Stef Begin forwarded message: > From: Andreas Raab <andreas.raab(a)gmx.de> > Date: August 14, 2011 7:58:06 PM GMT+02:00 > To: vm-dev(a)lists.squeakfoundation.org > Subject: Re: [Vm-dev] Socket's readSemaphore is losing signals with Cog on Linux > Reply-To: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > > On 8/13/2011 13:42, Levente Uzonyi wrote: >> Socket's readSemaphore is losing signals with CogVMs on linux. We found several cases (RFB, PostgreSQL) when processes are stuck in the following method: >> >> Socket >> waitForDataIfClosed: closedBlock >> "Wait indefinitely for data to arrive. This method will block until >> data is available or the socket is closed." >> >> [ >> (self primSocketReceiveDataAvailable: socketHandle) >> ifTrue: [^self]. >> self isConnected >> ifFalse: [^closedBlock value]. >> self readSemaphore wait ] repeat >> >> When we inspect the contexts, the process is waiting for the readSemaphore, but evaluating (self primSocketReceiveDataAvailable: socketHandle) yields true. Signaling the readSemaphore makes the process running again. As a workaround we replaced #wait with #waitTimeoutMSecs: and all our problems disappeared. >> >> The interpreter VM doesn't seem to have this bug, so I guess the bug was introduced with the changes of aio.c. > > Oh, interesting. We know this problem fairly well and have always worked around by changing the wait in the above to a "waitTimeoutMSecs: 500" which turns it into a soft busy loop. It would be interesting to see if there's a bug in Cog which causes this. FWIW, here is the relevant portion: > > "Soft 500ms busy loop - to protect against AIO probs; > occasionally, VM-level AIO fails to trip the semaphore" > self readSemaphore waitTimeoutMSecs: 500. > > Cheers, > - Andreas >

1 0

[Pharo-project] Congratulations on help system
by Max Leske Aug. 14, 2011

Aug. 14, 2011

Just wanted to let the people who wrote the Pharo help system know that I think you did a great job. I especially enjoy the editor workspace for writing help texts (BTW: could autocompleteion and syntax highlighting be turned off by default for editor workspaces?). I encourage everyone to write for the help system. The help on help is an excellent tutorial that also shows how valuable the help system can be in getting to know a new tool. While I'm at it, I'll also write a small help part for Filesystem. Cheers, Max

1 0

[Pharo-project] BDD: Cucumber Toy Project
by Sean P. DeNigris Aug. 14, 2011

Aug. 14, 2011

I'm playing with Polymorph to make a BDD tool like Ruby's Cucumber (but infinitely better because we're in a live image and don't have to cram the infinite richness of our imagination into dead text, lol). It's amazing how a few lines of code got me *very* close to an active essay of the cucumber book's first example. Here is a screenshot of the Cucumber book: http://forum.world.st/file/n3742986/Screen_Shot_2011-08-14_at_10.30.11_AM.p… And here is a quick Polymorph view: http://forum.world.st/file/n3742986/Screen_Shot_2011-08-14_at_10.29.44_AM.p… Hopefully I'll have something we can play with by ESUG! Sean -- View this message in context: http://forum.world.st/BDD-Cucumber-Toy-Project-tp3742986p3742986.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

3 2

[Pharo-project] formatting style
by StÃ©phane Ducasse Aug. 13, 2011

Aug. 13, 2011

I know that you all have your own hyper cool view on formatting. =========================================== Now I would really like that we agree on the minimum put a space after a variable and before := stamp: anObject "stores an author alias and a timestamp" stamp := anObject instead of stamp: anObject "stores an author alias and a timestamp" stamp:= anObject =========================================== Put a space before method argument stamp: anObject "stores an author alias and a timestamp" stamp := anObject instead of stamp:anObject "stores an author alias and a timestamp" stamp := anObject =========================================== Put a space after ifNil: ifTrue: ....

7 14

[Pharo-project] Thanks Jenkins/Marcus
by Mariano Martinez Peck Aug. 13, 2011

Aug. 13, 2011

Since several months, Fuel tests in Jenkins were all red. We never could understood why because of course in our machines it worked. We tried in Mac, Linux and Windows. All were working correctly. Only Hudson was failing. Of course, we blamed Hudson, Cog, the OS, Marcus (hahhaahaha), everyone. Today, after a couple of hours we finally found the problem. Guess what? of course, it was a bug in Fuel!!! It is difficult to explain why it was only failing in Jenkins. But anyway, thanks for such great tool. Now, every single commit in Fuel fires up a build in Jenkins and run our 162 tests. All green so far. Finally, in Fuel, speed is very important and hence we have a large set of benchmarks. I would LOVE to be able to run benchmarks in addition to tests and then watch nice graphs where I can notice which commit made Fuel faster or slower. Thanks! -- Mariano http://marianopeck.wordpress.com

1 0

[Pharo-project] PPElementParser & a small PetitTests contribution
by Damien Pollet Aug. 13, 2011

Aug. 13, 2011

While we're at it, I committed a tiny change to the assertions in PPAbstractParserTest, so that assertions return the parse result. I needed it for cases where I don't want to compare to an expected result, but still make further assertions than just "yup, it parses". For Coral I also wrote a simple PPDelegateParser subclass that applies its inner parser to the stream first element. It's like: PPPredicateObjectParser>>matching: elementParser message: aString ^ self on: [ :each | elementParser matches: each ] message: aString BUT: it will return the parse result of its inner parser, rather than the accepted element as-is. I use it to parse the argument array in a Coral script, some arguments are expected to be integers or other parseable. It allows me to predefine a bunch of utility parsers for simple argument types, that return a ready-to-use object. If you want to see the code, it's PPElementParser in the Coral package http://www.squeaksource.com/Coral.html but mostly it looks like this: parseOn: aStream | result | aStream atEnd ifTrue: [ ^ PPFailure message: 'element expected' at: aStream position ]. result := parser "end" parse: aStream uncheckedPeek. ^ result isPetitFailure ifFalse: [ aStream next. result ] ifTrue: [ PPFailure message: (message ifNil: ['error: ' , result printString , ' in element']) at: aStream position ] What do you think? I'm still not sure what the best way is. I hesitated between subclassing PPDelegateParser, PPLiteralParserâ¦ maybe a factory method in PPPredicateObjectParser would work as well: -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

2 16

[Pharo-project] Pharo/Seaside Experience Report
by Torsten Bergmann Aug. 13, 2011

Aug. 13, 2011

Nice post on using Pharo/Seaside: http://articles.tulipemoutarde.be/pharo-smalltalk-experience-report-part-i -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

2 1

[Pharo-project] is there a way I can see the PharoDebug of a hudson job?
by Mariano Martinez Peck Aug. 13, 2011

Aug. 13, 2011

because a test is red and I don't have enough information with the small stack show in Hudson. THanks -- Mariano http://marianopeck.wordpress.com

3 3

[Pharo-project] Why is #stepTime in the 'testing' protocol?
by Sean P. DeNigris Aug. 13, 2011

Aug. 13, 2011

It should be in 'stepping and presenter' with the other step methods, no? S -- View this message in context: http://forum.world.st/Why-is-stepTime-in-the-testing-protocol-tp3740584p374… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1