I looked some more. If I remove the check from the below message it seems
to work fine (essentially, re-establishing the code from before).

MCPackageManager class>>classModified: anEvent
anEvent isPropagation ifTrue:  [ ^ self ].
 self
managersForClass: anEvent classAffected
do:[ :mgr | mgr modified: true ].


It seems that the isPropagation was added as an optimization mechanism, but
I cannot understand its meaning. Anyone? Could we figure out the issue that
was related to the commit?

Cheers,
Doru




On Sun, Jan 26, 2014 at 4:06 PM, Esteban Lorenzano <[email protected]>wrote:

> yep, I can confirm.
> Looks like latest update broke something.
>
> Esteban
>
> On 26 Jan 2014, at 15:50, Tudor Girba <[email protected]> wrote:
>
> Hi,
>
> If I execute the following code in 30720:
> Gofer new
> smalltalkhubUser: 'Moose' project: 'MooseAlgos';
>  configuration;
> loadDevelopment.
>
> I get an emergency evaluator with a strange Original error:
> MessageNotUnderstood Trait>>layout.
>
> Can anyone have a look at the first one? It seems to be related to some
> deep code changes because the same code works find in 30714.
>
> And also there seems to be something related to a nsWriteStream: message
> somewhere that breaks the Spec debugger in the same process and this is why
> we get an Emergency evaluator instead of the debugger.
>
> Cheers,
> Doru
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

Reply via email to