Re: [Pharo-project] froze image just
Btw. Waiting for network timeout doesn't work. That is to say, waiting a night is not long enough Stephan Verstuurd vanaf mijn iPhone
Yes :) Same behavior here On May 1, 2013, at 11:51 AM, Stephan Eggermont <stephan@stack.nl> wrote:
Btw. Waiting for network timeout doesn't work. That is to say, waiting a night is not long enough
Stephan
Verstuurd vanaf mijn iPhone
On 01 May 2013, at 14:06, stephane ducasse <stephane.ducasse@free.fr> wrote:
Yes :) Same behavior here On May 1, 2013, at 11:51 AM, Stephan Eggermont <stephan@stack.nl> wrote:
Btw. Waiting for network timeout doesn't work. That is to say, waiting a night is not long enough
Stephan
Verstuurd vanaf mijn iPhone
Well, Stephan or Stéphane, give us/me a repeatable use case on Mac OS X (preferably using latest VM and 2.0) where you are sure a network timeout should occur and it doesn't. It has to include a description of what is precisely 'no network'. I know it is not perfect, but to make any progress we need something concrete. Sven
I created a slice then pressed save when clicking on the package cache and I was on the train my connection was flaky. So I should retry to see if I cut internet I get the same behavior Stef On May 1, 2013, at 2:16 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 01 May 2013, at 14:06, stephane ducasse <stephane.ducasse@free.fr> wrote:
Yes :) Same behavior here On May 1, 2013, at 11:51 AM, Stephan Eggermont <stephan@stack.nl> wrote:
Btw. Waiting for network timeout doesn't work. That is to say, waiting a night is not long enough
Stephan
Verstuurd vanaf mijn iPhone
Well, Stephan or Stéphane, give us/me a repeatable use case on Mac OS X (preferably using latest VM and 2.0) where you are sure a network timeout should occur and it doesn't. It has to include a description of what is precisely 'no network'.
I know it is not perfect, but to make any progress we need something concrete.
Sven
Maybe something like this will help... http://architects.dzone.com/articles/simulate-network-latency cheers -ben stephane ducasse wrote:
I created a slice then pressed save when clicking on the package cache and I was on the train my connection was flaky. So I should retry to see if I cut internet I get the same behavior
Stef On May 1, 2013, at 2:16 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 01 May 2013, at 14:06, stephane ducasse <stephane.ducasse@free.fr> wrote:
Yes :) Same behavior here On May 1, 2013, at 11:51 AM, Stephan Eggermont <stephan@stack.nl> wrote:
Btw. Waiting for network timeout doesn't work. That is to say, waiting a night is not long enough
Stephan
Verstuurd vanaf mijn iPhone
Well, Stephan or Stéphane, give us/me a repeatable use case on Mac OS X (preferably using latest VM and 2.0) where you are sure a network timeout should occur and it doesn't. It has to include a description of what is precisely 'no network'.
I know it is not perfect, but to make any progress we need something concrete.
Sven
On 1 May 2013 19:45, Ben Coman <btc@openinworld.com> wrote:
Maybe something like this will help... http://architects.dzone.com/articles/simulate-network-latency
yeah.. good-old ipfw (know it by heart from times when i was working with FreeBSD)
cheers -ben
stephane ducasse wrote:
I created a slice then pressed save when clicking on the package cache and I was on the train my connection was flaky. So I should retry to see if I cut internet I get the same behavior
Stef On May 1, 2013, at 2:16 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 01 May 2013, at 14:06, stephane ducasse <stephane.ducasse@free.fr> wrote:
Yes :) Same behavior here On May 1, 2013, at 11:51 AM, Stephan Eggermont <stephan@stack.nl> wrote:
Btw. Waiting for network timeout doesn't work. That is to say, waiting a night is not long enough
Stephan
Verstuurd vanaf mijn iPhone
Well, Stephan or Stéphane, give us/me a repeatable use case on Mac OS X (preferably using latest VM and 2.0) where you are sure a network timeout should occur and it doesn't. It has to include a description of what is precisely 'no network'.
I know it is not perfect, but to make any progress we need something concrete.
Sven
-- Best regards, Igor Stasenko.
Same problem in same train situation. I press commit on local directory and system start connect to smalltalkhub repository and hang for ever. Why system doing this when I use local repository? 2013/5/1 stephane ducasse <stephane.ducasse@free.fr>
I created a slice then pressed save when clicking on the package cache and I was on the train my connection was flaky. So I should retry to see if I cut internet I get the same behavior
Stef On May 1, 2013, at 2:16 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 01 May 2013, at 14:06, stephane ducasse <stephane.ducasse@free.fr>
wrote:
Yes :) Same behavior here On May 1, 2013, at 11:51 AM, Stephan Eggermont <stephan@stack.nl>
wrote:
Btw. Waiting for network timeout doesn't work. That is to say, waiting
a night is not long enough
Stephan
Verstuurd vanaf mijn iPhone
Well, Stephan or Stéphane, give us/me a repeatable use case on Mac OS X (preferably using latest VM and 2.0) where you are sure a network timeout should occur and it doesn't. It has to include a description of what is precisely 'no network'.
I know it is not perfect, but to make any progress we need something concrete.
Sven
And I use Windows 7 2013/5/2 Denis Kudriashov <dionisiydk@gmail.com>
Same problem in same train situation. I press commit on local directory and system start connect to smalltalkhub repository and hang for ever. Why system doing this when I use local repository?
2013/5/1 stephane ducasse <stephane.ducasse@free.fr>
I created a slice then pressed save when clicking on the package cache and I was on the train my connection was flaky. So I should retry to see if I cut internet I get the same behavior
Stef On May 1, 2013, at 2:16 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 01 May 2013, at 14:06, stephane ducasse <stephane.ducasse@free.fr>
wrote:
Yes :) Same behavior here On May 1, 2013, at 11:51 AM, Stephan Eggermont <stephan@stack.nl>
wrote:
Btw. Waiting for network timeout doesn't work. That is to say,
waiting a night is not long enough
Stephan
Verstuurd vanaf mijn iPhone
Well, Stephan or Stéphane, give us/me a repeatable use case on Mac OS X (preferably using latest VM and 2.0) where you are sure a network timeout should occur and it doesn't. It has to include a description of what is precisely 'no network'.
I know it is not perfect, but to make any progress we need something concrete.
Sven
On 2013-05-02, at 08:36, Denis Kudriashov <dionisiydk@gmail.com> wrote:
Same problem in same train situation. I press commit on local directory and system start connect to smalltalkhub repository and hang for ever. Why system doing this when I use local repository?
Because MC has some limitations :). If you commit a package that is by default in Pharo you'll always have the Pharo30 repository there. So when you commit MC tries to be smart and gather a unique version number by checking ALL repositories ... there is your issue :(
2013/5/2 Camillo Bruni <camillobruni@gmail.com>
On 2013-05-02, at 08:36, Denis Kudriashov <dionisiydk@gmail.com> wrote:
Same problem in same train situation. I press commit on local directory and system start connect to smalltalkhub repository and hang for ever. Why system doing this when I use local repository?
Because MC has some limitations :). If you commit a package that is by default in Pharo you'll always have the Pharo30 repository there. So when you commit MC tries to be smart and gather a unique version number by checking ALL repositories ... there is your issue :(
It makes offline work impossible. Can we add setting for this?
On 2013-05-02, at 09:01, Denis Kudriashov <dionisiydk@gmail.com> wrote:
2013/5/2 Camillo Bruni <camillobruni@gmail.com>
On 2013-05-02, at 08:36, Denis Kudriashov <dionisiydk@gmail.com> wrote:
Same problem in same train situation. I press commit on local directory and system start connect to smalltalkhub repository and hang for ever. Why system doing this when I use local repository?
Because MC has some limitations :). If you commit a package that is by default in Pharo you'll always have the Pharo30 repository there. So when you commit MC tries to be smart and gather a unique version number by checking ALL repositories ... there is your issue :(
It makes offline work impossible. Can we add setting for this?
yes I know. Humm yeah, I guess we could solve this by having setting to disable the "global" unique version number check...
On 02 May 2013, at 09:01, Denis Kudriashov <dionisiydk@gmail.com> wrote:
2013/5/2 Camillo Bruni <camillobruni@gmail.com>
On 2013-05-02, at 08:36, Denis Kudriashov <dionisiydk@gmail.com> wrote:
Same problem in same train situation. I press commit on local directory and system start connect to smalltalkhub repository and hang for ever. Why system doing this when I use local repository?
Because MC has some limitations :). If you commit a package that is by default in Pharo you'll always have the Pharo30 repository there. So when you commit MC tries to be smart and gather a unique version number by checking ALL repositories ... there is your issue :(
It makes offline work impossible. Can we add setting for this?
Yes, there should be a setting that says: 'MC should not check other repositories for potential conflicts when saving'. It is a lot faster when you do have network as well. Sven
participants (7)
-
Ben Coman -
Camillo Bruni -
Denis Kudriashov -
Igor Stasenko -
Stephan Eggermont -
stephane ducasse -
Sven Van Caekenberghe