SCOOP crashes depending on network connection. about scoop HOT 1 OPEN

Thanks for reaching out. I'm happy to see that SCOOP works for you at home.
I have a guess about what's happening when you disable your internet connection: SCOOP queries the networking module to get an identifier of the local system. When you disable every interface, this particular query fails (as it cannot get an identifier). By the way, I'm not sure I understand what you mean by your work's internet connection which is a disabled interface?

As to why it isn't reported more appropriately in a Python traceback, I am not sure. My best bet would be that most of SCOOP runs into a 'sandbox' generated by runpy. When the identity query call fails, if it does not fail at runtime but import time, that would explain what you are seeing (and runpy eats away the error message).

Now, as per the fix, I am of course welcoming any pull requests. These times, I am a bit overwhelmed with other projects, so I can't guarantee a quick fix on my part. If you are ready to mess a bit with the code, here's what I would try: on scoop/utils.py, try replacing the call to socket.getfqdn() to a static string of your choice. I believe it could be the culprit in your problem.

from scoop.