Issue: There have been reports of the Runner not working if no internet connection could be established. Also, firewall or port blocking from institutional VPN's can lead to a "no internet connection" error.
This should not happen, at least not on a local machine. When running a model locally and all packages are installed, the Runner should work. The issue is when LibRegistry tries to install packages (even though no new package needed).
If possible, catch the "no internet connection" error and throw a warning into the LOGGER instead. If a package needs to be installed with no internet available, only then we can throw an error.
Issue: There have been reports of the Runner not working if no internet connection could be established. Also, firewall or port blocking from institutional VPN's can lead to a "no internet connection" error.
This should not happen, at least not on a local machine. When running a model locally and all packages are installed, the Runner should work. The issue is when LibRegistry tries to install packages (even though no new package needed). If possible, catch the "no internet connection" error and throw a warning into the LOGGER instead. If a package needs to be installed with no internet available, only then we can throw an error.