Skip to content
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

ApexIndexer throwing NullPointerException #581

Closed
PhilippOrtnerUp2Go opened this issue Aug 21, 2018 · 3 comments
Closed

ApexIndexer throwing NullPointerException #581

PhilippOrtnerUp2Go opened this issue Aug 21, 2018 · 3 comments

Comments

@PhilippOrtnerUp2Go
Copy link

Summary

When starting VSCode in a valid folder with a sfdx-config.json I am missing most of the LS features since I can observe an error in the output of the Apex Language Server in the output window.

Other features such as Debugging or the CLI plugin work perfectly fine.

Steps To Reproduce:

  1. Open sfdx-config.json containing folder (connection and CLI works in this folder).
  2. Observe output window of Apex Language Server.

Expected result

Full LS features / no errors.

Actual result

Multiple of these NullPointerExceptions:

[ApexIndexer STARTING] ERROR a.jorje.lsp.impl.index.ApexIndexer - exception thrown in traversing codeunit for references
java.lang.NullPointerException: null

Additional information

apex-ls.log

VS Code Version:

1.26.1

SFDX CLI Version:

sfdx-cli/6.29.0 (linux-x64) node-v10.6.0

OS and version:

Ubuntu 16.04 LTS
4.15.0-32-generic

@vazexqi
Copy link
Contributor

vazexqi commented Aug 21, 2018

@PhilippOrtnerUp2Go - Are you able to open up a support case – once you do that reference this bug and tell them to assign it to Nick Chen (Platform Dev Tools)? If we can take a look at the code it would help. This seems very specific to what you have in your code base.

If you can't do that then we need to put more logging in or we need to have some other way to get access to the code (if that is possible).

@PhilippOrtnerUp2Go
Copy link
Author

Thanks for the quick reply @vazexqi .

Seems to be similar to issue #388 which was solved.

If you need any other logging info or want me to test something I'll happily help you.

Will look into opening a support case, need to talk to my supervisors, also not really sure about looking at the code at the moment.

@vazexqi
Copy link
Contributor

vazexqi commented Aug 24, 2018

Duplicate of #587.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants