Platformio-atom-ide-terminal: Uncaught Error: channel closed

[aldaaga]

events.js:160

Doesn't let me you use terminal on Atom. What should I do? Anyone faced this problem before?

[AlfieDarko]

I got this problem today

[aldaaga]

anyone any suggestion how to work this out?

[EswarJ]

+1

[mrhBU67]

Same with me. I'm new to this so any help is appreciated.

[Sanil14]

same. How can i fix this.

[hellbenthorse]

I've also had the same error happen. Running Windows 10 x64. have tried in the 32 bit version of Atom and still the same problem persists.

I've also tried swapping default shell's from cmd to powershell and back to no avail.

Have installed/reinstalled C++ libraries, build tools etc and can't get around it at present.

Very interested in finding a fix for this.

[Lalit12289]

Same with me. I'm new to this so any help is appreciated.

[GeorgeBurac]

Same

[asadkamal]

Having the same issue. Really new to atom, so not sure what to do.

Thanks

[npabbisetty]

Seeing the same issue with Windows10 and Atom.

[hellbenthorse]

Update: I still get the error sometimes when opening a terminal in atom. However I've noticed ignoring the error the first couple of times and then when opening a new terminal if i begin typing in the terminal as soon as it initializes it will work. All future terminal instances in that atom session will also function without issue.

I don't have a fool proof way of replicating this at present as it seems to be random but random seldom is. I don't possess the technical knowledge presently to pin point it.

[thbui]

This issue come up again and again every time PlatformIO is updated.

[RayTimlin]

Having same problem in windows 10

[naziasc]

also having the same issue, is there a fix found for this issue

[EdgarDelaRosa]

Same 👎

[ShivaShankarPuvvada]

same here

[Freekdirkx]

same here

[MichFe]

Same issue, someone managed to solve it?

[concon121]

Resolved on my windows 10 box. Appears to be an issue with node-gyp building some native extensions for pty.js. Its a bit of a faff to fix, but here it is anyway:

1. Open up cmd.exe as admin
2. npm install --global --production windows-build-tools
3. Uninstall platformio-ide-terminal
4. Reboot PC
5. Reinstall platformio-ide-terminal
6. cd ~/.atom/packages/platformio-ide-terminal/node_modules/pty.js
7. node scripts\install.js

You should see in the terminal the native extensions being build correctly, it prints a lot of junk out to the console but you're looking for:

 Generating code
  Finished generating code
  pty.vcxproj -> C:\Users\<userid>\.atom\packages\platformio-ide-terminal\node_modules\pty.js\build\Release\\pty.node
  pty.vcxproj -> C:\Users\<userid>\.atom\packages\platformio-ide-terminal\node_modules\pty.js\build\Release\pty.pdb (Full PDB)

After that just restart atom and you're all set with a working terminal!

[erkobg]

Should be "npm install --global --production windows-build-tools" , right?

[concon121]

Yeah sorry I was half asleep when I wrote that, edited and updated my comment for future readers. Cheers!

[hellbenthorse]

@concon121 Thanks your wisdom mate, fixed it right up. Cheers!

[kmohan10]

Here is what worked for me:
Settings - Install Packages - Search for platformio-ide-terminal

Since the package is already installed, select 'Uninstall'.

Close Atom - Reopen Atom

Back to Install Packages and re-install platformio-ide-terminal

Hope it works to you as well. I am using Windows 7 (64-bit) system.

[erkobg]

Unfortunately for me any of these instructions don't work.
Windows 10 (64) ...
Any other ideas?

[concon121]

@erkobg do you get a stack trace or anything printed out to the developer console that could help us debug the issue?

[erkobg]

In the Dev Console I see:
events.js:106 A dynamic link library (DLL) initialization routine failed. \\?\C:\Users\MY_USER\.atom\packages\platformio-ide-terminal\node_modules\pty.js\build\Release\pty.node (anonymous) @ <embedded>:72772 (anonymous) @ <embedded>:72849 module.exports.Emitter.simpleDispatch @ <embedded>:64068 module.exports.Emitter.emit @ <embedded>:64184 (anonymous) @ <embedded>:72801 emitTwo @ events.js:106 emit @ events.js:191 process.nextTick @ internal/child_process.js:752 _combinedTickCallback @ internal/process/next_tick.js:67 _tickCallback @ internal/process/next_tick.js:98 events.js:106 Objectcode: "ENOENT"errno: -4058path: "C:\Users\MY_USER\.atom\packages\platformio-ide-terminal\node_modules\pty.js\bin\win32\x64_m53\pty.node.bak"syscall: "lstat"__proto__: Object (anonymous) @ <embedded>:72775 (anonymous) @ <embedded>:72849 module.exports.Emitter.simpleDispatch @ <embedded>:64068 module.exports.Emitter.emit @ <embedded>:64184 (anonymous) @ <embedded>:72801 emitTwo @ events.js:106 emit @ events.js:191 process.nextTick @ internal/child_process.js:752 _combinedTickCallback @ internal/process/next_tick.js:67 _tickCallback @ internal/process/next_tick.js:98

[surajgampa]

@concon121 Of your 7 step solution, after step 5, I still get the same error in the terminal and I'm not able to run the 6th and 7th step in it (doesn't allow to enter any text). Kindly help. Mine is a Windows 10 (64).

[h3rmanj]

Got this error when on W10 1703, upgrading to 1709 seems to have fixed it.

[abhirathod07]

I've got the same error, can anyone help please...

Error: channel closed
at ChildProcess.target.send (internal/child_process.js:548:16)

[lffg]

Same. Bump.

[antonapua]

same.

[1985michel]

me too W10 64

[erkobg]

Hello,
Windows 10 64 here.
after checking the referenced issue https://github.com/jeremyramin/terminal-plus/issues/280
I was able to fix the issue by doing following :

1. Closed PlatformIO
2. Open CMD
3. Navigate to C:\Users\USERNAME\.atom\packages\platformio-ide-terminal (eg. CD C:\Users\USERNAME\.atom\packages\platformio-ide-terminal )
4. type npm install and wait to complete
5. type apm rebuild and wait to complete
6. Start PlatformIO
7. Try any Serial Monitor or "Upgrade platforms, packages and libraries"
   ( it can give the same error first time, ignore and start Serial Monitor or "Upgrade platforms, packages and libraries" again, second time)

Hope this helps.

[collins73]

Same issue here..

[ElecTreeFrying]

for windows

run atom as administrator
close atom
then run atom normally not as an administrator

[daev3]

Did anyone manage to run it properly? I tried but wasn't able to run it on Atom. I use Windows 10.

I tried the npm install (...) but my prompt didn't reconize it

[edivaldodelgado]

@Barenco I was able to do what @erkobg did and it worked. You have to install node.js first.

[https://nodejs.org/en/]

After that, try the steps again.

[erkobg]

Well, testing from a long time so far ... issue tends to come over and over again.... it is really annoying ... I used to ignore it somehow so far but in long term it would be better if they fix the issue from the root...

[edivaldodelgado]

@erkobg that's true. In fact, I had some troubles with conda virtual environments after, then I decide to use cmd itself, in another windows.

[daev3]

@edivaldodelgado indeed it work! Thank you guys!

[Rayongice]

I have a "Uncaught Error: channel closed"
event.js.160
my OS is win 10

[buttrs2013]

also having this error, have followed all the various instructions in this thread but to no avail. does anyone have any other ideas?

[the-j0k3r]

Please retest again with platformio-atom-ide-terminal 2.9.0 is using node-pty-prebuilt instead unmaintained and outdated pty.js