redhat-developer / redhat-developer/vscode-java

insufficient error logging for diagnostic

Open
#1,242 8 comments 0 reactions 1 assignee View on GitHub

@snjeza is already working on this.

Since Jan 17, 2020.

enhancement Lombok
Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
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?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.