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

Re: [Pharo-project] GUI failing apart

by Nicolas Cellier

I also noted this: (Array does notUnderstand: #nextPut:) and it comes from: MouseOverHandler>>handleAsMouseEnter: anEvent | asMouseEnterEvent | asMouseEnterEvent := anEvent asMouseEnter. enteredMorphs := enteredMorphs contents. enteredMorphs reverseDo: [ :anEnteredMorph | self inform: asMouseEnterEvent to: anEnteredMorph originatedFrom: anEvent ifNotFocusedDo: [] ] enteredMorphs is changing indead from WriteStream -> Array. IMHO mutating an inst var is very bad behaved This should be corrected ASAP Nicolas 2011/8/8 Gary Chambers <gazzaguru2(a)btinternet.com>: > Looks like you may have changed one of the following methods: > > CharacterBlockScanner buildCharacterBlockIn: {private} > CharacterBlockScanner characterBlockAtPoint:index:in: {scanning} > NewParagraph defaultCharacterBlock {selection} > > since getting a CharacterBlockScanner back instead of a CharacterBlock in > MultiNewParagraph>>buildSelectionBlocksFrom:to: > > Regards, Gary > > ----- Original Message ----- From: "Janko MivÅ¡ek" <janko.mivsek(a)eranova.si> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Monday, August 08, 2011 6:29 PM > Subject: Re: [Pharo-project] GUI failing apart > > >> Here it is, in attachment, there actually are some GUI related >> exceptions captured. Troubles started an hour or so ago. >> >> Thanks for your time and best regards >> Janko >> >> S, Gary Chambers piÅ¡e: >>> >>> Your PharoDebug.log may have some clues... >>> >>> Regards, Gary >>> >>> ----- Original Message ----- From: "Janko MivÅ¡ek" >>> <janko.mivsek(a)eranova.si> >>> To: <Pharo-project(a)lists.gforge.inria.fr> >>> Sent: Monday, August 08, 2011 6:04 PM >>> Subject: [Pharo-project] GUI failing apart >>> >>> >>>> Hi guys, >>>> >>>> Strange things start happening to my 1.3 image. When edited some method >>>> it suddenly became covered with red, yellow crossed. Now other windows >>>> also have trouble to recreate when they come in focus. Not to mention >>>> many other such problems I cannot even describe. I somehow still manage >>>> to work with this image but with such trouble all the time. >>>> >>>> Is there a way to recover this image from such troubles? >>>> >>>> Best regards >>>> Janko >>>> >>>> -- >>>> Janko MivÅ¡ek >>>> Aida/Web >>>> Smalltalk Web Application Server >>>> http://www.aidaweb.si >>>> >>> >>> >>> >> >> -- >> 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 >> > > >

Aug. 8, 2011

Re: [Pharo-project] Be careful, problem with WeakOrderedCollection in Pharo (there is a fix)

by Chris Muller

Ok, thanks for the note. I just skimmed through the issue in tracker and it sounds like Marcus has it straightened out.. I'm glad Pharo decided to keep WeakOrderedCollection and refer to #arrayType in OrderedCollection rather than hard-coded Array. - Chris On Mon, Aug 8, 2011 at 6:21 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > 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 > > > _______________________________________________ > Magma mailing list > Magma(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/magma > >

Aug. 8, 2011

Re: [Pharo-project] Summary with UUID not so unique.

by Eliot Miranda

On Mon, Aug 8, 2011 at 1:13 AM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > Hi guys. Can someone do a summary of the problem of UUID not so unique? > because I have been bitten again. > In my image, primMakeUUID is still calling the primitive: > > primMakeUUID > <primitive: 'primitiveMakeUUID' module: 'UUIDPlugin'> > UUIDGenerator default generateBytes: self forVersion: 4. > > By my VM is still broken with this aspect. So....how should we deal with > it? > Update your VM. > > a) Change/Commmit/Integrate this: > > primMakeUUID > UUIDGenerator default generateBytes: self forVersion: 4. > > b) there are new Cog VMs somewhere that I can use with this problem fixed? > Yes. See http://www.mirandabanda.org/files/Cog/VM/VM.r2485/ > Thanks > > -- > Mariano > http://marianopeck.wordpress.com > > -- best, Eliot

Aug. 8, 2011

[Pharo-project] FSGit for new Filesystem implementation

by Max Leske

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

Aug. 8, 2011

Re: [Pharo-project] GUI failing apart

by Gary Chambers

