MNU: RubPluggableTextMorph>>appendEntry

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

MNU: RubPluggableTextMorph>>appendEntry

abergel
Hi!

A new Pharo user bumps into a nasty bug. No idea why it appears time to time.
The method ThreadSafeTranscript>>stepGlobal does a "self changed: #appendEntry.” This apparently update by RubPluggableTextMorph by calling "RubPluggableTextMorph >>update:  #appendEntry”. All this ultimately sends #appendEntry to RubPluggableTextMorph, which is not understood.

What is the solution for this?

https://pharo.fogbugz.com/f/cases/16749/MNU-RubPluggableTextMorph-appendEntry

Alexandre


--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




Reply | Threaded
Open this post in threaded view
|

Re: MNU: RubPluggableTextMorph>>appendEntry

Pharo Smalltalk Users mailing list
Hello,
I’ve just tested.
It seems to  works well with the last version of Pharo 5
Cheers
Alain

> On 08 Oct 2015, at 22:40, Alexandre Bergel <[hidden email]> wrote:
>
> Hi!
>
> A new Pharo user bumps into a nasty bug. No idea why it appears time to time.
> The method ThreadSafeTranscript>>stepGlobal does a "self changed: #appendEntry.” This apparently update by RubPluggableTextMorph by calling "RubPluggableTextMorph >>update:  #appendEntry”. All this ultimately sends #appendEntry to RubPluggableTextMorph, which is not understood.
>
> What is the solution for this?
>
> https://pharo.fogbugz.com/f/cases/16749/MNU-RubPluggableTextMorph-appendEntry
>
> Alexandre
>
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: MNU: RubPluggableTextMorph>>appendEntry

Andrei Chis
This error happens now in Moose every time something is printed to the transcript.
Seems that rubric has diverged a bit in Pharo


On Fri, Oct 9, 2015 at 8:16 AM, Alain Plantec via Pharo-users <[hidden email]> wrote:


---------- Forwarded message ----------
From: Alain Plantec <[hidden email]>
To: Any question about pharo is welcome <[hidden email]>
Cc: 
Date: Fri, 9 Oct 2015 08:16:00 +0200
Subject: Re: [Pharo-users] MNU: RubPluggableTextMorph>>appendEntry
Hello,
I’ve just tested.
It seems to  works well with the last version of Pharo 5
Cheers
Alain

> On 08 Oct 2015, at 22:40, Alexandre Bergel <[hidden email]> wrote:
>
> Hi!
>
> A new Pharo user bumps into a nasty bug. No idea why it appears time to time.
> The method ThreadSafeTranscript>>stepGlobal does a "self changed: #appendEntry.” This apparently update by RubPluggableTextMorph by calling "RubPluggableTextMorph >>update:  #appendEntry”. All this ultimately sends #appendEntry to RubPluggableTextMorph, which is not understood.
>
> What is the solution for this?
>
> https://pharo.fogbugz.com/f/cases/16749/MNU-RubPluggableTextMorph-appendEntry
>
> Alexandre
>
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>




Reply | Threaded
Open this post in threaded view
|

Re: MNU: RubPluggableTextMorph>>appendEntry

Marcus Denker-4

On 09 Oct 2015, at 15:42, Andrei Chis <[hidden email]> wrote:

This error happens now in Moose every time something is printed to the transcript.
Seems that rubric has diverged a bit in Pharo


Du to problems with changes that where crosscutting some changes where done that need to 
be re=synced back to the repository… someone needs to do that. There is even an issue tracker entry
for that.


On Fri, Oct 9, 2015 at 8:16 AM, Alain Plantec via Pharo-users <[hidden email]> wrote:


---------- Forwarded message ----------
From: Alain Plantec <[hidden email]>
To: Any question about pharo is welcome <[hidden email]>
Cc: 
Date: Fri, 9 Oct 2015 08:16:00 +0200
Subject: Re: [Pharo-users] MNU: RubPluggableTextMorph>>appendEntry
Hello,
I’ve just tested.
It seems to  works well with the last version of Pharo 5
Cheers
Alain

> On 08 Oct 2015, at 22:40, Alexandre Bergel <[hidden email]> wrote:
>
> Hi!
>
> A new Pharo user bumps into a nasty bug. No idea why it appears time to time.
> The method ThreadSafeTranscript>>stepGlobal does a "self changed: #appendEntry.” This apparently update by RubPluggableTextMorph by calling "RubPluggableTextMorph >>update:  #appendEntry”. All this ultimately sends #appendEntry to RubPluggableTextMorph, which is not understood.
>
> What is the solution for this?
>
> https://pharo.fogbugz.com/f/cases/16749/MNU-RubPluggableTextMorph-appendEntry
>
> Alexandre
>
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>





Reply | Threaded
Open this post in threaded view
|

Re: MNU: RubPluggableTextMorph>>appendEntry

Tudor Girba-2
I just checked, and it looks like someone has back-copied all versions to the Rubric repo. Thanks :)

I also tested in the latest Moose 6, and there is no error when printing on the Transcript.

Doru

On Fri, Oct 9, 2015 at 4:19 PM, Marcus Denker <[hidden email]> wrote:

On 09 Oct 2015, at 15:42, Andrei Chis <[hidden email]> wrote:

This error happens now in Moose every time something is printed to the transcript.
Seems that rubric has diverged a bit in Pharo


Du to problems with changes that where crosscutting some changes where done that need to 
be re=synced back to the repository… someone needs to do that. There is even an issue tracker entry
for that.


On Fri, Oct 9, 2015 at 8:16 AM, Alain Plantec via Pharo-users <[hidden email]> wrote:


---------- Forwarded message ----------
From: Alain Plantec <[hidden email]>
To: Any question about pharo is welcome <[hidden email]>
Cc: 
Date: Fri, 9 Oct 2015 08:16:00 +0200
Subject: Re: [Pharo-users] MNU: RubPluggableTextMorph>>appendEntry
Hello,
I’ve just tested.
It seems to  works well with the last version of Pharo 5
Cheers
Alain

> On 08 Oct 2015, at 22:40, Alexandre Bergel <[hidden email]> wrote:
>
> Hi!
>
> A new Pharo user bumps into a nasty bug. No idea why it appears time to time.
> The method ThreadSafeTranscript>>stepGlobal does a "self changed: #appendEntry.” This apparently update by RubPluggableTextMorph by calling "RubPluggableTextMorph >>update:  #appendEntry”. All this ultimately sends #appendEntry to RubPluggableTextMorph, which is not understood.
>
> What is the solution for this?
>
> https://pharo.fogbugz.com/f/cases/16749/MNU-RubPluggableTextMorph-appendEntry
>
> Alexandre
>
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>








--

"Every thing has its own flow"