July 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [squeak-dev] BlockClosure asContext losing bound variable?

by Levente Uzonyi

On Thu, 1 Jul 2010, Eliot Miranda wrote: > Hi Rob, Hi All, > > On Sun, Jun 27, 2010 at 3:34 PM, Rob Withers <reefedjib(a)yahoo.com> wrote: > >> I am getting a walkback on this code, with a valid vat: >> >> EventualProcess class>>#newOnVat: vat >> ^ super new >> suspendedContext: [ >> vat processSends. >> Processor terminateActive] asContext; >> priority: Processor userSchedulingPriority; >> eventualName: 'vat thread'; >> vat: vat; >> yourself >> >> once it has been resumed. The exception is >> UndefinedObject(Object)>>doesNotUnderstand: #processSends. Somehow the vat >> variable inside the Closure/MethodContext has become nil. Anyone know >> about this stuff? >> > > > This is due to a bad bug i the closure support for BlockClosure>>asContext, > which was forgetting to push any copied values (in the above case the > argument vat) onto the stack of the new context so that when the process > resumed the initial pushTemp0 that should push the copied value of vat in > fact pushed (at least in the Cog VM) 4 bytes from the middle of the method, > and hence bang! > > The fixes are in Kernel-eem.468 and Kernel-eem.469. Its probably best to > load Kernel-eem.468 and then Kernel-eem.469 rather than just Kernel-eem.469 > because the system will crash if the fixes come i in the wrong order. > Kernel-eem.468 Thanks for the fix. I added a new update map to the trunk which makes sure that Kernel-eem.468 is loaded before Kernel-eem.469. Levente > also fixes restart in blocks in the debugger (its the same issue; forgetting > to initialize the context with any arguments and copied values; local temps > get initialized by explicit pushNil bytecodes). > > thanks for the test case Rob! > > best > Eliot > > P.S. Here are the methods: > > >> Many thanks, >> Rob >> >> >

July 2, 2010

[Pharo-project] [update 1.1] #11408

by Marcus Denker

11408 ----- Issue 2598: Trait composition with exclusion lost when loading package from MC

July 2, 2010

Re: [Pharo-project] ConfigurationOfOSProcess updated

by StÃ©phane Ducasse

Thanks david We should clean the Tests* package in pharo. On Jul 2, 2010, at 4:32 AM, David T. Lewis wrote: > I have made a few updates to OSProcess and CommandShell that I hope > will be useful for Pharo: > > On SqueakSource, I repackaged both OSProcess and CommandShell into > finer-grained package naming. Tests-OSProcess and Tests-CommandShell > become OSProcess-Tests and CommandShell-Tests to avoid package name > conflicts with Pharo and Squeak. The rest of the former OSProcess > and CommandShell are split out into sub-packages to support this, > and also to make it possible avoid loading portions of the package > that are not required (e.g. in Pharo, do not load MVC portions of > CommandShell). > > I updated ConfigurationOfOSProcess in SqS/MetacelloRespository to > load OSProcess from the new package structure. This will also load > a number of updates that make things work properly on Pharo. On > a Unix/Linux platform, all tests should be green (I am not sure > of the status on OS X). > > I have not yet tried to do a ConfigurationOfCommandShell, but if > you use OSProcess and want to also use PipeableOSProcess from > the CommandShell package (but are not interested in the rest of > CommandShell), you can load ConfigurationOfOSProcess, then use > a Monticello browser to load just package CommandShell-Piping > from the CommandShell project on SqueakSource. > > This is my first attempt to do anything with Metacello, so any > fixes or corrections will be appreciated. Miguel Cob originally > created the ConfigurationOfOSProcess, so thanks to Miguel for > doing this. > > Dave > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 2, 2010

[Pharo-project] How-to load O2 on 1.1?

by Geert Claes

How do I load O2 in the 1.1 RC3? -- View this message in context: http://forum.world.st/How-to-load-O2-on-1-1-tp2276308p2276308.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 2, 2010

[Pharo-project] [update 1.2] #12027

by Marcus Denker

