redhat-developer / redhat-developer/vscode-java
insufficient error logging for diagnostic
@snjeza y travaille déjà.
Depuis le 17/1/2020.
- Langage dominant
- TypeScript
- Étoiles
- 2.3k
- Forks
- 546
- Merge moyen
- 20 h 1 min
- PR mergées (30 j)
- 11
Description
We are running this extension in Gitpod and users start reporting crashes with https://github.com/gitpod-io/gitpod/issues/1073 While trying to investigate we could not find any traces of the extension logging errors during the incident. It only helped to ask a user to enable verbose tracing.
Would it be possible to use Window.logMessage LSP api to log errors always? It would help with diagnostic, probably revealing the output view with an error in the case of a crash would be good too.
At the end a user figured out that an error was: Error opening zip file or JAR manifest missing : /tmp/vscode-extensions/GabrielBB.vscode-lombok@0.9.9/extension//server/lombok.jar
Although he does not seem to install such extension in the workspace: https://github.com/gitpod-io/gitpod/issues/1073#issuecomment-575138552
What could be the reason for that? Does java extension automatically expect lombok extension to be installed if a project makes use of lombok?
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Évaluation
Cette issue n'a pas encore été évaluée.