[Pharo-project] PharoCore 1.3 built stalled
On 2 May 2011 23:26, Igor Stasenko <siguctua@gmail.com> wrote:
On 2 May 2011 23:13, laurent laffont <laurent.laffont@gmail.com> wrote:
Last built started more than 1 day ago and not finished .... Laurent.
This is not good. I killed the jobs. Lets see if it will repeat again.
Okay the problem is that there is a warning and it is handled by MorphicUIManager, instead of NonInteractiveUIManager which just forcing it to always proceed, while morphic one expects user to press proceed or abandon. So, the problem is with an update of progressTitle: 'Loading 13179-Pha-PlentyOfCleans...' But i don't undestand why it not switched to NonInteractiveUIManager at image startup. Aha.. i guess i know why. Is its not because command line stuff that are triggered at image startup, which tries to evaluate some code before full startup procedure completes? A command line , i think should be changed to start loading external code only after everything else is started (including UI manager). Otherwise we will have problems like that.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
it is my fault but I have no idea how to solve it. A package was loading over an already existing one and you get a pop up. Stef On May 2, 2011, at 11:39 PM, Igor Stasenko wrote:
On 2 May 2011 23:26, Igor Stasenko <siguctua@gmail.com> wrote:
On 2 May 2011 23:13, laurent laffont <laurent.laffont@gmail.com> wrote:
Last built started more than 1 day ago and not finished .... Laurent.
This is not good. I killed the jobs. Lets see if it will repeat again.
Okay the problem is that there is a warning and it is handled by MorphicUIManager, instead of NonInteractiveUIManager which just forcing it to always proceed, while morphic one expects user to press proceed or abandon.
So, the problem is with an update of progressTitle: 'Loading 13179-Pha-PlentyOfCleans...'
But i don't undestand why it not switched to NonInteractiveUIManager at image startup. Aha.. i guess i know why. Is its not because command line stuff that are triggered at image startup, which tries to evaluate some code before full startup procedure completes?
A command line , i think should be changed to start loading external code only after everything else is started (including UI manager). Otherwise we will have problems like that.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
On 3 May 2011 00:49, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
it is my fault but I have no idea how to solve it. A package was loading over an already existing one and you get a pop up.
i have a fix for it. See #4075 it makes sure that no matter what current UI manager you using (running image headless or not) a system startup (all classes startup) is _always_ performed using non-interactive UI manager. So, since CommandLine file-in scripts during startup, this will make sure that it will run non-interactively.
Stef
On May 2, 2011, at 11:39 PM, Igor Stasenko wrote:
On 2 May 2011 23:26, Igor Stasenko <siguctua@gmail.com> wrote:
On 2 May 2011 23:13, laurent laffont <laurent.laffont@gmail.com> wrote:
Last built started more than 1 day ago and not finished .... Laurent.
This is not good. I killed the jobs. Lets see if it will repeat again.
Okay the problem is that there is a warning and it is handled by MorphicUIManager, instead of NonInteractiveUIManager which just forcing it to always proceed, while morphic one expects user to press proceed or abandon.
So, the problem is with an update of         progressTitle:  'Loading 13179-Pha-PlentyOfCleans...'
But i don't undestand why it not switched to NonInteractiveUIManager at image startup. Aha.. i guess i know why. Is its not because command line stuff that are triggered at image startup, which tries to evaluate some code before full startup procedure completes?
A command line , i think should be changed to start loading external code only after everything else is started (including UI manager). Otherwise we will have problems like that.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
excellent good night igor (or good day sleeping) On May 3, 2011, at 3:52 AM, Igor Stasenko wrote:
On 3 May 2011 00:49, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
it is my fault but I have no idea how to solve it. A package was loading over an already existing one and you get a pop up.
i have a fix for it. See #4075
it makes sure that no matter what current UI manager you using (running image headless or not) a system startup (all classes startup) is _always_ performed using non-interactive UI manager.
So, since CommandLine file-in scripts during startup, this will make sure that it will run non-interactively.
Stef
On May 2, 2011, at 11:39 PM, Igor Stasenko wrote:
On 2 May 2011 23:26, Igor Stasenko <siguctua@gmail.com> wrote:
On 2 May 2011 23:13, laurent laffont <laurent.laffont@gmail.com> wrote:
Last built started more than 1 day ago and not finished .... Laurent.
This is not good. I killed the jobs. Lets see if it will repeat again.
Okay the problem is that there is a warning and it is handled by MorphicUIManager, instead of NonInteractiveUIManager which just forcing it to always proceed, while morphic one expects user to press proceed or abandon.
So, the problem is with an update of progressTitle: 'Loading 13179-Pha-PlentyOfCleans...'
But i don't undestand why it not switched to NonInteractiveUIManager at image startup. Aha.. i guess i know why. Is its not because command line stuff that are triggered at image startup, which tries to evaluate some code before full startup procedure completes?
A command line , i think should be changed to start loading external code only after everything else is started (including UI manager). Otherwise we will have problems like that.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
Of course, now, we get no warning of being unable to write to the changes file... (e.g. when starting a second invocation of Pharo...) Regards, Gary ----- Original Message ----- From: "Igor Stasenko" <siguctua@gmail.com> To: <Pharo-project@lists.gforge.inria.fr> Sent: Tuesday, May 03, 2011 2:52 AM Subject: Re: [Pharo-project] PharoCore 1.3 built stalled On 3 May 2011 00:49, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
it is my fault but I have no idea how to solve it. A package was loading over an already existing one and you get a pop up.
i have a fix for it. See #4075 it makes sure that no matter what current UI manager you using (running image headless or not) a system startup (all classes startup) is _always_ performed using non-interactive UI manager. So, since CommandLine file-in scripts during startup, this will make sure that it will run non-interactively.
Stef
On May 2, 2011, at 11:39 PM, Igor Stasenko wrote:
On 2 May 2011 23:26, Igor Stasenko <siguctua@gmail.com> wrote:
On 2 May 2011 23:13, laurent laffont <laurent.laffont@gmail.com> wrote:
Last built started more than 1 day ago and not finished .... Laurent.
This is not good. I killed the jobs. Lets see if it will repeat again.
Okay the problem is that there is a warning and it is handled by MorphicUIManager, instead of NonInteractiveUIManager which just forcing it to always proceed, while morphic one expects user to press proceed or abandon.
So, the problem is with an update of progressTitle: 'Loading 13179-Pha-PlentyOfCleans...'
But i don't undestand why it not switched to NonInteractiveUIManager at image startup. Aha.. i guess i know why. Is its not because command line stuff that are triggered at image startup, which tries to evaluate some code before full startup procedure completes?
A command line , i think should be changed to start loading external code only after everything else is started (including UI manager). Otherwise we will have problems like that.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
On Wed, May 4, 2011 at 5:04 PM, Gary Chambers <gazzaguru2@btinternet.com>wrote:
Of course, now, we get no warning of being unable to write to the changes file... (e.g. when starting a second invocation of Pharo...)
Once (at brussels Sprint) I suggested Igor to change the headless UIMAnager so that if receives iteration, instead (or maybe in addition) to throwing an error, to log somewhere (kind of Transcipt in file) about such event. Maybe it is worth it...
Regards, Gary
----- Original Message ----- From: "Igor Stasenko" <siguctua@gmail.com> To: <Pharo-project@lists.gforge.inria.fr> Sent: Tuesday, May 03, 2011 2:52 AM Subject: Re: [Pharo-project] PharoCore 1.3 built stalled
On 3 May 2011 00:49, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
it is my fault but I have no idea how to solve it. A package was loading over an already existing one and you get a pop up.
i have a fix for it. See #4075
it makes sure that no matter what current UI manager you using (running image headless or not) a system startup (all classes startup) is _always_ performed using non-interactive UI manager.
So, since CommandLine file-in scripts during startup, this will make sure that it will run non-interactively.
Stef
On May 2, 2011, at 11:39 PM, Igor Stasenko wrote:
On 2 May 2011 23:26, Igor Stasenko <siguctua@gmail.com> wrote:
On 2 May 2011 23:13, laurent laffont <laurent.laffont@gmail.com> wrote:
Last built started more than 1 day ago and not finished .... Laurent.
This is not good. I killed the jobs. Lets see if it will repeat again.
Okay the problem is that there is a warning and it is handled by MorphicUIManager, instead of NonInteractiveUIManager which just forcing it to always proceed, while morphic one expects user to press proceed or abandon.
So, the problem is with an update of progressTitle: 'Loading 13179-Pha-PlentyOfCleans...'
But i don't undestand why it not switched to NonInteractiveUIManager at image startup. Aha.. i guess i know why. Is its not because command line stuff that are triggered at image startup, which tries to evaluate some code before full startup procedure completes?
A command line , i think should be changed to start loading external code only after everything else is started (including UI manager). Otherwise we will have problems like that.
--
Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
-- Mariano http://marianopeck.wordpress.com
On 4 May 2011 17:11, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Wed, May 4, 2011 at 5:04 PM, Gary Chambers <gazzaguru2@btinternet.com> wrote:
Of course, now, we get no warning of being unable to write to the changes file... (e.g. when starting a second invocation of Pharo...)
Once (at brussels Sprint) I suggested Igor to change the headless UIMAnager so that if receives iteration, instead (or maybe in addition) to throwing an error, to log somewhere (kind of Transcipt in file) about such event. Maybe it is worth it...
headless ui manager logs all errors, warnings and notices to PharoDebug.log
Regards, Gary
----- Original Message ----- From: "Igor Stasenko" <siguctua@gmail.com> To: <Pharo-project@lists.gforge.inria.fr> Sent: Tuesday, May 03, 2011 2:52 AM Subject: Re: [Pharo-project] PharoCore 1.3 built stalled
On 3 May 2011 00:49, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
it is my fault but I have no idea how to solve it. A package was loading over an already existing one and you get a pop up.
i have a fix for it. See #4075
it makes sure that no matter what current UI manager you using (running image headless or not) a system startup (all classes startup) is _always_ performed using non-interactive UI manager.
So, since CommandLine file-in scripts during startup, this will make sure that it will run non-interactively.
Stef
On May 2, 2011, at 11:39 PM, Igor Stasenko wrote:
On 2 May 2011 23:26, Igor Stasenko <siguctua@gmail.com> wrote:
On 2 May 2011 23:13, laurent laffont <laurent.laffont@gmail.com> wrote:
Last built started more than 1 day ago and not finished .... Laurent.
This is not good. I killed the jobs. Lets see if it will repeat again.
Okay the problem is that there is a warning and it is handled by MorphicUIManager, instead of NonInteractiveUIManager which just forcing it to always proceed, while morphic one expects user to press proceed or abandon.
So, the problem is with an update of progressTitle: 'Loading 13179-Pha-PlentyOfCleans...'
But i don't undestand why it not switched to NonInteractiveUIManager at image startup. Aha.. i guess i know why. Is its not because command line stuff that are triggered at image startup, which tries to evaluate some code before full startup procedure completes?
A command line , i think should be changed to start loading external code only after everything else is started (including UI manager). Otherwise we will have problems like that.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
-- Mariano http://marianopeck.wordpress.com
-- Best regards, Igor Stasenko AKA sig.
On 4 May 2011 17:04, Gary Chambers <gazzaguru2@btinternet.com> wrote:
Of course, now, we get no warning of being unable to write to the changes file... (e.g. when starting a second invocation of Pharo...)
which is never shown properly , because it was "shown" before morphic initialized. To fix that, it should use #addDeferredUIMessage: to inform user, when UI is ready to work after startup is complete. But apparently not in the middle of startup, when you cannot clearly tell, if its already safe to make any calls to morphic or not..
Regards, Gary
----- Original Message ----- From: "Igor Stasenko" <siguctua@gmail.com> To: <Pharo-project@lists.gforge.inria.fr> Sent: Tuesday, May 03, 2011 2:52 AM Subject: Re: [Pharo-project] PharoCore 1.3 built stalled
On 3 May 2011 00:49, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
it is my fault but I have no idea how to solve it. A package was loading over an already existing one and you get a pop up.
i have a fix for it. See #4075
it makes sure that no matter what current UI manager you using (running image headless or not) a system startup (all classes startup) is _always_ performed using non-interactive UI manager.
So, since CommandLine file-in scripts during startup, this will make sure that it will run non-interactively.
Stef
On May 2, 2011, at 11:39 PM, Igor Stasenko wrote:
On 2 May 2011 23:26, Igor Stasenko <siguctua@gmail.com> wrote:
On 2 May 2011 23:13, laurent laffont <laurent.laffont@gmail.com> wrote:
Last built started more than 1 day ago and not finished .... Laurent.
This is not good. I killed the jobs. Lets see if it will repeat again.
Okay the problem is that there is a warning and it is handled by MorphicUIManager, instead of NonInteractiveUIManager which just forcing it to always proceed, while morphic one expects user to press proceed or abandon.
So, the problem is with an update of progressTitle: 'Loading 13179-Pha-PlentyOfCleans...'
But i don't undestand why it not switched to NonInteractiveUIManager at image startup. Aha.. i guess i know why. Is its not because command line stuff that are triggered at image startup, which tries to evaluate some code before full startup procedure completes?
A command line , i think should be changed to start loading external code only after everything else is started (including UI manager). Otherwise we will have problems like that.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
Indeed, perhaps then an alert after startup showing startup "issues"? Regards, Gary ----- Original Message ----- From: "Igor Stasenko" <siguctua@gmail.com> To: <Pharo-project@lists.gforge.inria.fr> Sent: Wednesday, May 04, 2011 4:45 PM Subject: Re: [Pharo-project] PharoCore 1.3 built stalled On 4 May 2011 17:04, Gary Chambers <gazzaguru2@btinternet.com> wrote:
Of course, now, we get no warning of being unable to write to the changes file... (e.g. when starting a second invocation of Pharo...)
which is never shown properly , because it was "shown" before morphic initialized. To fix that, it should use #addDeferredUIMessage: to inform user, when UI is ready to work after startup is complete. But apparently not in the middle of startup, when you cannot clearly tell, if its already safe to make any calls to morphic or not..
Regards, Gary
----- Original Message ----- From: "Igor Stasenko" <siguctua@gmail.com> To: <Pharo-project@lists.gforge.inria.fr> Sent: Tuesday, May 03, 2011 2:52 AM Subject: Re: [Pharo-project] PharoCore 1.3 built stalled
On 3 May 2011 00:49, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
it is my fault but I have no idea how to solve it. A package was loading over an already existing one and you get a pop up.
i have a fix for it. See #4075
it makes sure that no matter what current UI manager you using (running image headless or not) a system startup (all classes startup) is _always_ performed using non-interactive UI manager.
So, since CommandLine file-in scripts during startup, this will make sure that it will run non-interactively.
Stef
On May 2, 2011, at 11:39 PM, Igor Stasenko wrote:
On 2 May 2011 23:26, Igor Stasenko <siguctua@gmail.com> wrote:
On 2 May 2011 23:13, laurent laffont <laurent.laffont@gmail.com> wrote:
Last built started more than 1 day ago and not finished .... Laurent.
This is not good. I killed the jobs. Lets see if it will repeat again.
Okay the problem is that there is a warning and it is handled by MorphicUIManager, instead of NonInteractiveUIManager which just forcing it to always proceed, while morphic one expects user to press proceed or abandon.
So, the problem is with an update of progressTitle: 'Loading 13179-Pha-PlentyOfCleans...'
But i don't undestand why it not switched to NonInteractiveUIManager at image startup. Aha.. i guess i know why. Is its not because command line stuff that are triggered at image startup, which tries to evaluate some code before full startup procedure completes?
A command line , i think should be changed to start loading external code only after everything else is started (including UI manager). Otherwise we will have problems like that.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
On 4 May 2011 17:48, Gary Chambers <gazzaguru2@btinternet.com> wrote:
Indeed, perhaps then  an alert after startup showing startup "issues"?
Yes, something like that. The point is, that during startup there should be no code, which shows a dialog and waiting user to press ok. Using UI during startup procedure is silly anyways, because you cannot be really sure, if there are UI at all (for instance this warning about .changes file could occur in image with having no morphic installed ;)
Regards, Gary
----- Original Message ----- From: "Igor Stasenko" <siguctua@gmail.com> To: <Pharo-project@lists.gforge.inria.fr> Sent: Wednesday, May 04, 2011 4:45 PM Subject: Re: [Pharo-project] PharoCore 1.3 built stalled
On 4 May 2011 17:04, Gary Chambers <gazzaguru2@btinternet.com> wrote:
Of course, now, we get no warning of being unable to write to the changes file... (e.g. when starting a second invocation of Pharo...)
which is never shown properly , because it was "shown" before morphic initialized. To fix that, it should use #addDeferredUIMessage: to inform user, when UI is ready to work after startup is complete.
But apparently not in the middle of startup, when you cannot clearly tell, if its already safe to make any calls to morphic or not..
Regards, Gary
----- Original Message ----- From: "Igor Stasenko" <siguctua@gmail.com> To: <Pharo-project@lists.gforge.inria.fr> Sent: Tuesday, May 03, 2011 2:52 AM Subject: Re: [Pharo-project] PharoCore 1.3 built stalled
On 3 May 2011 00:49, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
it is my fault but I have no idea how to solve it. A package was loading over an already existing one and you get a pop up.
i have a fix for it. See #4075
it makes sure that no matter what current UI manager you using (running image headless or not) a system startup (all classes startup) is _always_ performed using non-interactive UI manager.
So, since CommandLine file-in scripts during startup, this will make sure that it will run non-interactively.
Stef
On May 2, 2011, at 11:39 PM, Igor Stasenko wrote:
On 2 May 2011 23:26, Igor Stasenko <siguctua@gmail.com> wrote:
On 2 May 2011 23:13, laurent laffont <laurent.laffont@gmail.com> wrote:
Last built started more than 1 day ago and not finished .... Laurent.
This is not good. I killed the jobs. Lets see if it will repeat again.
Okay the problem is that there is a warning and it is handled by MorphicUIManager, instead of NonInteractiveUIManager which just forcing it to always proceed, while morphic one expects user to press proceed or abandon.
So, the problem is with an update of progressTitle: 'Loading 13179-Pha-PlentyOfCleans...'
But i don't undestand why it not switched to NonInteractiveUIManager at image startup. Aha.. i guess i know why. Is its not because command line stuff that are triggered at image startup, which tries to evaluate some code before full startup procedure completes?
A command line , i think should be changed to start loading external code only after everything else is started (including UI manager). Otherwise we will have problems like that.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
A command line , i think should be changed to start loading external code only after everything else is started (including UI manager). Otherwise we will have problems like that.
add a bug entry.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
participants (5)
-
Gary Chambers -
Igor Stasenko -
laurent laffont -
Mariano Martinez Peck -
Stéphane Ducasse