12027 ----- Issue 2612: DateAndTime current asUnixTime walkback in 1.1 rc3 Issue 2588: Dictionary>>do: Issue 2598: Trait composition with exclusion lost when loading package from MC

July 2, 2010

Re: [Pharo-project] bug in RC3: Trait composition lost when loading a MC package

by Alexandre Bergel

I guess there is no more issue pending with this slice. I think it is just a matter of time for the integrator. Thanks for your feedback. I guess that fact you tried it should accelerate its integration Cheers, Alexandre On 2 Jul 2010, at 12:18, Tudor Girba wrote: > Hi Alex, > > Thanks. Indeed with this fix it works well. Would it be possible to integrate this fix in Core, or are there other issues with it? > > Cheers, > Doru > > > On 2 Jul 2010, at 11:36, Alexandre Bergel wrote: > >> Even after having loaded SLICE-Issue-2598-LoadingTraitCompositionFromMonticello-Alexandre_Bergel.1 from the inbox? >> >> Alexandre >> >> >> On 2 Jul 2010, at 11:16, Tudor Girba wrote: >> >>> Hi, >>> >>> This issue is still present in RC3 (both dev and core). >>> >>> To my mind this is a show stopper bug. >>> >>> Cheers, >>> Doru >>> >>> >>> >>> On 29 Jun 2010, at 11:32, Simon Denier wrote: >>> >>>> >>>> >>>> Opened issue 2598 >>>> >>>> >>>> On 29 juin 2010, at 07:36, StÃ©phane Ducasse wrote: >>>> >>>>> thanks simon >>>>> >>>>> Stef >>>>> >>>>> On Jun 28, 2010, at 10:45 PM, Simon Denier wrote: >>>>> >>>>>> >>>>>> When loading a package with class definitions containing a trait composition like ClassX uses: TraitY - {#selector}, the composition is lost in the image. >>>>>> >>>>>> It seems closely related to previous issues 2477 and 2148 >>>>>> But I am not sure if this is the same bug reappearing or a variant. >>>>>> >>>>>> To reproduce: >>>>>> Gofer new squeaksource: 'MooseAlgos'; package: 'Moose-Algos-Graph'; package: 'Moose-Tests-Algos-Graph'; load >>>>>> >>>>>> Run tests in Moose-Tests-Algos-Graph: you should have 3 failures and 4 errors, all due to the missing trait composition in some classes. >>>>>> >>>>>> >>>>>> After loading, you can make a diff changes in monticello, it will highlight the package as dirty and show you the lost trait compositions in two classes: >>>>>> >>>>>> MOGraphNode subclass: #MABfsNode >>>>>> uses: MATEdgeNode - {#previousEdges. #from:edge:} >>>>>> instanceVariableNames: 'nextEdges firstDepth' >>>>>> classVariableNames: '' >>>>>> poolDictionaries: '' >>>>>> category: 'Moose-Algos-Graph' >>>>>> >>>>>> MODisjointSetNode subclass: #MANextNode >>>>>> uses: MATNodeNode - {#from:. #previousNodes} >>>>>> instanceVariableNames: 'nextNodes' >>>>>> classVariableNames: '' >>>>>> poolDictionaries: '' >>>>>> category: 'Moose-Algos-Graph' >>>>>> >>>>>> >>>>>> >>>>>> The problem has been reproduced in 11383 and 11400 RC2. >>>>>> >>>>>> >>>>>> -- >>>>>> Simon >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> -- >>>> Simon >>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> -- >>> www.tudorgirba.com >>> >>> "Problem solving should be focused on describing >>> the problem in a way that makes the solution obvious." >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "Every now and then stop and ask yourself if the war you're fighting is the right one." > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 2, 2010

Re: [Pharo-project] ConfigurationOfOSProcess updated

by Adrian Lienhard

Hi David, Thanks a lot! Please find my report for OS X below. On Jul 2, 2010, at 04:32 , David T. Lewis wrote: > I have made a few updates to OSProcess and CommandShell that I hope > will be useful for Pharo: > > On SqueakSource, I repackaged both OSProcess and CommandShell into > finer-grained package naming. Tests-OSProcess and Tests-CommandShell > become OSProcess-Tests and CommandShell-Tests to avoid package name > conflicts with Pharo and Squeak. The rest of the former OSProcess > and CommandShell are split out into sub-packages to support this, > and also to make it possible avoid loading portions of the package > that are not required (e.g. in Pharo, do not load MVC portions of > CommandShell). > > I updated Processs in SqS/MetacelloRespository to > load OSProcess from the new package structure. This will also load > a number of updates that make things work properly on Pharo. On > a Unix/Linux platform, all tests should be green (I am not sure > of the status on OS X). Image: Pharo-1.1-11406-rc3dev10.07.1 VM: Squeak 4.2.4beta1U Loading OSProcess: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfOSProcess'; load. ((Smalltalk at: #ConfigurationOfOSProcess) project latestVersion) load ThisOSProcess initialize (this seems necessary, is it the right #initialize?) The following tests crash the VM: - UnixProcessUnixFileLockingTest - UnixProcessWin32FileLockingTest - UnixProcessTestCase The failures and errors of the other tests: Failures: AioEventHandlerTestCase>>#testEnableHandleAndDisable AioEventHandlerTestCase>>#testPrimAioModuleVersionString AioEventHandlerTestCase>>#testFileWritableEvent AioEventHandlerTestCase>>#testFileReadableEvent UnixProcessAccessorTestCase>>#testChDir UnixProcessAccessorTestCase>>#testIsWritableForUserInGroup AioEventHandlerTestCase>>#testSuspendAioForSocketReadableEvent UnixProcessAccessorTestCase>>#testIsReadableForUserInGroup AioEventHandlerTestCase>>#testHandleForSocket AioEventHandlerTestCase>>#testHandleForFile AioEventHandlerTestCase>>#testSocketReadableEvent UnixProcessAccessorTestCase>>#testIsExecutableForUserInGroup Errors: AioEventHandlerTestCase>>#testPrimAioModuleName I wonder whether the Mac VM includes the latest version of the OSProcess plugin? Cheers, Adrian > I have not yet tried to do a ConfigurationOfCommandShell, but if > you use OSProcess and want to also use PipeableOSProcess from > the CommandShell package (but are not interested in the rest of > CommandShell), you can load ConfigurationOfOSProcess, then use > a Monticello browser to load just package CommandShell-Piping > from the CommandShell project on SqueakSource. > > This is my first attempt to do anything with Metacello, so any > fixes or corrections will be appreciated. Miguel Cob originally > created the ConfigurationOfOSProcess, so thanks to Miguel for > doing this. > > Dave > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 2, 2010

Re: [Pharo-project] bug in RC3: Trait composition lost when loading a MC package

by Tudor Girba

Hi Alex, Thanks. Indeed with this fix it works well. Would it be possible to integrate this fix in Core, or are there other issues with it? Cheers, Doru On 2 Jul 2010, at 11:36, Alexandre Bergel wrote: > Even after having loaded SLICE-Issue-2598- > LoadingTraitCompositionFromMonticello-Alexandre_Bergel.1 from the > inbox? > > Alexandre > > > On 2 Jul 2010, at 11:16, Tudor Girba wrote: > >> Hi, >> >> This issue is still present in RC3 (both dev and core). >> >> To my mind this is a show stopper bug. >> >> Cheers, >> Doru >> >> >> >> On 29 Jun 2010, at 11:32, Simon Denier wrote: >> >>> >>> >>> Opened issue 2598 >>> >>> >>> On 29 juin 2010, at 07:36, StÃ©phane Ducasse wrote: >>> >>>> thanks simon >>>> >>>> Stef >>>> >>>> On Jun 28, 2010, at 10:45 PM, Simon Denier wrote: >>>> >>>>> >>>>> When loading a package with class definitions containing a trait >>>>> composition like ClassX uses: TraitY - {#selector}, the >>>>> composition is lost in the image. >>>>> >>>>> It seems closely related to previous issues 2477 and 2148 >>>>> But I am not sure if this is the same bug reappearing or a >>>>> variant. >>>>> >>>>> To reproduce: >>>>> Gofer new squeaksource: 'MooseAlgos'; package: 'Moose-Algos- >>>>> Graph'; package: 'Moose-Tests-Algos-Graph'; load >>>>> >>>>> Run tests in Moose-Tests-Algos-Graph: you should have 3 failures >>>>> and 4 errors, all due to the missing trait composition in some >>>>> classes. >>>>> >>>>> >>>>> After loading, you can make a diff changes in monticello, it >>>>> will highlight the package as dirty and show you the lost trait >>>>> compositions in two classes: >>>>> >>>>> MOGraphNode subclass: #MABfsNode >>>>> uses: MATEdgeNode - {#previousEdges. #from:edge:} >>>>> instanceVariableNames: 'nextEdges firstDepth' >>>>> classVariableNames: '' >>>>> poolDictionaries: '' >>>>> category: 'Moose-Algos-Graph' >>>>> >>>>> MODisjointSetNode subclass: #MANextNode >>>>> uses: MATNodeNode - {#from:. #previousNodes} >>>>> instanceVariableNames: 'nextNodes' >>>>> classVariableNames: '' >>>>> poolDictionaries: '' >>>>> category: 'Moose-Algos-Graph' >>>>> >>>>> >>>>> >>>>> The problem has been reproduced in 11383 and 11400 RC2. >>>>> >>>>> >>>>> -- >>>>> Simon >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>> project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> -- >>> Simon >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> www.tudorgirba.com >> >> "Problem solving should be focused on describing >> the problem in a way that makes the solution obvious." >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Every now and then stop and ask yourself if the war you're fighting is the right one."

July 2, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.1-11406-rc3dev10.07.1

by Adrian Lienhard

Thanks, Mariano! Here is the result of running all the tests: 15 failures, 76 errors Failures: NSFileStreamTest>>#testFlush21 ObjectAsOneTimeMethodWrapperTest>>#testInstallOnClassCategory NSFileStreamTest>>#testPeek01 ReleaseTest>>#testUndeclared SHParserST80Test>>#testNumbers NSMultiByteBinaryOrTextStreamTest>>#testFileIn NSFileStreamTest>>#testReadWriteText NSMultiByteBinaryOrTextStreamTest>>#testFileOut WeakRegistryTest>>#testFinalization NSFileStreamTest>>#testNext01 NSFileStreamTest>>#testReadWriteBinary NSFileStreamTest>>#testDo01 NSFileStreamTest>>#testSkip01 ObjectFinalizerTests>>#testFinalizationOfMultipleResources MCInitializationTest>>#testWorkingCopy Errors: NSRWBinaryOrTextStreamTest>>#testFileIn NSRWBinaryOrTextStreamTest>>#testFileInExpresion NSRWBinaryOrTextStreamTest>>#testFileOut NSRWBinaryOrTextStreamTest>>#testFileOutFileIn NSCompressedSourceStreamTest>>#testAtEnd01 NSCompressedSourceStreamTest>>#testAtEnd11 NSCompressedSourceStreamTest>>#testAtStart11 NSCompressedSourceStreamTest>>#testBack11 NSCompressedSourceStreamTest>>#testBack61 NSCompressedSourceStreamTest>>#testDo01 NSCompressedSourceStreamTest>>#testFlush21 NSCompressedSourceStreamTest>>#testGlobal NSCompressedSourceStreamTest>>#testIsEmpty11 NSCompressedSourceStreamTest>>#testNext01 NSCompressedSourceStreamTest>>#testNextInto01 NSCompressedSourceStreamTest>>#testNextMatchFor01 NSCompressedSourceStreamTest>>#testNextPutAllAppending21 NSCompressedSourceStreamTest>>#testNextPutAllAppendingASet21 NSCompressedSourceStreamTest>>#testNextPutAllReplacing21 NSCompressedSourceStreamTest>>#testNextPutAllReplacingASet21 NSCompressedSourceStreamTest>>#testNextPutAppending21 NSCompressedSourceStreamTest>>#testNextPutReplacing21 NSCompressedSourceStreamTest>>#testNexts01 NSCompressedSourceStreamTest>>#testPeek01 NSCompressedSourceStreamTest>>#testPeekFor01 NSCompressedSourceStreamTest>>#testPosition11 NSCompressedSourceStreamTest>>#testReset11 NSCompressedSourceStreamTest>>#testSetPosition11 NSCompressedSourceStreamTest>>#testSetToEnd11 NSCompressedSourceStreamTest>>#testSize11 NSCompressedSourceStreamTest>>#testSkip01 NSCompressedSourceStreamTest>>#testSkip61 NSCompressedSourceStreamTest>>#testUpToElementSatisfying01 NSCompressedSourceStreamTest>>#testWriteBack71 WeakSetInspectorTest>>#testSymbolTableM6812 NSMCPseudoFileStreamTest>>#testFileIn NSMCPseudoFileStreamTest>>#testFileInExpresion NSMCPseudoFileStreamTest>>#testFileOut NSMCPseudoFileStreamTest>>#testFileOutFileIn NSSmartRefStreamTest>>#testGlobal NSMailAddressTokenizerTest>>#testNextElements NSMultiByteBinaryOrTextStreamTest>>#testFileInExpresion NSPipeTest>>#testScenario1 NSFileStreamTest>>#testAtEnd01 NSFileStreamTest>>#testAtEnd11 NSFileStreamTest>>#testAtStart11 NSFileStreamTest>>#testBack11 NSFileStreamTest>>#testBack61 NSFileStreamTest>>#testIsBinaryOnBinaryStream NSFileStreamTest>>#testIsBinaryOnNonBinaryStream NSFileStreamTest>>#testIsClosedTest NSFileStreamTest>>#testIsEmpty11 NSFileStreamTest>>#testNextInto01 NSFileStreamTest>>#testNextMatchFor01 NSFileStreamTest>>#testNextPutAllAppending21 NSFileStreamTest>>#testNextPutAllAppendingASet21 NSFileStreamTest>>#testNextPutAllReplacing21 NSFileStreamTest>>#testNextPutAllReplacingASet21 NSFileStreamTest>>#testNextPutAppending21 NSFileStreamTest>>#testNextPutReplacing21 NSFileStreamTest>>#testNexts01 NSFileStreamTest>>#testPeekFor01 NSFileStreamTest>>#testPosition11 NSFileStreamTest>>#testReadWriteBinary2 NSFileStreamTest>>#testReadWriteText2 NSFileStreamTest>>#testReset11 NSFileStreamTest>>#testSetPosition11 NSFileStreamTest>>#testSetToEnd11 NSFileStreamTest>>#testSimpleWriteData NSFileStreamTest>>#testSize11 NSFileStreamTest>>#testSkip61 NSFileStreamTest>>#testTruncateBinary NSFileStreamTest>>#testTruncateText NSFileStreamTest>>#testUpToElementSatisfying01 NSFileStreamTest>>#testWriteBack71 NSCollectionAdditionsTest>>#testMakeRoomForSmallCollections Nile is broken because it sends #isFinalizationSupported, which does not exist anymore. Adrian On Jul 2, 2010, at 00:29 , Mariano Martinez Peck wrote: > Hi folks. I am glad to announce the Pharo 1.1 RC3. It has not too much > changes in compare to RC2. The main change is the menu structure. I also > updated to newest version of external packages. > > Here is the image: > > https://gforge.inria.fr/frs/download.php/27241/Pharo-1.1-11406-rc3dev10.07.… > > We would really appreaciate feedback and help to fix the failing tests. > > Cheers > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 2, 2010

Re: [Pharo-project] CLFramework and Pharo

by StÃ©phane Ducasse

Thanks! On Jul 1, 2010, at 11:59 PM, nullPointer wrote: > > I did created a new project in Squeaksource called UIBuilder, where the > people could access and modify without problems. Then CLFramework now is > only for me, as backup copy and probes. > > Regards. > -- > View this message in context: http://forum.world.st/CLFramework-and-Pharo-tp2273256p2275771.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 2, 2010