-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension fails to start #110
Comments
Hey @anthonyvdotbe, |
That works. I assume it's due to the fact that I deleted the previous JDK installation at |
The extension is marketed as a better replacement to the RedHat one, and this is the setup experience? |
#124 is the fix that is merged for troubleshooting such issues, hope it helps everyone. It would be available in next release. |
@Achal1607 Please consider reopening. The whole point is that the extension should do this automatically: the extension was able to show me the error/notification dialogs, so it knows the extension is unusable and could simply delete the cache itself in an attempt to recover. |
The dialog could probably have a CTA that directly runs the cache clearing |
We wouldn't prefer to delete cache without user's permission so automatically deleting would probably be not possible but what @StanFromTraction is saying we can try that. |
Automatically deleting the cache without user's permission doesn't seem right and providing dialog box to clear cache for any type of failure to start the extension also doesn't sound that great. So, for now in my opinion we have added the troubleshoot section in the README file and a command to clear the cache is enough. |
For the particular error I reported, the extension should not give an error in the first place & simply be able to locate the JDK. |
When I open VS Code, I see the following errors and the extension fails to start. (And yes, C:\dev\jdk-21.0.2 contains a valid JDK installation.)
extension: 1.0.0
VS Code: 1.85.2 (8b3775030ed1a69b13e4f4c628c612102e30a681)
OS: Windows_NT x64 10.0.22631
Log:
The text was updated successfully, but these errors were encountered: