-
Notifications
You must be signed in to change notification settings - Fork 385
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.
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
Getting NullPointerException in signatureHelp/codeAction/inlayHint requests when AST is not generated. #2608
Comments
Also triggers exceptions during inlayHint request:
codeAction request:
semanticHighlighting request:
|
Similar error when performing completion |
Basically, all calls to |
Added guards where needed whenever CoreASTProvider.getAST() is called. Fixes eclipse-jdtls#2608 and silences various errors logged when AST creation fails. Also see: eclipse-jdt/eclipse.jdt.core#317 Signed-off-by: Fred Bricon <fbricon@gmail.com>
So all those "IllegalArgumentException at org.eclipse.jdt.core.dom.InfixExpression.setOperator(InfixExpression.java:383)" are just polluting the logs, but are not crashes. |
Added guards where needed whenever CoreASTProvider.getAST() is called. Fixes eclipse-jdtls#2608 and silences various errors logged when AST creation fails. Also see: eclipse-jdt/eclipse.jdt.core#317 Signed-off-by: Fred Bricon <fbricon@gmail.com>
Added guards where needed whenever CoreASTProvider.getAST() is called. Fixes #2608 and silences various errors logged when AST creation fails. Also see: eclipse-jdt/eclipse.jdt.core#317 Signed-off-by: Fred Bricon <fbricon@gmail.com>
Issue
When there is a bug in user's code because of which AST can't be generated, then all the
textDocument/signatureHelp
requests are throwingNullPointerException
How to reproduce
textDocument/signatureHelp
request.Stack Trace
The text was updated successfully, but these errors were encountered: