That was integrated 4 versions ago :).<br><br>Now, about the extra state for unexpected monkey failures, I think we can tag issues with whatever tag we want, even if they are not configured in the engine.� But the creator must make himself responsible of doing that...<br>
Something like &quot;ManualReviewNeeded&quot; probably...<br><br>Guille<br><br><div class="gmail_quote">On Thu, Jul 5, 2012 at 8:45 AM, Torsten Bergmann <span dir="ltr">&lt;<a href="mailto:astares@gmx.de" target="_blank">astares@gmx.de</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Looks like our monkey is not able to read important notes before filing in changeset ;)<br>
<br>
see <a href="http://code.google.com/p/pharo/issues/detail?id=6139" target="_blank">http://code.google.com/p/pharo/issues/detail?id=6139</a><br>
<br>
<br>
IMPORTANT NOTE:<br>
===============<br>
The fix is using an utility method from the fix for isse #6138<br>
Therefore the attached fix requires &quot;ProposedFix.cs&quot; from <a href="http://code.google.com/p/pharo/issues/detail?id=6138" target="_blank">http://code.google.com/p/pharo/issues/detail?id=6138</a><br>
<br>
Please check manually.<br>
<br>
Can we have an issue state: THE_MONKEY_RUNS_OUT_OF_BANANA<br>
so they get integrated<br>
<br>
I tested on different machines - IMHO the fixes for<br>
#6138 and #6139 are safe to integrate.<br>
<br>
Thx<br>
<span class="HOEnZb"><font color="#888888">T.<br>
<br>
</font></span></blockquote></div><br>