localizer
localizer copied to clipboard
infinite loop after waking from sleep
If my laptop goes to sleep for a long time localizer will go into an infinite loop of trying to open endpoints
I can usually resolve this pretty quickly by just restarting it
I bring this up because I can think of a couple of things that might be good features worth thinking about.
- notice that the app has been asleep and missed a bunch of events and redo the internal state (may be connected to #19 )
- limit the number of times a host file can be updated in a time period maybe once every 5 seconds or something (updating the host file a bunch of times causes the machine to have trouble with DNS)
- just die if localizer missed a bunch of events
These all seem like pretty good improvements!
This would be very helpful!