- Pharo-dev - lists.pharo.org

Re: [Pharo-project] OSProcess error in 1.3

by David T. Lewis

Sean, Can you please try two things, in this order, and let me know which one causes the problem to go away? 1) Save your image, exit, and restart. Then try (OSProcess command: 'ls') inspect and see if it results in a process proxy with run state "complete". 2) Restart the child watcher OSProcess accessor restartChildWatcherProcess. (OSProcess command: 'ls') inspect and see if it results in a process proxy with run state "complete". Thanks, Dave On Tue, May 01, 2012 at 10:22:44PM -0700, Sean P. DeNigris wrote: > With the latest OSProcess package from SqS, when I save the image, I get: > > 2 May 2012 1:20:30 am > > VM: Mac OS - intel - 1073 - Croquet Closure Cog VM [CoInterpreter > VMMaker-oscog-EstebanLorenzano.155] 21.0 > Image: Pharo1.3 [Latest update: #13320] > > UndefinedObject(Object)>>doesNotUnderstand: #wait > Receiver: nil > Arguments and temporary variables: > aMessage: wait > exception: MessageNotUnderstood: receiver of "wait" is nil > resumeValue: nil > Receiver's instance variables: > nil > > [[event wait. > processSynchronizationDelay wait. > self changed: #childProcessStatus] repeat. > nil] in UnixOSProcessAccessor>>grimReaperProcess > Receiver: a UnixOSProcessAccessor on pid 22740 > Arguments and temporary variables: > event: nil > processSynchronizationDelay: a Delay(20 msecs) > Receiver's instance variables: > dependents: a DependentsArray(a UnixProcess with pid 22740) > sessionIdentifier: #[104 195 160 79] > canObtainSessionIdentifierFromPlugin: true > hasTestEof: nil > grimReaper: a Process in > MorphicUIManager>>openDebuggerOn:context:label:content...etc... > sigChldSemaphore: nil > > Weird... > > > -- > View this message in context: http://forum.world.st/OSProcess-error-in-1-3-tp4602389.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 2, 2012

[Pharo-project] [update 2.0] #20038

by Marcus Denker

20038 ----- Issue 5775: add test to trait removal http://code.google.com/p/pharo/issues/detail?id=5775 Issue 5738: do allow the same ivar in the hierarchy http://code.google.com/p/pharo/issues/detail?id=5738 Issue 5742: BallonMorph shows flyover help using an extra line http://code.google.com/p/pharo/issues/detail?id=5742 Issue 5667: Renaming a file just deletes it due to missing #fileNameFromFormattedItem: http://code.google.com/p/pharo/issues/detail?id=5667 Issue 5773: Have access to the original event in PLuggableButtonMorph http://code.google.com/p/pharo/issues/detail?id=5773 -- Marcus Denker -- http://marcusdenker.de

May 2, 2012

[Pharo-project] Deprecate FileDirectory

by Damien Cassou

Do we have to deprecate all methods of the FileDirectory API? http://code.google.com/p/pharo/issues/detail?id=5772 -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

May 2, 2012

Re: [Pharo-project] Pharo 2.0: Just need a recompileAll or a real problem in background?

by Marcus Denker

On May 2, 2012, at 10:27 AM, Mariano Martinez Peck wrote: > > Ok, I wrote an ugly test and I noticed that the ONLY method with this problem in the image is > > > | behaviorAssociations broken | > behaviorAssociations := Smalltalk globals associations select: [:each | each value isBehavior or: [each value isTrait]]. > broken := OrderedCollection new. > (CompiledMethod allInstances select: [:each | each isInstalled]) > do: [:aMethod | aMethod literals > do: [:aLiteral | aLiteral isVariableBinding > ifTrue: [ ((behaviorAssociations includes: aLiteral) > and: [(behaviorAssociations identityIncludes: aLiteral) not]) > ifTrue: [broken add: (aMethod -> aLiteral)] > ] > ] > ]. > broken inspect > > And I have 6 methods from the classes SmalltalkImage and ScriptLoader and all the 6 literals are pointing to ScriptLoader. So something weird happened with this class. > Any idea? > Maybe monticello does not recompile sometimes a method when it should? > For the moment I will update the test and do a Compiler recompileAll. > ok. -- Marcus Denker -- http://marcusdenker.de

May 2, 2012

Re: [Pharo-project] Pharo 2.0: Just need a recompileAll or a real problem in background?

by Mariano Martinez Peck

On Tue, May 1, 2012 at 10:17 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Tue, May 1, 2012 at 10:05 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> On 1 May 2012 21:45, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> > >> > >> > On Tue, May 1, 2012 at 9:22 PM, Francisco Garau < >> francisco.garau(a)gmail.com> >> > wrote: >> >> >> >> Your code snippet is comparing the associations. The below one >> evaluates >> >> to true: >> >> >> >> (Smalltalk globals associationAt: #ScriptLoader) value >> >> == >> >> ((SmalltalkImage >> #shrinkToCore) literalAt: 4) value >> >> >> > >> > Yes, but the literals of CompiledMethod that refer to classes should >> have >> > the SAME association as Smalltalk globals. In fact, that's the reason >> why we >> > have: >> > >> indeed. >> The question is what leads to creation of multiple associations >> pointing to same global? >> > > > Exactly. I can easily fix it with a Compiler recompileAll. But the main > question is if we have a bug or something that could let us in that state. > > Ok, I wrote an ugly test and I noticed that the ONLY method with this problem in the image is | behaviorAssociations broken | behaviorAssociations := Smalltalk globals associations select: [:each | each value isBehavior or: [each value isTrait]]. broken := OrderedCollection new. (CompiledMethod allInstances select: [:each | each isInstalled]) do: [:aMethod | aMethod literals do: [:aLiteral | aLiteral isVariableBinding ifTrue: [ ((behaviorAssociations includes: aLiteral) and: [(behaviorAssociations identityIncludes: aLiteral) not]) ifTrue: [broken add: (aMethod -> aLiteral)] ] ] ]. broken inspect And I have 6 methods from the classes SmalltalkImage and ScriptLoader and all the 6 literals are pointing to ScriptLoader. So something weird happened with this class. Any idea? For the moment I will update the test and do a Compiler recompileAll. > >> > Association >> #literalEqual: otherLiteral >> > "Answer true if the receiver and otherLiteral represent the same >> > literal. >> > Variable bindings are literally equals only if identical. >> > This is how variable sharing works, by preserving identity and >> changing >> > only the value." >> > ^self == otherLiteral >> > >> > instead of the Object implementation. >> > >> > >> >> >> >> On 1 May 2012 17:52, Mariano Martinez Peck <marianopeck(a)gmail.com> >> wrote: >> >>> >> >>> (Smalltalk globals associationAt: #ScriptLoader) == ((SmalltalkImage >> >> >> >>> #shrinkToCore) literalAt: 4) >> >>> gives false when it should be true. If I do a Compiler recompileAll >> it >> >>> gets fixed. So, my question is, is that normal? how could that happen? >> >>> is there any real problem behind? >> >>> >> >>> anyway, can we do a recompileAll for the moment? >> >>> >> >>> thanks! >> >>> >> >>> -- >> >>> Mariano >> >>> http://marianopeck.wordpress.com >> >>> >> >> >> > >> > >> > >> > -- >> > Mariano >> > http://marianopeck.wordpress.com >> > >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

May 2, 2012

[Pharo-project] One month working for Pharo Consortium

by Esteban Lorenzano

Hi, So, I'm working since one month for Pharo Consortium, and I want to talk a bit about how is life here, in RMOD headquarters... Of course, is obvious to say that, so far, is been a great experience, and a lot of fun... the team here is great, very capable, focused and always willing to help (and to hack something, he). In one month, I already face a lot of different issues: 1) I helped on release 1.4: - lots of bugfixed and reviews integrated. - finishing and integrate new ecompletion/ocompletion - integration of FileSystem - fixing VM important issues in windows (FFI plugin and command line options) 2) I worked on the new release process, both in defining them and in doing steps to make it happen (still far from there) 3) Tried to took off some pressure from Marcus and Stef shoulders... I failed miserably in this issue, because they (both of them) are more or less workaholics and really enjoy what they do, so, take some of their responsibilities is not to easy :) 4) I also made some small steps on the upcoming pharo consortium web site. Well, more or less, that's all. Could I make more? Probably, but well, I was just adapting to a new country, a new language and a new work environment. In my not-so-good list, my responsibilities includes the bootstrap of the pharo consortium, and I think that's the biggest missing in the month work. I will try to fix that next month. In my TODO list, now there are: -bootstrap consortium site -make a first iteration on new release process -make some "experiments" on validating configurations -tackle issues and integrate them :) best, Esteban

May 2, 2012

Re: [Pharo-project] #nsWriteStream

by Damien Cassou

On Thu, Apr 26, 2012 at 10:31 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > From http://code.google.com/p/pharo/wiki/CodeSnippets : > Â Â MCWorkingCopy allManagers flatCollect: [:e | e repositoryGroup > repositories]. > -> error: Array DNU #nsWriteStream looks like the code has changed to use #asSet. #nsWriteStream creates a Nile stream and it doesn't work if Nile is not loaded. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

May 2, 2012

Re: [Pharo-project] browsing versions of a method

by Mariano Martinez Peck

On Wed, May 2, 2012 at 1:00 AM, Francisco Garau <francisco.garau(a)gmail.com>wrote: > Hi - I've noticed we have a new way of showing diffs between two versions > of a method. Very nice! yes, I did it with Ben in the sprint ;) > > But it would be more useful if the user had the choice of which two > versions to compare. > > You can right click a version and you have the option "Compare to current" and "compare to version..." The problem is that they have not been fixed with the nice diff so it opens an ugly popup diff. > For example, if I maje 10 changes to method Date>>today I would like to > compare my first and last versions... > > Cheers, > Francisco > -- Mariano http://marianopeck.wordpress.com

May 2, 2012

Re: [Pharo-project] [Vm-dev] Re: [squeak-dev] Re: problem with tempNamed: in Pharo 2.0

by Mariano Martinez Peck

> > >> Actually, we do have: >> >> namedTempAt: index >> "Answer the value of the temp at index in the receiver's sequence of >> tempNames." >> ^self debuggerMap namedTempAt: index in: self >> >> and >> >> namedTempAt: index put: aValue >> "Set the value of the temp at index in the receiver's sequence of >> tempNames. >> (Note that if the value is a copied value it is also set out along >> the lexical chain, >> but alas not in along the lexical chain.)." >> ^self debuggerMap namedTempAt: index put: aValue in: self >> >> so, if I understand correctly all we need to do is to fix tempNamed: and >> tempNamedPut: so that the delegate to namedTempAt: and namedTempPut: rather >> than to tempAt: and tempAtPut: ? >> > > Yes. > > Now I was thinking, what happens with the rest of the senders of tempAt: and tempAtPut: ? do I need to do something with them? Thanks -- Mariano http://marianopeck.wordpress.com

May 2, 2012

[Pharo-project] [update 2.0] #20037

by Marcus Denker

20037 ----- Issue 5763: ProtoObject>>#~~ cleanup http://code.google.com/p/pharo/issues/detail?id=5763 Issue 5743: Cannot load editions of class side methods http://code.google.com/p/pharo/issues/detail?id=5743 Issue 2063: NumberTest http://code.google.com/p/pharo/issues/detail?id=2063 -- Marcus Denker -- http://marcusdenker.de

May 2, 2012