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

[Pharo-project] FSGit for new Filesystem implementation
by Max Leske Aug. 8, 2011

Aug. 8, 2011

Hello everyone. I'm happy to announce that Camillo (with a little help from me) has adapted FSGit to run with the new Filesystem implementation (version 2.0.1). All tests are green. Nonetheless, please be careful when using it. There's also support for Monticello, although I haven't used that myself. AFAIK Camillo uses that part to store his Monticello versions in a git repository on his disk (correct me if I'm wrong). One new thing is that I wrote thorough tests for the handling of packs (thanks to Simon Denier for reporting the bug). Note that FSGit *cannot* write pack files and I have decided to not implement write support in the future (if someone else wants to however, I'm fine with that :) ). I'd like to thank all the people who have snuck looks at FSGit and pointed out important stuff. There's still a lot that can be improved but I feel that FSGit is on a good way. You can load FSGit through ConfigurationOfFSGit which you will find in the FSGit SqueakSource repository. This will also load Filesystem into the image. As usual, if you have suggestions or find a bug, hit me up directly or send an email to the list. Here's to the coolest Smalltalk environment available! :D Max

2 1

Re: [Pharo-project] [Vm-dev] Re: Troubles with #flushCache and #run:with:in:
by Jorge Ressia Aug. 8, 2011

Aug. 8, 2011

Hi Eliot, I am experiencing the same problem as Lukas. I was having random DNU on replaced methods. I fixed the problem by flushing the cache on the compiled methods only, before I was flushing on the selector and on the class. It is not yet clear to me what is the right way of flushing the cache. Any explanation on that? I think that this goes along with http://code.google.com/p/pharo/issues/detail?id=2255 http://forum.world.st/flushCache-with-MethoWrappers-in-CogVM-td3381310.html Eliot, if you need help debugging or testing a potential solution let me know, I have a bunch of test working on top of this. Cheers, On Mon, Jul 11, 2011 at 6:31 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi All, > Â Â Â I'm in touch with Lukas on this but have no time to address it right now. Â worry not :) > > On Mon, Jul 11, 2011 at 3:05 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> >> >> Maybe cc'ing VM mailing list can help. >> >> On Fri, Jul 1, 2011 at 9:32 AM, Lukas Renggli <renggli(a)gmail.com> wrote: >>> >>> Hi Eliot, >>> >>> I am using one of the latest VMs from your site (VM.r2434) and I >>> continue to have subtle problems with objects as methods (#flushCache, >>> #run:with:in:). >>> >>> The issue is that the test coverage in Pharo is kind of broken on Cog >>> for a long time already. It reports methods as not covered that are >>> clearly covered, and tests seem to randomly fail. >>> >>> I suspected that there is something wrong with the coverage code >>> itself. So I started to experiment with TestCoverage>>flushCache and >>> noticed that the current implementation >>> >>> Â Â TestCoverage>>flushCache >>> Â Â Â Â self reference methodSymbol flushCache >>> >>> performs not that well: The set of not covered methods is wrong and >>> many tests suddenly fail. If I replace it with >>> >>> Â Â TestCoverage>>flushCache >>> Â Â Â Â self reference actualClass flushCache >>> >>> I actually get accurate coverage information, but there are still a >>> few tests constantly failing. I tried to use all possible combinations >>> of #flushCache (also calling it on the compiled method), but only >>> flushing the cache on the class seems to work properly. So far so >>> good, but I really wonder what the correct way is to flush the cache? >>> :-) >>> >>> For my experiments I was using the package 'AST-Tests-Semantics'. This >>> is a small package with lots of test methods that cover each method >>> but one (RBSemanticAnnotationMisssing>>#isResumable). Now the "real" >>> problem is that when running these tests in coverage mode, the same 4 >>> tests always fail: >>> >>> Â Â RBSemanticTest>>testBlockScope >>> Â Â RBSemanticTest>>testCascadeReceiver >>> Â Â RBSemanticTest>>testClassVariableBinding >>> Â Â RBSemanticTest>>testGlobalVariableBinding >>> >>> Not sure of how to debug that? Do you have an idea why these otherwise >>> passing tests suddenly fail? If you want to try to reproduce you can >>> use any Pharo image with the tests loaded, or use those that I used: >>> >>> Â Â http://jenkins.lukas-renggli.ch/job/Development/lastSuccessfulBuild/artifac… >>> Â Â http://jenkins.lukas-renggli.ch/job/Development/lastSuccessfulBuild/artifac… >>> >>> Open the Test Runner, select 'AST-Tests-Semantics' and 'Run Coverage'. >>> >>> Any help or clarification would be appreciated :-) >>> >>> Lukas >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > > > > -- > best, > Eliot > > -- Jorge Ressia www.jorgeressia.com

1 0

[Pharo-project] Be careful, problem with WeakOrderedCollection in Pharo (there is a fix)
by Mariano Martinez Peck Aug. 8, 2011

Aug. 8, 2011

Hi Chris. We found a problem with WeakOrderedCollection in Pharo which may cause problems in Magma users in Pharo. Basically, once a WeakOrderedCollection needed to #grew, it stops being weak because the internal array was replaced by a Array instead of a WeakArray. (WeakOrderedCollection new instVarNamed: 'array') class ->>>> WeakArray (WeakOrderedCollection new grow instVarNamed: 'array') class ->>>> Array So....I can imagine that some applications running magma may grow a lot due to this bug. Just to check whether someone is having this bug or not, you may want to execute: WeakOrderedCollection allInstances select: [:each | (each instVarNamed: 'array') class = Array ] if you have instances, then that's a problem ;) To fix it, you can fileine the changes of the issue tracker: http://code.google.com/p/pharo/issues/detail?id=4596 and then you should fix the already created instances. cheers ps: I have no idea how much Magma uses WeakOrderedCollection, but I thought it was just worth it to raise a warning. -- Mariano http://marianopeck.wordpress.com

2 1

[Pharo-project] Build failed in Hudson: Pharo 1.3 #252
by marcus.denker＠inria.fr Aug. 8, 2011

Aug. 8, 2011

See <https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/252/> ------------------------------------------ D?marr? par le projet amont "Pharo Core 1.3" de num?ro de build 396 Construction ? distance sur pharo-build.lille.inria.fr [Pharo 1.3] $ /bin/sh -xe /tmp/hudson3266939052725223867.sh + /builds/builder/build13.sh -i Core1.3 -s dev3 -s pharo/version -o Pharo-1.3 [version] 1.3 #13296 + /builds/builder/build13.sh -i Pharo-1.3 -s testrunner -s delHDLintReport -s runalltests -o Pharo-1.3-AfterRunningTests + zip -r Pharo-1.3.zip Pharo-1.3/Pharo-1.3.changes Pharo-1.3/PharoV10.sources Pharo-1.3/Pharo-1.3.image updating: Pharo-1.3/Pharo-1.3.changes (deflated 79%) updating: Pharo-1.3/PharoV10.sources (deflated 76%) updating: Pharo-1.3/Pharo-1.3.image (deflated 57%) + zip -r Pharo-1.3-AfterRunningTests.zip Pharo-1.3-AfterRunningTests/Pharo-1.3-AfterRunningTests.changes Pharo-1.3-AfterRunningTests/Pharo-1.3-AfterRunningTests.image updating: Pharo-1.3-AfterRunningTests/Pharo-1.3-AfterRunningTests.changes (deflated 80%) updating: Pharo-1.3-AfterRunningTests/Pharo-1.3-AfterRunningTests.image (deflated 57%) + /builds/builder/build-oneclick.sh -i Pharo-1.3 -o PharoOneClick1.3 -n PharoOneClick1.3 -v 1.3 -c Pharo -t Pharo + sh /builds/builder/pharo-shell-scripts/SavePharo13.sh Archiving artifacts Enregistrement des r?sultats des tests ERROR: Failed to archive test reports hudson.util.IOException2: remote file operation failed: <https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/ws/> at hudson.remoting.Channel@18af45f9:pharo-build.lille.inria.fr at hudson.FilePath.act(FilePath.java:752) at hudson.FilePath.act(FilePath.java:738) at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:66) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:108) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:120) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:580) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:558) at hudson.model.Build$RunnerImpl.post2(Build.java:158) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528) at hudson.model.Run.run(Run.java:1264) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:122) Caused by: hudson.util.IOException2: Failed to read <https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/ws/Pharo-1.3-AfterRu…> at hudson.tasks.junit.TestResult.parse(TestResult.java:198) at hudson.tasks.junit.TestResult.parse(TestResult.java:139) at hudson.tasks.junit.TestResult.<init>(TestResult.java:102) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:95) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:70) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2028) at hudson.remoting.UserRequest.perform(UserRequest.java:114) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:270) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: org.dom4j.DocumentException: Error on line 3 of document file:///builds/workspace/Pharo%201.3/Pharo-1.3-AfterRunningTests/Refactoring-Tests-Spelling-Test.xml : XML document structures must start and end within the same entity. Nested exception: XML document structures must start and end within the same entity. at org.dom4j.io.SAXReader.read(SAXReader.java:482) at org.dom4j.io.SAXReader.read(SAXReader.java:264) at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:94) at hudson.tasks.junit.TestResult.parse(TestResult.java:183) ... 14 more Caused by: org.xml.sax.SAXParseException: XML document structures must start and end within the same entity. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.endEntity(XMLDocumentFragmentScannerImpl.java:905) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.endEntity(XMLDocumentScannerImpl.java:605) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.endEntity(XMLEntityManager.java:1393) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1763) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.peekChar(XMLEntityScanner.java:487) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2687) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at org.dom4j.io.SAXReader.read(SAXReader.java:465) ... 17 more Description set:

1 1

[Pharo-project] [update 1.3] #13298
by Marcus Denker Aug. 8, 2011

Aug. 8, 2011

13298 ----- Issue 4596: WeakOrderedColllection array is replaced by an Array instead of a WeakArray (Part5) - change #grow to use #arrayType. WeakOrderedCollection Tests are green. -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 1.3] #13297
by Marcus Denker Aug. 8, 2011

Aug. 8, 2011

13297 ----- Issue 4596: WeakOrderedColllection array is replaced by an Array instead of a WeakArray (Part4) -undo changes to #makeRoomAtFirst and #makeRoomAtLast -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 1.3] #13296
by Marcus Denker Aug. 8, 2011

Aug. 8, 2011

13296 ----- Issue 4596: WeakOrderedColllection array is replaced by an Array instead of a WeakArray (Part3) - put back #grow and #growSize -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Web app security
by Torsten Bergmann Aug. 8, 2011

Aug. 8, 2011

>What we are currently doing: >- integrate some vm patches (thanks Mariano :) from netstyle / seaside >hosting which limit file system / socket access Yes seasidehosting.st is running a modified VM to provide a more sandbox like environment. But one problem of port limitation is that it is not possible to send mails from the seasidehosting app (for instance for a registration step). That's OK since the hosting is free and it could be abused to send spam - but if you want to form a new Smalltalk based business and create a seaside app using SmallHarbour this may be something you will not miss in your shiny new online application. Maybe there could be two versions of SmallHarbour - an edition with limited rights for all and one with more rights for people/developers the community knows longer and trusts. Developers have to "earn" the second status (by providing extensions, code fixes,...) - this would also help moving Pharo/Seaside forward. It may also help to distinguish between "I just played with this stuff" (like most inactive accounts on seasidehosting prove) and real active users who may provide the next success story. Bye T. -- 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] Questions about Ocean
by Igor Stasenko Aug. 8, 2011

Aug. 8, 2011

1. why library does not serve as a factory for objects? I think it should, so one can write: library := MyLibrary new. socket := library createTcpSocket. socket connectTo: (library ipv4Address: 'x.y.z' port: 1000) I think it could simplify a lot of things. 2. what is OCNConversationTcpSocket and what its role? As to me it is unnecessary. I'd rather leave only single socket class in kernel. And for others, i think it would be better to use delegation instead of subclassing. So you will have: MyCustomRoleSocket (socket) -> OCNSocket (socketid, library) -> library with such encapsulation, you could ensure that you won't leak unwanted public/generic behavior outside of your model. While if you subclassing, it always takes everything as granted, and then it is unclear for user, what is safe to use and how. 3. Why OCNSocket keeps track its "state"? I think it would be better to always ask system about its state, because you never know for sure.. 4. error handling is below the waterline and needs to be addressed properly :) See the amount of error codes which connect() could produce. Where are they? Also, there is a lot of missing things for finer socket controls, like select(), poll(), fnctl() setsockopt() etc.. with all flags. So you have a lot to do :) 5. where i can put my code for NativeBoost backend of Ocean? 6. I understand that project is far from being complete, so don't treat my comments as an arrogant asshole. Just my thoughts, how it would be better to implement :) I created couple of classes and couple of tests (i could create socket, connect to remote host), but i stopping now, since of the above issues. Ideally, i would like to introduce you to NativeBoost and to see if you like it and if you can use it without my direct involvement (because it's already too much on my plate anyways ;) -- Best regards, Igor Stasenko AKA sig.

3 5

[Pharo-project] UTF-8 support when exporting to XML
by Hilaire Fernandes Aug. 8, 2011

Aug. 8, 2011

Hello, I am wondering, does latest XML Parser get the string value really exported to UTF-8. I am still using an old version #20 of XMLParser (for code compatibility) and I noted that Pharo accented string (still in 8 bits forms as far as I can see) are not converted to UTF-8 when exported in the XML file. Is it still the case with latest XML Parser? Hilaire -- Education 0.2 -- http://blog.ofset.org/hilaire

2 4