-
Notifications
You must be signed in to change notification settings - Fork 408
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
Outgoing calls hierarchies runs into NullPointerException if hashCode() is called #3192
Comments
I think it would have helped if you'd provided the options provided in initialize message. I solved this problem in my case by adding various options to init message:
|
In my case it was caused by the JLS trying to resolve a reference into the Java Standard Library that it couldn't find. Probably for you too finding Object::hashCode. |
I have posted the entire log of messages exchanged between my client and JDT. Specifically the options were:
That does seem to be the case, but I don't see what I've done wrong. |
The error regarding Closing this for now as the error mentioned should be fixed. You could try https://download.eclipse.org/jdtls/snapshots/jdt-language-server-latest.tar.gz for the latest version. We also plan to release by the end of this week. |
With the code above and a request for outgoing calls from the constructor, JDT returns "Internal error" status.
Here's the JDT log:
The JDT stderr:
And here are the exchanged messages from from the client's point of view:
The text was updated successfully, but these errors were encountered: