Issue 4617 in pharo: More error tolerant startup

Comment #20 on issue 4617 by [hidden email]: More error tolerant  
startup
http://code.google.com/p/pharo/issues/detail?id=4617

Issue 5040 has been merged into this issue.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #21 on issue 4617 by [hidden email]: More error tolerant  
startup
http://code.google.com/p/pharo/issues/detail?id=4617

Thank you, Max and Camillo


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #22 on issue 4617 by [hidden email]: More error tolerant  
startup
http://code.google.com/p/pharo/issues/detail?id=4617

As soon as you have something ready, please tell... we should do a new  
one-click image for 1.3 soon.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #23 on issue 4617 by [hidden email]: More error tolerant  
startup
http://code.google.com/p/pharo/issues/detail?id=4617

We (Max and I) are still testing and improving it, but it will be ready  
soon.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: FixReviewNeeded

Comment #24 on issue 4617 by [hidden email]: More error tolerant  
startup
http://code.google.com/p/pharo/issues/detail?id=4617

So, here is our fix... It is not a backport anymore, but it works fine. The  
behaviour is the following:

StartupUIManager (during startup):
- UI not interactive
- image is not quit automatically
- on error, the UI becomes interactive (and stays interactive) and opens a  
debugger
- same on user interrupt

NonInteractiveUIManager (not used except you use it manually):
- UI not interactive
- image quits on error
- on user interrupt, the UI becomes interactive (and stays interactive) and  
opens a debugger

(We enhanced the fix for Netstyle to also send error mails, because we need  
to be informed when a productive image can not start properly. This  
anhancement is not included here because it is Netstyle specific)

Have fun with the fix and thank you for integrating it!

Attachments:
        4617startupfix.cs  4.1 KB


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #25 on issue 4617 by [hidden email]: More error tolerant  
startup
http://code.google.com/p/pharo/issues/detail?id=4617

Thanks!



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #26 on issue 4617 by [hidden email]: More error tolerant  
startup
http://code.google.com/p/pharo/issues/detail?id=4617

I wonder if this will break our build server, though.

The setup now requires that the image quits itself when there is a problem.  
Else it will just hang and the job will never terminate.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #27 on issue 4617 by [hidden email]: More error tolerant  
startup
http://code.google.com/p/pharo/issues/detail?id=4617

this fix is only for 1.3 right? most builds run on 1.4 anyway, no?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #28 on issue 4617 by [hidden email]: More error tolerant  
startup
http://code.google.com/p/pharo/issues/detail?id=4617

There are some 1.3 depending projects left... but we would retire 1.3 from  
the build server soon after
starting the next elopement cycle.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #29 on issue 4617 by [hidden email]: More error tolerant  
startup
http://code.google.com/p/pharo/issues/detail?id=4617

We use the NonInteractiveUIManager on our build server, this one quits on  
error.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Owner: [hidden email]
        Cc: [hidden email]

Comment #30 on issue 4617 by [hidden email]: More error tolerant  
startup
http://code.google.com/p/pharo/issues/detail?id=4617

Could one of you please summarize this report and tell us what needs to be  
done?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #31 on issue 4617 by [hidden email]: More error tolerant  
startup
http://code.google.com/p/pharo/issues/detail?id=4617

Summary

Description: The problem was that the image quit when an Exception occurred  
during startup.

Fix for 1.4:
SLICE-Issue-4617-More-error-tolerant-startup-Camillobruni.1
Status: integrated

Fix for 1.3:
4617startupfix.cs in comment 24, explained there
Status: needs to be integrated


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Integrated

Comment #32 on issue 4617 by [hidden email]: More error tolerant  
startup
http://code.google.com/p/pharo/issues/detail?id=4617

in 13 329


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker