Skip to content

Sometimes failed to restart the unsaved VS Code workspace #27

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.

Sign up for GitHub

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

Jump to bottom
Open
testforstephen opened this issue Oct 20, 2020 · 0 comments
Open

Sometimes failed to restart the unsaved VS Code workspace #27

testforstephen opened this issue Oct 20, 2020 · 0 comments

Comments

@testforstephen
Copy link
Owner

log.txt

Below is a piece of logs when restarting the unsaved workspace again.

!ENTRY org.eclipse.core.resources 2 10035 2020-10-20 11:10:11.172
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

!ENTRY org.apache.felix.scr 4 0 2020-10-20 11:10:14.061
!MESSAGE bundle org.apache.felix.scr:2.1.16.v20200110-1820 (9)Error while disposing components of bundle org.eclipse.core.resources:3.13.800.v20200706-2152 (21)
!STACK 0
java.lang.IllegalStateException: BundleContext is no longer valid org.eclipse.core.resources_3.13.800.v20200706-2152 [21]
...

A workaround is to clean Java language server workspace, or manually clean the directory "redhat.java/jdt_ws/.metadata/.plugins/org.eclipse.core.resources".
@testforstephen testforstephen changed the title Sometimes shutdown VS Code with unsaved changes and restart the project won't succeed Sometimes failed to restart the unsaved VS Code workspace Oct 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@testforstephen