redhat-developer / redhat-developer/vscode-java
Autocompletion doesn't work well within lambda expressions
Nessuno ha ancora preso questa issue.
- Lingua principale
- TypeScript
- Stelle
- 2.3k
- Fork
- 546
- Merge medio
- 20h 1m
- PR unite (30g)
- 11
Descrizione
Issue Type: Bug
[Error - 7:12:19 PM] Feb 17, 2022, 7:12:19 PM Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
java.lang.IllegalArgumentException:
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:66)
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:50)
at org.eclipse.core.internal.jobs.JobManager.setRule(JobManager.java:1400)
at org.eclipse.core.internal.jobs.InternalJob.setRule(InternalJob.java:486)
at org.eclipse.core.runtime.jobs.Job.setRule(Job.java:771)
at org.eclipse.jdt.ls.core.internal.handlers.BaseDocumentLifeCycleHandler.triggerValidation(BaseDocumentLifeCycleHandler.java:154)
at org.eclipse.jdt.ls.core.internal.handlers.BaseDocumentLifeCycleHandler.triggerValidation(BaseDocumentLifeCycleHandler.java:138)
at org.eclipse.jdt.ls.core.internal.handlers.WorkspaceDiagnosticsHandler.visit(WorkspaceDiagnosticsHandler.java:180)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:67)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:51)
at org.eclipse.jdt.ls.core.internal.handlers.WorkspaceDiagnosticsHandler.resourceChanged(WorkspaceDiagnosticsHandler.java:103)
at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:305)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:295)
at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:158)
at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:381)
at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1503)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2327)
at org.eclipse.core.internal.events.NotificationManager$NotifyJob.run(NotificationManager.java:44)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Extension version: 1.3.0
VS Code version: Code 1.64.2 (f80445acd5a3dadef24aa209168452a3d97cc326, 2022-02-09T22:02:28.252Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz (8 x 2304) |
| GPU Status | 2d_canvas: unavailable_software gpu_compositing: disabled_software multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: disabled_off rasterization: disabled_software skia_renderer: enabled_on video_decode: disabled_software vulkan: disabled_off webgl: unavailable_software webgl2: unavailable_software |
| Load (avg) | undefined |
| Memory (System) | 31.73GB (16.09GB free) |
| Process Argv | --disable-gpu --disable-gpu-compositing --log error |
| Screen Reader | no |
| VM | 0% |
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia riproducendo il completamento automatico Java all’interno di un’espressione lambda, quindi esamina il percorso segnalato attraverso BaseDocumentLifeCycleHandler e WorkspaceDiagnosticsHandler. Il lavoro è completato quando il completamento funziona nel contesto lambda senza la IllegalArgumentException segnalata durante la validazione.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java, typescript, vscode
- Ambito
- developer-experience, tooling
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 30/100