-
Notifications
You must be signed in to change notification settings - Fork 2
Uncaught TypeError: Cannot read property 'setEncoding' of undefined #10
Comments
Uh. My response would be pretty much the same as in atom-haskell-archive/haskell-ghc-mod#211... Frankly, I would suspect faulty RAM, but that's baseless conjecture of course. Also might be a bug in Atom, but don't quote me on that. I will point out that the error is thrown from the depths of Atom internals, so not much I could possibly do, even if I knew what. |
Just installed ide-haskell-hasktags, and having the same. Can the missing hasktags be the cause? |
@cblp, generally, you would expect something like this from missing Since the code base changed a lot since this was last reported, I would appreciate it if you'd provide a complete report. There's a clipboard icon on the big scary error message that should copy the Markdown-formatted report into the clipboard: |
[Enter steps to reproduce:]
Atom: 1.24.0 x64 Stack TraceUncaught TypeError: Cannot read property 'setEncoding' of undefined
Commands
Non-Core Packages
|
@cblp, thanks. It looks like process dies before Atom sets up event handlers... Which I honestly have no explanation for. So... I've released v0.0.14, which uses node's child_process directly without Atom's wrappers. Let's see if that helps. |
Steps to reproduce: no idea. I had a somewhat broken compilation cache (see atom-haskell-archive/haskell-ghc-mod#212) and I was issuing commands like
stack clean
. After I switched back to the Atom window, I had this error.Atom: 1.16.0 x64
Electron: 1.4.15
OS: "Manjaro Linux"
Thrown From: ide-haskell-hasktags package 0.0.10
Stack Trace
Uncaught TypeError: Cannot read property 'setEncoding' of undefined
Commands
Non-Core Packages
The text was updated successfully, but these errors were encountered: