SessionManager and SystemSettings?
My stored settings aren't loaded at start up anymore (for example, in Pharo 60107). any ideas?
2016-06-23 11:33 GMT+02:00 Sven Van Caekenberghe <sven@stfx.eu>:
An error during the load ?
I do not see any error message. Settings were automatically load until Pharo 60102 Since Pharo 60103, it does not load any stored settings on startup.
On 23 Jun 2016, at 09:01, Nicolai Hess <nicolaihess@gmail.com> wrote:
My stored settings aren't loaded at start up anymore (for example, in Pharo 60107).
any ideas?
What happens if you execute 'SystemSettingsPersistence resumeSystemSettingsâ in a 60103 image? If nothing happens, it could be that 'SystemSettingsPersistence instVarNamed: âalreadyResumedââ is true I checked the startupList and PharoCommandLineHandler>>#runPreferences but nothing changed there.
Le 23 juin 2016 à 11:42, Nicolai Hess <nicolaihess@gmail.com> a écrit :
2016-06-23 11:33 GMT+02:00 Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@stfx.eu>>: An error during the load ?
I do not see any error message. Settings were automatically load until Pharo 60102 Since Pharo 60103, it does not load any stored settings on startup.
On 23 Jun 2016, at 09:01, Nicolai Hess <nicolaihess@gmail.com <mailto:nicolaihess@gmail.com>> wrote:
My stored settings aren't loaded at start up anymore (for example, in Pharo 60107).
any ideas?
2016-06-23 15:07 GMT+02:00 Christophe Demarey <christophe.demarey@inria.fr>:
What happens if you execute 'SystemSettingsPersistence resumeSystemSettingsâ in a 60103 image? If nothing happens, it could be that 'SystemSettingsPersistence instVarNamed: âalreadyResumedââ is true
Yes, nothing happens. Any way to read out SystemSettingsPersistence alreadyResumed value, before the resumeSystemSettings is executed on startup ?
I checked the startupList and PharoCommandLineHandler>>#runPreferences but nothing changed there.
Le 23 juin 2016 à 11:42, Nicolai Hess <nicolaihess@gmail.com> a écrit :
2016-06-23 11:33 GMT+02:00 Sven Van Caekenberghe <sven@stfx.eu>:
An error during the load ?
I do not see any error message. Settings were automatically load until Pharo 60102 Since Pharo 60103, it does not load any stored settings on startup.
On 23 Jun 2016, at 09:01, Nicolai Hess <nicolaihess@gmail.com> wrote:
My stored settings aren't loaded at start up anymore (for example, in Pharo 60107).
any ideas?
On 23/06/2016 15:07, Christophe Demarey wrote:
What happens if you execute 'SystemSettingsPersistence resumeSystemSettingsâ in a 60103 image? If nothing happens, it could be that 'SystemSettingsPersistence instVarNamed: âalreadyResumedââ is true
I checked the startupList and PharoCommandLineHandler>>#runPreferences but nothing changed there.
I think I read something about a script esteban added to clear the ever-growing stack. Couldn't it be that? Maybe it open the image and the system setting think he already loaded the settings.
-- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France
On 23 Jun 2016, at 15:29, Cyril Ferlicot Delbecque <cyril.ferlicot@gmail.com> wrote:
On 23/06/2016 15:07, Christophe Demarey wrote:
What happens if you execute 'SystemSettingsPersistence resumeSystemSettingsâ in a 60103 image? If nothing happens, it could be that 'SystemSettingsPersistence instVarNamed: âalreadyResumedââ is true
I checked the startupList and PharoCommandLineHandler>>#runPreferences but nothing changed there.
I think I read something about a script esteban added to clear the ever-growing stack. Couldn't it be that? Maybe it open the image and the
system setting think he already loaded the settings.
no it shouldnât⦠and *my* preferences are correctly loaded :)
-- Cyril Ferlicot
165 Avenue Bretagne Lille 59000 France
On 23/06/2016 15:32, Esteban Lorenzano wrote:
no it shouldnât⦠and *my* preferences are correctly loaded :)
I check on my Mac, mine are loaded too. -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France
On 23 Jun 2016, at 15:32, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 23 Jun 2016, at 15:29, Cyril Ferlicot Delbecque <cyril.ferlicot@gmail.com> wrote:
On 23/06/2016 15:07, Christophe Demarey wrote:
What happens if you execute 'SystemSettingsPersistence resumeSystemSettingsâ in a 60103 image? If nothing happens, it could be that 'SystemSettingsPersistence instVarNamed: âalreadyResumedââ is true
I checked the startupList and PharoCommandLineHandler>>#runPreferences but nothing changed there.
I think I read something about a script esteban added to clear the ever-growing stack. Couldn't it be that? Maybe it open the image and the
system setting think he already loaded the settings.
no it shouldnât⦠and *my* preferences are correctly loaded :)
Are you talking about preferences or startup scripts?
-- Cyril Ferlicot
http://www.synectique.eu <http://www.synectique.eu/>
165 Avenue Bretagne Lille 59000 France
2016-06-23 15:32 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com>:
On 23 Jun 2016, at 15:29, Cyril Ferlicot Delbecque < cyril.ferlicot@gmail.com> wrote:
On 23/06/2016 15:07, Christophe Demarey wrote:
What happens if you execute 'SystemSettingsPersistence resumeSystemSettingsâ in a 60103 image? If nothing happens, it could be that 'SystemSettingsPersistence instVarNamed: âalreadyResumedââ is true
I checked the startupList and PharoCommandLineHandler>>#runPreferences but nothing changed there.
I think I read something about a script esteban added to clear the ever-growing stack. Couldn't it be that? Maybe it open the image and the
system setting think he already loaded the settings.
no it shouldnât⦠and *my* preferences are correctly loaded :)
Can we please fix this. I work a lot with fresh images, and now every time a start a new image and trying to access a repository I have to remmember to set the network proxy settings.
-- Cyril Ferlicot
165 Avenue Bretagne Lille 59000 France
cc Juraj
On 25 Jun 2016, at 22:28, Nicolai Hess <nicolaihess@gmail.com> wrote:
2016-06-23 15:32 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>>:
On 23 Jun 2016, at 15:29, Cyril Ferlicot Delbecque <cyril.ferlicot@gmail.com <mailto:cyril.ferlicot@gmail.com>> wrote:
On 23/06/2016 15:07, Christophe Demarey wrote:
What happens if you execute 'SystemSettingsPersistence resumeSystemSettingsâ in a 60103 image? If nothing happens, it could be that 'SystemSettingsPersistence instVarNamed: âalreadyResumedââ is true
I checked the startupList and PharoCommandLineHandler>>#runPreferences but nothing changed there.
I think I read something about a script esteban added to clear the ever-growing stack. Couldn't it be that? Maybe it open the image and the
system setting think he already loaded the settings.
no it shouldnât⦠and *my* preferences are correctly loaded :)
Can we please fix this. I work a lot with fresh images, and now every time a start a new image and trying to access a repository I have to remmember to set the network proxy settings.
-- Cyril Ferlicot
http://www.synectique.eu <http://www.synectique.eu/>
165 Avenue Bretagne Lille 59000 France
Thanks Yuriy! Last time, there was a problem on Jenkins. I do not have access to check it or change it. It is necessary that cleanUp process is called as a last command on Jenkins. The other thing is to find out another solution. The current solution expects that an instance variable is unset in a fresh (downloaded) image. And this variable is set when the image is opened. Cheers, Juraj
On Jun 25, 2016, at 17:25, Yuriy Tymchuk <yuriy.tymchuk@me.com <mailto:yuriy.tymchuk@me.com>> wrote:
cc Juraj
On 25 Jun 2016, at 22:28, Nicolai Hess <nicolaihess@gmail.com <mailto:nicolaihess@gmail.com>> wrote:
2016-06-23 15:32 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>>:
On 23 Jun 2016, at 15:29, Cyril Ferlicot Delbecque <cyril.ferlicot@gmail.com <mailto:cyril.ferlicot@gmail.com>> wrote:
On 23/06/2016 15:07, Christophe Demarey wrote:
What happens if you execute 'SystemSettingsPersistence resumeSystemSettingsâ in a 60103 image? If nothing happens, it could be that 'SystemSettingsPersistence instVarNamed: âalreadyResumedââ is true
I checked the startupList and PharoCommandLineHandler>>#runPreferences but nothing changed there.
I think I read something about a script esteban added to clear the ever-growing stack. Couldn't it be that? Maybe it open the image and the
system setting think he already loaded the settings.
no it shouldnât⦠and *my* preferences are correctly loaded :)
Can we please fix this. I work a lot with fresh images, and now every time a start a new image and trying to access a repository I have to remmember to set the network proxy settings.
-- Cyril Ferlicot
http://www.synectique.eu <http://www.synectique.eu/>
165 Avenue Bretagne Lille 59000 France
Settings should work now
On 26 Jun 2016, at 04:56, Juraj Kubelka <juraj.kubelka@icloud.com> wrote:
Thanks Yuriy!
Last time, there was a problem on Jenkins. I do not have access to check it or change it. It is necessary that cleanUp process is called as a last command on Jenkins.
The other thing is to find out another solution. The current solution expects that an instance variable is unset in a fresh (downloaded) image. And this variable is set when the image is opened.
Cheers, Juraj
On Jun 25, 2016, at 17:25, Yuriy Tymchuk <yuriy.tymchuk@me.com <mailto:yuriy.tymchuk@me.com>> wrote:
cc Juraj
On 25 Jun 2016, at 22:28, Nicolai Hess <nicolaihess@gmail.com <mailto:nicolaihess@gmail.com>> wrote:
2016-06-23 15:32 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>>:
On 23 Jun 2016, at 15:29, Cyril Ferlicot Delbecque <cyril.ferlicot@gmail.com <mailto:cyril.ferlicot@gmail.com>> wrote:
On 23/06/2016 15:07, Christophe Demarey wrote:
What happens if you execute 'SystemSettingsPersistence resumeSystemSettingsâ in a 60103 image? If nothing happens, it could be that 'SystemSettingsPersistence instVarNamed: âalreadyResumedââ is true
I checked the startupList and PharoCommandLineHandler>>#runPreferences but nothing changed there.
I think I read something about a script esteban added to clear the ever-growing stack. Couldn't it be that? Maybe it open the image and the
system setting think he already loaded the settings.
no it shouldnât⦠and *my* preferences are correctly loaded :)
Can we please fix this. I work a lot with fresh images, and now every time a start a new image and trying to access a repository I have to remmember to set the network proxy settings.
-- Cyril Ferlicot
http://www.synectique.eu <http://www.synectique.eu/>
165 Avenue Bretagne Lille 59000 France
2016-07-10 23:49 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk@me.com>:
Settings should work now
Yes! Thanks :-)
On 26 Jun 2016, at 04:56, Juraj Kubelka <juraj.kubelka@icloud.com> wrote:
Thanks Yuriy!
Last time, there was a problem on Jenkins. I do not have access to check it or change it. It is necessary that cleanUp process is called as a last command on Jenkins.
The other thing is to find out another solution. The current solution expects that an instance variable is unset in a fresh (downloaded) image. And this variable is set when the image is opened.
Cheers, Juraj
On Jun 25, 2016, at 17:25, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
cc Juraj
On 25 Jun 2016, at 22:28, Nicolai Hess <nicolaihess@gmail.com> wrote:
2016-06-23 15:32 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com>:
On 23 Jun 2016, at 15:29, Cyril Ferlicot Delbecque < cyril.ferlicot@gmail.com> wrote:
On 23/06/2016 15:07, Christophe Demarey wrote:
What happens if you execute 'SystemSettingsPersistence resumeSystemSettingsâ in a 60103 image? If nothing happens, it could be that 'SystemSettingsPersistence instVarNamed: âalreadyResumedââ is true
I checked the startupList and PharoCommandLineHandler>>#runPreferences but nothing changed there.
I think I read something about a script esteban added to clear the ever-growing stack. Couldn't it be that? Maybe it open the image and the
system setting think he already loaded the settings.
no it shouldnât⦠and *my* preferences are correctly loaded :)
Can we please fix this. I work a lot with fresh images, and now every time a start a new image and trying to access a repository I have to remmember to set the network proxy settings.
-- Cyril Ferlicot
165 Avenue Bretagne Lille 59000 France
participants (7)
-
Christophe Demarey -
Cyril Ferlicot Delbecque -
Esteban Lorenzano -
Juraj Kubelka -
Nicolai Hess -
Sven Van Caekenberghe -
Yuriy Tymchuk