Skip to content
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

Closing the IDE after a command line 'bazel clean --expunge' throws many errors #113

Closed
plaird opened this issue Apr 30, 2020 · 1 comment
Closed

Closing the IDE after a command line 'bazel clean --expunge' throws many errors #113

plaird opened this issue Apr 30, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@plaird
Copy link
Contributor

plaird commented Apr 30, 2020 •
edited
Loading

There are probably a number of ways to repro this, but here is one reliable set of steps:

  1. launch Eclipse with BEF
  2. import a Bazel workspace
  3. open up one of the projects in the Project Explorer and navigate down into the Bazel Classpath Container
  4. on the command line in the bazel workspace, 'bazel clean --expunge'
  5. without doing anything else in the IDE, try to close the IDE

It will take a long time because it will log a lot of information. The root issue is the files on disk have been removed, and our aspect/classpath caching has stale info, so the BazelClasspathContainer is annoyed.

Thread [ModalContext] (Suspended (breakpoint at line 535 in BazelClasspathContainer))
owns: BazelClasspathContainer (id=193)
BazelClasspathContainer.printDirectoryDiagnostics(File, String) line: 535
BazelClasspathContainer.getJarPathOnDisk(File, File, String) line: 499
BazelClasspathContainer.jarsToClasspathEntry(BazelWorkspace, WorkProgressMonitor, AspectOutputJarSet, boolean) line: 444
BazelClasspathContainer.getClasspathEntries() line: 226
JavaModelManager$VariablesAndContainersSaveHelper.saveContainers(IJavaProject, Map<IPath,IClasspathContainer>) line: 4569
JavaModelManager$VariablesAndContainersSaveHelper.saveProjects(IJavaProject[]) line: 4636
JavaModelManager$VariablesAndContainersSaveHelper.save(ISaveContext) line: 4477
JavaModelManager.saveVariablesAndContainers(ISaveContext) line: 4448
JavaModelManager.saving(ISaveContext) line: 4680
SaveManager.executeLifecycle(int, ISaveParticipant, SaveContext) line: 387
SaveManager$1.run() line: 204
SafeRunner.run(ISafeRunnable) line: 45
SaveManager.broadcastLifecycle(int, Map<String,SaveContext>, MultiStatus, IProgressMonitor) line: 207
SaveManager.save(int, boolean, Project, IProgressMonitor) line: 1164
Workspace.save(boolean, boolean, IProgressMonitor) line: 2338
IDEWorkbenchAdvisor.lambda$1(boolean, ProgressMonitorJobsDialog, MultiStatus, IProgressMonitor) line: 509
1519489617.run(IProgressMonitor) line: not available
ModalContext$ModalContextThread.run() line: 122
plaird added a commit that referenced this issue Apr 30, 2020
@plaird
limit the times diagnostics will be reported for #113
dcf62f2
@plaird plaird mentioned this issue Apr 30, 2020
Merged
plaird added a commit that referenced this issue Apr 30, 2020
@plaird
limit the times diagnostics will be reported for #113 (#114)
f5be81b
@plaird plaird added the bug Something isn't working label Apr 30, 2020
@plaird
Copy link
Contributor Author

plaird commented Oct 8, 2020

This was fixed by the same solution as #156

@plaird plaird closed this as completed Oct 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@plaird