Closed hannesrauhe closed 10 years ago
Is there no timeout? What kind of connection? But you're right, connecting in background would be a lot of additional work.
It's a problem in my VM: every connection is stuck, when I change the network, so I guess there is some system call involved that does not timeout. It's a general problem: the twitter thread also hangs and I'm unable to even close the lunchinator when that happens. It's waiting for I/O. In the twitter case the I/O is handled in the background. That means the lunchinator works until you try to close it. I did some googleing. It seems there is no way out.
Since we want to have the database connection ready on startup it would not make sense to do this in the background anyway.
TL;DR This is a VM-specific problem and has nothing to do with the lunchinator itself. Other application are blocked as well when that happens.
I'm not sure if we can fix that... When connecting to a remote database this blocks the startup and everything else.
Maybe when can at least show some notification why nothing is happening.