> On 19 May 2016, at 19:36, Alistair Grant <[email protected]> wrote: > > On Thu, May 19, 2016 at 01:53:04PM +0200, Sven Van Caekenberghe wrote: >> >>> On 19 May 2016, at 13:41, stepharo <[email protected]> wrote: >>> >>> Hi guys >>> >>> This is hyper annoying that Spotter look for the net by default. >>> >>> We should turn it off. >> >> This was 'fixed' in the sense that it now only gets it once every 24 >> hours and then caches it in the image. >> >> The real problem is that NetNameResolver (dns name -> IP address >> resolution, using of course opaque primitives) sometimes hangs. This >> makes it very hard for the image to decide if it has network >> connection or not. And thus hard to react in an intelligent way. >> >> This situation is also hard to debug, because if I turn off my >> wireless network, NetNameResolver fails immediately (which is >> perfect). It is hard to reproduce the case where it hangs, at least >> for me. > > I think this can be "easily" reproduced by leaving Pharo running while > switching networks. > > I haven't tested this explicitly, but my working assumption at the > moment is that if I suspend my laptop with Pharo running and connect to > a different network then Pharo will hang on the first network access.
I do this every day twice (home > work > home) and it never fails. > I'll try and track this down further if someone wants. Yes please, but include details (platform, OS, versions). > Cheers, > Alistair
