Actually the problem is even worse, NetNameResolver class>>#addressForName: not just hangs for at least its timeout period, during that time the whole image seems to be blocked (as it is a primitive). That is why this is so annoying (spotter goes to great length to work in a background thread, but that does not seem to help here).
On 19 May 2016, at 13:53, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 19 May 2016, at 13:41, stepharo <stepharo@free.fr> 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.
That is the issue that we should fix.
Assuming someone has no internet, and force them to manage the connection state themselves manually, seems very backward to me - in this century.
So I vote against turning it off.
We should also improve the comment of the catalog setting because it is unclear
that this is this setting that should be turned off.
Yes that would be good.
Stef