Hi!
In a new Moose image, we cannot do a "Transcript open”. Apparently, #Transcript is bound to a NonInteractiveTranscript. NonInteractiveTranscript open raises en error.
That is odd.
Cheers, Alexandre
I got the same in the latest Moose today, but thought that it was my local fault.
+1
Cheers, Alex
On Mon, Mar 21, 2016 at 8:16 PM, Alexandre Bergel alexandre.bergel@me.com wrote:
Hi!
In a new Moose image, we cannot do a "Transcript open”. Apparently, #Transcript is bound to a NonInteractiveTranscript. NonInteractiveTranscript open raises en error.
That is odd.
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
Le 21/03/2016 20:16, Alexandre Bergel a écrit :
Hi!
In a new Moose image, we cannot do a "Transcript open”. Apparently, #Transcript is bound to a NonInteractiveTranscript. NonInteractiveTranscript open raises en error.
That is odd.
Cheers, Alexandre
This was introduced by Pharo 5 but should have been corrected since few days… A temporary workaround is to execute "ThreadSakeTranscript install".
On 21/03/2016 21:24, Cyril Ferlicot D. wrote:
This was introduced by Pharo 5 but should have been corrected since few days… A temporary workaround is to execute "ThreadSakeTranscript install".
I saw that the Moose 6 build did not succeed the past few days, so the last green version is the one with the bug in Pharo. As soon as another image will be green for Moose6, the bug will vanish.
Okay. Thanks Cyril for looking into this
Alexandre
I fixed the build.
Doru
On Mar 22, 2016, at 6:24 PM, Alexandre Bergel alexandre.bergel@me.com wrote:
Okay. Thanks Cyril for looking into this
Alexandre
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Mar 22, 2016, at 6:57 AM, Cyril Ferlicot Delbecque cyril.ferlicot@gmail.com wrote:
On 21/03/2016 21:24, Cyril Ferlicot D. wrote:
This was introduced by Pharo 5 but should have been corrected since few days… A temporary workaround is to execute "ThreadSakeTranscript install".
I saw that the Moose 6 build did not succeed the past few days, so the last green version is the one with the bug in Pharo. As soon as another image will be green for Moose6, the bug will vanish.
-- Cyril Ferlicot
165 Avenue Bretagne Lille 59000 France
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
-- www.tudorgirba.com www.feenk.com
"Every thing should have the right to be different."