Looks like you may have changed one of the following methods: CharacterBlockScanner buildCharacterBlockIn: {private} CharacterBlockScanner characterBlockAtPoint:index:in: {scanning} NewParagraph defaultCharacterBlock {selection} since getting a CharacterBlockScanner back instead of a CharacterBlock in MultiNewParagraph>>buildSelectionBlocksFrom:to: Regards, Gary ----- Original Message ----- From: "Janko MivÅ¡ek" <janko.mivsek(a)eranova.si> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Monday, August 08, 2011 6:29 PM Subject: Re: [Pharo-project] GUI failing apart > Here it is, in attachment, there actually are some GUI related > exceptions captured. Troubles started an hour or so ago. > > Thanks for your time and best regards > Janko > > S, Gary Chambers piÅ¡e: >> Your PharoDebug.log may have some clues... >> >> Regards, Gary >> >> ----- Original Message ----- From: "Janko MivÅ¡ek" >> <janko.mivsek(a)eranova.si> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Monday, August 08, 2011 6:04 PM >> Subject: [Pharo-project] GUI failing apart >> >> >>> Hi guys, >>> >>> Strange things start happening to my 1.3 image. When edited some method >>> it suddenly became covered with red, yellow crossed. Now other windows >>> also have trouble to recreate when they come in focus. Not to mention >>> many other such problems I cannot even describe. I somehow still manage >>> to work with this image but with such trouble all the time. >>> >>> Is there a way to recover this image from such troubles? >>> >>> Best regards >>> Janko >>> >>> -- >>> Janko MivÅ¡ek >>> Aida/Web >>> Smalltalk Web Application Server >>> http://www.aidaweb.si >>> >> >> >> > > -- > 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 >

Aug. 8, 2011

[Pharo-project] Hudson build is back to normal : Pharo 1.3 #253

by marcus.denker＠inria.fr

See <https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/253/>

Aug. 8, 2011

Re: [Pharo-project] GUI failing apart

by Janko MivÅ¡ek

Here it is, in attachment, there actually are some GUI related exceptions captured. Troubles started an hour or so ago. Thanks for your time and best regards Janko S, Gary Chambers piÅ¡e: > Your PharoDebug.log may have some clues... > > Regards, Gary > > ----- Original Message ----- From: "Janko MivÅ¡ek" <janko.mivsek(a)eranova.si> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Monday, August 08, 2011 6:04 PM > Subject: [Pharo-project] GUI failing apart > > >> Hi guys, >> >> Strange things start happening to my 1.3 image. When edited some method >> it suddenly became covered with red, yellow crossed. Now other windows >> also have trouble to recreate when they come in focus. Not to mention >> many other such problems I cannot even describe. I somehow still manage >> to work with this image but with such trouble all the time. >> >> Is there a way to recover this image from such troubles? >> >> Best regards >> Janko >> >> -- >> Janko MivÅ¡ek >> Aida/Web >> Smalltalk Web Application Server >> http://www.aidaweb.si >> > > > -- 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

Aug. 8, 2011

Re: [Pharo-project] GUI failing apart

by Gary Chambers

Your PharoDebug.log may have some clues... Regards, Gary ----- Original Message ----- From: "Janko MivÅ¡ek" <janko.mivsek(a)eranova.si> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Monday, August 08, 2011 6:04 PM Subject: [Pharo-project] GUI failing apart > Hi guys, > > Strange things start happening to my 1.3 image. When edited some method > it suddenly became covered with red, yellow crossed. Now other windows > also have trouble to recreate when they come in focus. Not to mention > many other such problems I cannot even describe. I somehow still manage > to work with this image but with such trouble all the time. > > Is there a way to recover this image from such troubles? > > Best regards > Janko > > -- > Janko MivÅ¡ek > Aida/Web > Smalltalk Web Application Server > http://www.aidaweb.si >

Aug. 8, 2011

[Pharo-project] GUI failing apart

by Janko MivÅ¡ek

Hi guys, Strange things start happening to my 1.3 image. When edited some method it suddenly became covered with red, yellow crossed. Now other windows also have trouble to recreate when they come in focus. Not to mention many other such problems I cannot even describe. I somehow still manage to work with this image but with such trouble all the time. Is there a way to recover this image from such troubles? Best regards Janko -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

Aug. 8, 2011

[Pharo-project] Build failed in Hudson: Pharo 1.3 #252

by marcus.denker＠inria.fr

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:

Aug. 8, 2011