You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OLS currently makes a request to Github on startup to potentially update itself.
If this request fails, OLS shuts down. This is annoying when e.g. traveling and not having a constant internet connection, because OLS cannot be used at all unless the project was loaded at an earlier point in time with internet connection.
It would be great if it could just ignore failed update requests and start up anyway.
The text was updated successfully, but these errors were encountered:
I think my initial diagnosis might not be correct, but here are some observations I have made: when OLS notices there is a new version available and I dismiss the dialog, this appears:
Following this OLS output shows this error message and it shuts down (?) (at least it does not index any files or allow code navigation after this).
[Error - 5:42:17 PM] Odin Language Server Client client: couldn't create connection to server.
Launching server using command /home/tadeo/.config/Code/User/globalStorage/danielgavin.ols/0/ols-x86_64-unknown-linux-gnu failed. Error: spawn /home/tadeo/.config/Code/User/globalStorage/danielgavin.ols/0/ols-x86_64-unknown-linux-gnu ENOENT
Now when I turn off the internet connection and open another project, OLS seems to remember that there is a new version available and tries to download it, but gives this error message after which it also shuts down.
So once it detect that an update is available it seems like you can't use OLS until the update has been done.
OLS currently makes a request to Github on startup to potentially update itself.
If this request fails, OLS shuts down. This is annoying when e.g. traveling and not having a constant internet connection, because OLS cannot be used at all unless the project was loaded at an earlier point in time with internet connection.
It would be great if it could just ignore failed update requests and start up anyway.
The text was updated successfully, but these errors were encountered: