Uncaught TypeError: Cannot read property 'process' of null #5

tmm1 · 2015-09-28T19:38:04Z

Atom Version: 1.0.19
System: Mac OS X 10.11
Thrown From: nim package, v0.3.0

Stack Trace

Uncaught TypeError: Cannot read property 'process' of null

At /Users/tmm1/.atom/packages/nim/lib/persistent-caas.coffee:33

TypeError: Cannot read property 'process' of null
  at /Users/tmm1/.atom/packages/nim/lib/persistent-caas.coffee:33:19
  at FSReqWrap.oncomplete (fs.js:82:15)

Commands

     -0:40.5.0 vim-mode:undo (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  2x -0:40 vim-mode:move-up (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:39 vim-mode:put-before (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:38.3.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
 11x -0:38.2.0 vim-mode:move-right (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  2x -0:37.6.0 vim-mode:move-up (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:36.7.0 vim-mode:move-to-previous-word (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:35.6.0 vim-mode:change (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:35.5.0 vim-mode:move-to-next-word (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
     -0:34.8.0 vim-mode:activate-normal-mode (atom-text-editor.editor.vim-mode.is-focused.insert-mode)
     -0:34.5.0 core:save (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  2x -0:33.9.0 blur (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:05.0 vim-mode:undo (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:03.4.0 core:save (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  2x -0:03.0 vim-mode:undo (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:01.8.0 core:save (atom-text-editor.editor.vim-mode.normal-mode.is-focused)

Config

{
  "core": {
    "disabledPackages": [
      "terminal",
      "git-plus",
      "atomatigit",
      "term2",
      "language-nim"
    ],
    "themes": [
      "one-dark-ui",
      "atom-dark-syntax"
    ]
  },
  "nim": {
    "nimExecutablePath": "/usr/local/bin/nim",
    "nimsuggestEnabled": true,
    "nimsuggestExecutablePath": "~/.nimble/bin/nimsuggest"
  }
}

Installed Packages

# User
autocomplete-clang, v0.8.7
autocomplete-emojis, v2.2.2
color-picker, v2.0.12
ex-mode, v0.7.0
git, v0.0.0
go-plus, v3.5.1
language-puppet, v0.14.0
language-rust, v0.4.5
linter, v1.6.0
linter-rust, v0.2.9
minimap, v4.13.4
minimap-git-diff, v4.1.8
minimap-hide, v0.3.0
nim, v0.3.0
racer, v0.17.2
remote-atom, v1.2.7
rust-api-docs-helper, v0.5.1
script, v2.29.0
vim-mode, v0.60.0

# Dev
No dev packages

The text was updated successfully, but these errors were encountered:

tmm1 · 2015-09-28T19:50:13Z

Seeing these as well:

Stack Trace

Uncaught Error: This socket has been ended by the other party

At events.js:141

Error: This socket has been ended by the other party
  at Socket.writeAfterFIN [as write] (net.js:266:12)
  at /Users/tmm1/.atom/packages/nim/lib/persistent-caas.coffee:33:34
  at FSReqWrap.oncomplete (fs.js:82:15)

russpowers · 2015-09-28T23:53:50Z

Thanks for the report. It looks like nimsuggest is crashing, which happens a lot, but it's not being handled properly... I'm not able to reproduce this, can you check the javascript console for errors and copy/paste them here?

ghost · 2015-09-29T08:01:43Z

persistent-caas.coffee:72 Nimsuggest crashed...
events.js:141 Uncaught Error: read ECONNRESET
persistent-caas.coffee:72 Nimsuggest crashed...
events.js:141 Uncaught Error: read ECONNRESET
persistent-caas.coffee:72 Nimsuggest crashed...
events.js:141 Uncaught Error: read ECONNRESET
persistent-caas.coffee:72 Nimsuggest crashed...
executor.coffee:68 ERROR: Command failed multiple times.
Command:
SUGGESTIONS: /src/nim/test.nim,8,8
Output:
Traceback (most recent call last)
nimsuggest.nim(355)      nimsuggest
nimsuggest.nim(336)      handleCmdLine
Error: unhandled exception: Cannot find Nim standard library: Nim compiler not in PATH [IOError]

russpowers · 2015-09-29T19:36:15Z

Ok, there was an issue with timing on some of the error handling related to temp files. That should be fixed now, although I can't verify it since I couldn't replicate the error. I'll leave this open, please let me know if either of you see that same null error anymore.

ghost · 2015-09-30T07:01:24Z

Uncaught Error: read ECONNRESET
persistent-caas.coffee:74 Nimsuggest crashed...
events.js:141 Uncaught Error: read ECONNRESET
persistent-caas.coffee:74 Nimsuggest crashed...
events.js:141 Uncaught Error: read ECONNRESET
persistent-caas.coffee:74 Nimsuggest crashed...
events.js:141 Uncaught Error: read ECONNRESET
persistent-caas.coffee:74 Nimsuggest crashed...
executor.coffee:68 ERROR: Command failed multiple times.
Command:
SUGGESTIONS: /home/user/src/nim/project/test.nim,2,2
Output:
Error: cannot open '/home/user/src/nim/lib/system.nim'
Traceback (most recent call last)
nimsuggest.nim(355)      nimsuggest
nimsuggest.nim(345)      handleCmdLine
nimsuggest.nim(281)      mainCommand
modules.nim(205)         compileProject
modules.nim(188)         compileSystemModule
modules.nim(158)         compileModule
modules.nim(66)          doCRC
securehash.nim(22)       secureHashFile
sysio.nim(192)           readFile
system.nim(2537)         sysFatal
Error: unhandled exception: cannot open: /home/user/src/nim/lib/system.nim [IOError]

Problem is it looks for stdlib in wrong dir.

~ % whereis nim
nim: /home/user/src/nim/Nim/bin/nim

And stdlib is in /home/user/src/nim/Nim/lib.

russpowers · 2015-09-30T07:56:45Z

This looks like an internal problem with nimsuggest... It's crashing because it can't find a file.

tmm1 · 2015-09-30T21:57:12Z

I'm having a similar issue, I have nimsuggest installed in ~/.nimble/bin and its unable to find system.nim:

SUGGESTIONS: /Users/tmm1/code/nim/compiler/pragmas.nim,848,68
Output:
Error: cannot open '/Users/tmm1/.nimble/pkgs/lib/system.nim'
Error: unhandled exception: cannot open: /Users/tmm1/.nimble/pkgs/lib/system.nim [IOError]

708 console messages are not shown.

tmm1 · 2015-09-30T21:59:57Z

In another project it's trying to access /usr/local/lib/system.nim when using /usr/local/bin/nim

ERROR: Command failed multiple times.
Command:
DEFINITION: /Users/tmm1/code/c2nim/postprocessor.nim,19,18
Output:
Error: cannot open '/usr/local/lib/nim/system.nim'
Error: unhandled exception: cannot open: /usr/local/lib/nim/system.nim [IOError]

russpowers · 2015-10-01T01:22:40Z

I've been reading through the issues over at nimsuggest, and it looks like there are sometimes problems locating the nim library folder. The solution is either to move the nimsuggest executable into the nim bin folder or to explicitly set the lib path via the --lib nim compiler option. I've added a config key Nim Lib Path where you can set that library path. Try it out and let me know how it goes.

ghost · 2015-10-01T07:39:28Z

This helps, thanks!

yglukhov · 2016-01-12T11:05:32Z

I'm still hitting this issue occasionaly even though I have set lib path :(
Edit: tightly related to #7

russpowers · 2016-01-13T06:24:47Z

Nimsuggest crashes constantly, especially if a macro is involved (if the macro evaluation crashes, nimsuggest crashes)... I've tried to write code that handles those crashes gracefully, but there must still be a problem there somewhere. I'll take a look.

yglukhov · 2016-04-07T19:42:36Z

@russpowers, fyi, i'm still experiencing this problem occasionally:
stack:

TypeError: Cannot read property 'process' of null
    at /Users/yglukhov/.atom/packages/nim/lib/persistent-caas.coffee:35:19
    at /Applications/Atom.app/Contents/Resources/app.asar/node_modules/babel-core/node_modules/regenerator/node_modules/commoner/node_modules/graceful-fs/graceful-fs.js:43:10
    at FSReqWrap.oncomplete (fs.js:82:15)

russpowers · 2016-04-13T06:16:32Z

Thanks for the report @yglukhov. Sorry I haven't been able to fix this yet, been very busy on other projects. I will try to set aside some time to see if I can figure out what is causing this...

singularperturbation · 2016-05-24T03:37:59Z

I was able to look in dev tools and see that this was because nimsuggest itself was not finding the Nim compiler when the editor was started (though I had the full path in my package settings). I was able to work around by starting atom from a terminal with the $PATH set correctly.

I'll see if I can make a fix for this (by mutating the $PATH when starting nimsuggest).

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uncaught TypeError: Cannot read property 'process' of null #5

Uncaught TypeError: Cannot read property 'process' of null #5

tmm1 commented Sep 28, 2015

tmm1 commented Sep 28, 2015

russpowers commented Sep 28, 2015

ghost commented Sep 29, 2015

russpowers commented Sep 29, 2015

ghost commented Sep 30, 2015

russpowers commented Sep 30, 2015

tmm1 commented Sep 30, 2015

tmm1 commented Sep 30, 2015

russpowers commented Oct 1, 2015

ghost commented Oct 1, 2015

yglukhov commented Jan 12, 2016

russpowers commented Jan 13, 2016

yglukhov commented Apr 7, 2016

russpowers commented Apr 13, 2016

singularperturbation commented May 24, 2016

Uncaught TypeError: Cannot read property 'process' of null #5

Uncaught TypeError: Cannot read property 'process' of null #5

Comments

tmm1 commented Sep 28, 2015

Stack Trace

Commands

Config

Installed Packages

tmm1 commented Sep 28, 2015

Stack Trace

russpowers commented Sep 28, 2015

ghost commented Sep 29, 2015

russpowers commented Sep 29, 2015

ghost commented Sep 30, 2015

russpowers commented Sep 30, 2015

tmm1 commented Sep 30, 2015

tmm1 commented Sep 30, 2015

russpowers commented Oct 1, 2015

ghost commented Oct 1, 2015

yglukhov commented Jan 12, 2016

russpowers commented Jan 13, 2016

yglukhov commented Apr 7, 2016

russpowers commented Apr 13, 2016

singularperturbation commented May 24, 2016