redhat-developer / redhat-developer/vscode-java

Sometimes several objects are shown in red after a small change, saying it can not find the type

未关闭
#1,766 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

主要语言
TypeScript
星标
2.3k
派生
547
平均合并
20 小时 1 分钟
30 天内合并 PR
11

描述

[provide a description of the issue]

Environment
  • Operating System: Fedora 33
  • JDK version: 11.0.2
  • Visual Studio Code version: 1.52.1
  • Java extension version:
Steps To Reproduce
  1. [step 1]
    It doesn't happen always, but happens often. To change one type somewhere and that triggers something and shows lots of classes as not found.

https://user-images.githubusercontent.com/1836434/104616247-59fa8d00-568a-11eb-8a29-31159179c0d4.mp4

  1. [step 2]

[Please attach a sample project reproducing the error]
https://github.com/jonathanvila/windup-operator

Please attach logs
languag-server.log
Basically this is the error inside :
org.osgi.framework.BundleException: Exception in org.eclipse.lsp4mp.jdt.core.MicroProfileCorePlugin.stop() of bundle org.eclipse.lsp4mp.jdt.core. at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:891) at org.eclipse.osgi.internal.framework.EquinoxBundle.stopWorker0(EquinoxBundle.java:1025) at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.stopWorker(EquinoxBundle.java:370) at org.eclipse.osgi.container.Module.doStop(Module.java:660) at org.eclipse.osgi.container.Module.stop(Module.java:521) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1886) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1761) at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:275) at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:202) at org.eclipse.osgi.container.Module.doStop(Module.java:660) at org.eclipse.osgi.container.Module.stop(Module.java:521) at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:207) at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:220) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: java.lang.IllegalStateException: Workspace is closed. at org.eclipse.core.resources.ResourcesPlugin.getWorkspace(ResourcesPlugin.java:432) at org.eclipse.lsp4mp.jdt.internal.core.MicroProfilePropertiesListenerManager.destroy(MicroProfilePropertiesListenerManager.java:245) at org.eclipse.lsp4mp.jdt.core.MicroProfileCorePlugin.stop(MicroProfileCorePlugin.java:39) at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:871) at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) at java.base/java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:863) ... 13 more Root exception: java.lang.IllegalStateException: Workspace is closed.

Current Result
Expected Result
Additional Informations

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

从 windup-operator 示例项目开始,通过更改一个类型来复现问题,然后结合提供的视频检查 language-server.log。跟踪 Workspace is closed 异常,并验证进行小幅更改后类不再显示为缺失,同时记录报告中的环境以供比较。

由索引模型根据 Issue 内容生成。

评估

技术栈
java, typescript
领域
devtools
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。