- Pharo-dev - lists.pharo.org

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 3 regressions found. FuelTests.FLMethodContextSerializationTest.testDoIt Tests.Release.ReleaseTest.testObsoleteBehaviors Tests.Release.ReleaseTest.testObsoleteClasses

May 3, 2013

[Pharo-project] [update 3.0] #30087

by Marcus Denker

May 3, 2013

Re: [Pharo-project] froze image just

by Henrik Johansen

Sooooâ¦. I made a slice, but how does one save to the new inbox? You need credentials + some sort of access privileges all of a sudden? :S Cheers, Henry

May 3, 2013

Re: [Pharo-project] froze image just

by Henrik Johansen

On May 3, 2013, at 9:44 AM, Henrik Johansen wrote: >> oh.. on second thought, even better.. >> >> processToInterrupt >> "look for best candidate to interrupt: >> first who is not weak-finalization process >> and only then weak-finalization process, if nothing left to interrupt. >> >> filter out the idle process, since killing it is fatal >> " >> | list | >> >> list := OrderedCollection new. >> Processor scanSchedule: [:p | >> "gather everything but idle process, and processes whose >> suspendedContext sender == nil, >> which usually means that process is only scheduled but had no chance to run" >> >> ((p ~~ Processor backgroundProcess) and: [ p suspendedContext sender notNil ]) >> ifTrue: [ list add: p ] ] startingAt: Processor activePriority. >> >> "now answer first process in list, skipping the finalization process" >> list do: [:p | p == WeakArray runningFinalizationProcess ifFalse: [ ^ p ] ]. >> >> "now answer first process , if any ,otherwise answer ui process by default" >> ^ list isEmpty ifTrue: [ UIManager default uiProcess ] ifFalse: [ list first ] >> >> >> so it interrupts >> even if i do >> >> 1 hour wait >> >> in workspace > Something like that yes, or maybe even: > processToInterrupt > "Look for best candidate to interrupt: > - any scheduled non-finalization process of lower priority > - the weak-finalization process, if scheduled > - the UI process > Never interrupt the idle process, since killing it is fatal" > > | fallback | > > fallback := UIManager default uiProcess. > Processor > scanSchedule: [:p | > "suspendedContext sender == nil usually means that process is only scheduled but had no chance to run" > ((p ~~ Processor backgroundProcess) and: [ p suspendedContext sender notNil ifTrue: [ > p ~~ WeakArray runningFinalizationProcess > ifTrue: [^p] > ifFalse: [fallback := p]] ] > startingAt: Processor activePriority. > ^fallback > > Cheers, > Henry (That's just rewritten btw, functionality is the same) Cheers, Henry

May 3, 2013

Re: [Pharo-project] NewListModel and AlainTreeModel

by Benjamin

Of course not, but I just can't name the two tree implementation TreeModel. As I said in my mail, I will push AlainTreeModel as default, and it will be named TreeModel. Same for the list. (that's also why they do not have a class comment) Ben On May 3, 2013, at 8:10 AM, "Torsten Bergmann" <astares(a)gmx.de> wrote: > maybe it is just me ... but will we continue to name classes like this? > > => NewListModel (will it still be new in year 2052) > => AlainTreeModel (followed by StefsNewTranscript, BenObject, IgorNBWinConstants, ...) > > What was the timeline for namespaces? > > Bye > T. > > >

May 3, 2013

Re: [Pharo-project] froze image just

by Henrik Johansen

On May 2, 2013, at 4:46 PM, Igor Stasenko wrote: > On 2 May 2013 16:39, Igor Stasenko <siguctua(a)gmail.com> wrote: >> On 2 May 2013 15:33, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: >>> >>> On May 2, 2013, at 2:50 PM, Igor Stasenko wrote: >>> >>>> On 2 May 2013 09:54, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: >>>>> What? >>>>> I am 99.99% sure it used to interrupt the GUI process if no other viable candidate could be found, why change that? >>>>> At least in my mind, if you hit cmd - dot, either you want to interrupt some process blocking the UI on a higher priority, or you want the UI process itself. >>>>> For everything else, there's the Process Browser. >>>>> >>>> >>>> It was never like that. >>>> It was always looking for a process which is scheduled, but not >>>> interrupt process itself. >>>> usually that meant it interrupts things like finalization process, >>>> so i added logic to avoid interrupting it unless there's nothing else >>>> to interrupt. >>> >>> From 1.4: >>> handleUserInterrupt >>> [|toInterrupt| >>> toInterrupt := Processor preemptedProcess. >>> "Only interrupt processes which are potentially blocking the UI" >>> toInterrupt priority < UIManager default uiProcess priority ifTrue: [toInterrupt := Project uiProcess]. >>> >>> So yes, it was like that. >>> (barring the other flaws you mentioned, about potentially interrupting critical high-priority processes) >>> >> Okay, then we need to change #ifNil clause in following method to just >> interrupt UI process, >> instead of showing useless "not interruptable" message: >> >> handleUserInterrupt >> "This will be called from the event-fetcher process. >> Assume no system-vital processes have a lower priority than this, and >> are thus ok to interrupt" >> UserInterruptHandler cmdDotEnabled ifFalse: [ ^ self ]. >> >> [ >> self processToInterrupt >> ifNotNil: [ :proc | proc debugWithTitle: 'User Interrupt' ] >> ifNil: [ UIManager default inform: 'Process not interruptable' ] >> >> "fork exceptions, we don't want interrupt handler to die" >> ] on: Error fork: [:ex | ex pass]. >> > > oh.. on second thought, even better.. > > processToInterrupt > "look for best candidate to interrupt: > first who is not weak-finalization process > and only then weak-finalization process, if nothing left to interrupt. > > filter out the idle process, since killing it is fatal > " > | list | > > list := OrderedCollection new. > Processor scanSchedule: [:p | > "gather everything but idle process, and processes whose > suspendedContext sender == nil, > which usually means that process is only scheduled but had no chance to run" > > ((p ~~ Processor backgroundProcess) and: [ p suspendedContext sender notNil ]) > ifTrue: [ list add: p ] ] startingAt: Processor activePriority. > > "now answer first process in list, skipping the finalization process" > list do: [:p | p == WeakArray runningFinalizationProcess ifFalse: [ ^ p ] ]. > > "now answer first process , if any ,otherwise answer ui process by default" > ^ list isEmpty ifTrue: [ UIManager default uiProcess ] ifFalse: [ list first ] > > > so it interrupts > even if i do > > 1 hour wait > > in workspace Something like that yes, or maybe even: processToInterrupt "Look for best candidate to interrupt: - any scheduled non-finalization process of lower priority - the weak-finalization process, if scheduled - the UI process Never interrupt the idle process, since killing it is fatal" | fallback | fallback := UIManager default uiProcess. Processor scanSchedule: [:p | "suspendedContext sender == nil usually means that process is only scheduled but had no chance to run" ((p ~~ Processor backgroundProcess) and: [ p suspendedContext sender notNil ifTrue: [ p ~~ WeakArray runningFinalizationProcess ifTrue: [^p] ifFalse: [fallback := p]] ] startingAt: Processor activePriority. ^fallback Cheers, Henry

May 3, 2013

[Pharo-project] [update 3.0] #30086

by Marcus Denker

30086 ----- 10425 DateAndTime refactoring https://pharo.fogbugz.com/f/cases/10425 Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/KernelTests-MarcusDenker.504 http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Kernel-MarcusDenker.1410 http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Fuel-MarcusDenker.764

May 3, 2013

[Pharo-project] [update 3.0] #30085

by Marcus Denker

30085 ----- 10476 fix CompiledMethodTest>>testCopyWithTrailerBytes https://pharo.fogbugz.com/f/cases/10476 10480 deprecated #decompilerClass https://pharo.fogbugz.com/f/cases/10480 Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/KernelTests-MarcusDenker.503 http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Kernel-MarcusDenker.1409 http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Compiler-MarcusDenker.432

May 3, 2013

[Pharo-project] How to Debug :D

by stephane ducasse

Begin forwarded message: > From: Camillo Bruni <camillobruni(a)gmail.com> > Subject: [Lsehub-staff] How to Debug :D > Date: May 2, 2013 6:22:06 PM GMT+02:00 > To: RMoD private list <lsehub-staff(a)lists.gforge.inria.fr> > Reply-To: RMoD private list <lsehub-staff(a)lists.gforge.inria.fr> > > Igor: Camillo can you help me debugging this strange athens rendering bug > Cami: sure > > Igor: where do you think the bug is? The green path jumps if I change the Y coordinate and it shouldn't... > Cami: no clue... > > Igor: Any clue how to get to the bug? > Cami: let's use the ASTInterpreter to interpret two methods with different transformation matrices and see when they diverge. > > Result: > ------- > - after 1h comparing AST Debugger is ready > - we run the two traces, they do NOT diverge => ???? > > Conclusion: > ----------- > Cairo, which was chosen as reference, did not properly draw the path!!! > > So we should publish the code of the ComparingInterpreter a bit and we > can use it for a few more tasks in Pharo ;) > >

May 3, 2013

[Pharo-project] NewListModel and AlainTreeModel

by Torsten Bergmann

maybe it is just me ... but will we continue to name classes like this? => NewListModel (will it still be new in year 2052) => AlainTreeModel (followed by StefsNewTranscript, BenObject, IgorNBWinConstants, ...) What was the timeline for namespaces? Bye T.

May 3, 2013