-
Notifications
You must be signed in to change notification settings - Fork 5
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
Uncaught TypeError: Cannot read property 'locator' of null #13
Comments
|
Sorry Atom version is 1.13.0 After a start with |
@wader I've not been able to reproduce the error you are seeing so I'm closing this issue for now as you suggested. If you get the popup again, feel free to reopen it. |
@wndhydrnt ok! will do |
I just got this same issue. Here is the stack trace:
|
|
Please reopen. I encountered this behavior by clicking on an argument to Atom: 1.16.0 ia32 Stack TraceUncaught TypeError: Cannot read property 'locator' of null
Commands
Non-Core Packages
|
On this line, can you check for null and throw? That will help troubleshoot this issue, since clearly whatever is calling the constructor is somehow calling it without an argument. |
I'm getting this as well since upgrading to atom 1.17. |
^^ Same here |
Same issue using the latest version of go-plus and atom. Error pop-up while running a search in a particular file. Here is the stacktrace
|
The problem is that provided services are async, and their order is not guaranteed. If consumeStatusBar is called before consumeGoconfig, this.goconfig will be null. |
The consume functions can be called in any order. If consumeStatusBar is called before consumeGoconfig, the init code will throw an error. Fixes wndhydrnt#13, fixes wndhydrnt#16
Hi, after a atom packages update some days ago i get this red exception popup a lot:
When I check which version of go-plus that is installed in the packages list the version is "undefined".
Could it be some local config causing it?
The text was updated successfully, but these errors were encountered: