- Pharo-dev - lists.pharo.org

[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

[Pharo-project] Debug it from browser, menu consistency, merged Inspector
by Janko MivÅ¡ek Aug. 8, 2011

Aug. 8, 2011

Hi guys, I just noticed that there is no 'Debug it' in browser's right-click menu, but it is on Workspace. It would be nice to be there too, and there is a place for it. But not need to add Profile it and Watch it in browser's one. Debug it is important for "through debugger" development style .. :) Second usability suggestion: please put Cut/Copy/Paste/Undo section consistently on the same place, or always on the top, or always somewhere else. Not on the bottom as is in context menu in Workspace while in browser it is on top. Same goes with DoIt/PrintIt/DebugIt block. Third: how is the state with merging Inspector and Explorer? Wasn't there already a nice tree-view Inspector in some older Pharo? Best regards Janko -- Janko MivÅ¡ek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565

4 4

[Pharo-project] [update 1.4] #14078
by Marcus Denker Aug. 8, 2011

Aug. 8, 2011

14078 ----- - add ensureCr for vmmaker compatibility to Transcript -- Marcus Denker -- http://marcusdenker.de

1 0

Aug. 8, 2011

Hi I was brainstorming for an example to illustrate announcements and I wanted to have a Growl feature. So I looked at Snarl from Tony Garnock-Jones and I redesigned a simpler Morph. It could be more generic with better default handled default. I do not understand why the color of the text is ignored but I can not want to spend more time on it now. Apparently the first time the text is read and when the background or the color of the border are set the blue get propagated. :( GrowlMorph openWithLabel: 'The time' contents: (TimeStamp now)) If somebody would like to glue together Growl and the available announcements it would be fun to check. Gofer new squeaksource: 'Growl'; package: 'Growl'; load GrowlMorph openWithLabel: 'The time' contents: (TimeStamp now) Stef Something changed between 14042 and 14077 because I do not have the same alpha for the handle but I do not have the time to check. I do not understand why round corners are not taken into account.

2 4