Hyper: Opening a new tab throws an uncaught exception

[cfjedimaster]

• [x ] I am on the latest Hyper.app version
• [ x] I have searched the issues of this repo and believe that this is not a duplicate

• OS version and name: Windows 10
• Hyper.app version: 1.4.3
• Link of a Gist with the contents of your .hyper.js: https://gist.github.com/cfjedimaster/7cfe0d2e70ae217c6e06eaf32e545a79
• Relevant information from devtools N/A
• The issue is reproducible in vanilla Hyper.app: No, and also not reproducible w/ plugins installed. It appears as if it was a one time event, but I wanted it logged in case I run into again.

Issue

Opening a new tab threw this error:

A JavaScript error occurred in the main process

[Content]
Uncaught Exception:
Error: Unable to start terminal process: CreateProcess failed
at new WindowsPtyAgent (C:\Users\ray\AppData\Local\hyper\app-1.4.3\resources\app.asar\node_modules\node-pty\lib\windowsPtyAgent.js:25:24)
at new WindowsTerminal (C:\Users\ray\AppData\Local\hyper\app-1.4.3\resources\app.asar\node_modules\node-pty\lib\windowsTerminal.js:45:24)
at spawn (C:\Users\ray\AppData\Local\hyper\app-1.4.3\resources\app.asar\node_modules\node-pty\lib\index.js:26:12)
at Session (C:\Users\ray\AppData\Local\hyper\app-1.4.3\resources\app.asar\session.js:45:18)
at initSession (C:\Users\ray\AppData\Local\hyper\app-1.4.3\resources\app.asar\ui\window.js:90:23)
at Server.Window.rpc.on.options (C:\Users\ray\AppData\Local\hyper\app-1.4.3\resources\app.asar\ui\window.js:93:7)
at emitOne (events.js:96:13)
at Server.emit (events.js:191:7)
at Server.ipcListener (C:\Users\ray\AppData\Local\hyper\app-1.4.3\resources\app.asar\rpc.js:34:11)
at emitTwo (events.js:106:13)
at EventEmitter.emit (events.js:194:7)

[chabou]

Thanks for your feedback

[Mohamed3on]

This happens with some Hyper windows for me too, but only when I open Hyper in a directory, instead of the default directory. I'm using Hyper 1.4.3 on Windows 10 with oh-my-zsh (Zsh on Bash on Windows) and I can't open any new tabs with that setup. Using cmd as a shell doesn't have the same issue though.
Update : Adding -p to the registry command solved it for me, as per this comment.

[cfjedimaster]

And it is back for me now too.

[chabou]

@cfjedimaster can you confirm that was due to open Hyper in a directory instead of the default directory ?

[cfjedimaster]

I'm away from the machine where the issue is cropping up, but do you mean - what directory I was in currently in the active tab? Or where I opened Hyper? If the later, I opened it via the Start menu.

[Mohamed3on]

So, adding -p to the registry command makes 'Open Hyper here' always open in the default directory, so it's not really a fix.

[Mohamed3on]

The error message for me is quite similar:

A JavaScript error occurred in the main process

Uncaught Exception:
Error: Unable to start terminal process: CreateProcess failed
    at new WindowsPtyAgent (C:\Users\Mohamed\AppData\Local\hyper\app-1.4.3\resources\app.asar\node_modules\node-pty\lib\windowsPtyAgent.js:25:24)
    at new WindowsTerminal (C:\Users\Mohamed\AppData\Local\hyper\app-1.4.3\resources\app.asar\node_modules\node-pty\lib\windowsTerminal.js:45:24)
    at spawn (C:\Users\Mohamed\AppData\Local\hyper\app-1.4.3\resources\app.asar\node_modules\node-pty\lib\index.js:26:12)
    at Session (C:\Users\Mohamed\AppData\Local\hyper\app-1.4.3\resources\app.asar\session.js:45:18)
    at initSession (C:\Users\Mohamed\AppData\Local\hyper\app-1.4.3\resources\app.asar\ui\window.js:90:23)
    at Server.Window.rpc.on.options (C:\Users\Mohamed\AppData\Local\hyper\app-1.4.3\resources\app.asar\ui\window.js:93:7)
    at emitOne (events.js:96:13)
    at Server.emit (events.js:191:7)
    at Server.ipcListener (C:\Users\Mohamed\AppData\Local\hyper\app-1.4.3\resources\app.asar\rpc.js:34:11)
    at emitTwo (events.js:106:13)
    at EventEmitter.emit (events.js:194:7)

Setup and reproduction:
Hyper 1.4.3
Windows 10
Bash on Windows as shell (with zsh)
Open hyper in directory then open a new tab.

[pattacini]

I'm having the same problem here on my system with the same configurations as yours.

[Mohamed3on]

Update: The issue just happened to me with a cmd shell that's been open for a while too, and I had to close/reopen it.

[cakenggt]

This is also happening with me. Same error message and trace as above.

Setup and reproduction:
Hyper 1.4.4
Windows 7 Professional
Empty shell property in .hyper.js with ['--login'] as shellArgs
Open hyper from start menu

[johnwebbcole]

Getting the same error when trying to split the view or open a new tab:

  Hyper 1.4.4
  Electron 1.7.6
  win32 x64 10.0.15063

My shell is git-bash

[nomad3k]

I was just about to report this issue. I can reliably reproduce it using mocha. If I have a tab that's running mocha --compilers js:babel-core/register src/**/*.test.js --watch --growl. Then when I click Split Horizontally I get the very same exception as @johnwebbcole above.

[luukverhoeven]

When opening a new tab from menu or shortcut this error is thrown

Microsoft Windows 10 Pro 10.0.15063 Build 15063

[johnwebbcole]

After @nomad3k mentioned it, I've noticed that this only happens after running a npm script.

Trying to narrow it down, whenever I run my development build npm run dev or build for production, this happens. Since I'm building a large Vue app, this doesn't narrow it down, so I tried some simpler commands.

Here are steps to reproduce:

• open hyper, create a new tab or split the view - it works
• install vue-cli npm install -g vue-cli
• open a new tab or split the view - it fails

If you already have vue-cli installed, reproduce this way:

• open hyper, create a new tab or split the view - it works
• vue init simple somenewproject
• cd somenewproject
• npm i
• create a new tab or split the view - it fails

I'm sure there are other things that trigger it, as @nomad3k used mocha, but these are my steps to reproduce on Windows 10.

[Mohamed3on]

The error is still present in 1.4.8.

[MartinMuzatko]

Yep. Happens with new tab, splits etc.

[MartinMuzatko]

I got some more information.
After resetting my .zshrc and .hyper.js file, everything works fine!
I think the SSH-agent was the problem.

[Mohamed3on]

@MartinMuzatko Hmm, but the error happens even if I use CMD as the shell.

[MartinMuzatko]

Now the problem only happens when splitting while running an NPM command or after that.

[Mystilund]

I doesn't happen when it's a new window but if I do something in the term, I always have the error if I want to split vertically / open a new tab.
It's very annoying, it should be a priority imo, but it's been more than a month now :(

[pattacini]

I agree it's somewhat annoying. Tabbing and splitting are practically unusable.
I was enthusiastic to leave Console2 in favor of hyper on my Windows and I'm trying hard to resist the urge to go back in the hope that this bug will be sorted out very soon 😉

[cakenggt]

I don't use npm commands very often at all, and it happens to me if I try to make a new tab when the hyper console opens (it opens at my C:\Users\username folder). However, if I cd into another directory, I can make a new tab. Additionally, if I run a .bat script, I can't create a new tab anymore.

[Radiergummi]

After taking some hints from the comments, I removed the hypercwd plugin which seems to have solved this issue for me.

[pattacini]

@Radiergummi that's correct; removing hypercwd worked also for me.

[cfjedimaster]

Seems to work for me too. Still needs an official fix imo.

[johnwebbcole]

Same here, removing hypercwd fixes it

[lsuarez-tiempo-dev]

I really wanted this to work , Hope it get's fixed soon .
I'm not sure what adding -p to the registry means. could somebody elaborate please?

[ivictbor]

Just installed fresh hyper. Opening new tab was working for me before I added hypercwd. Now it shows mentioned error.

[janat08]

how to remove hypercwd?

[Stanzilla]

@janat08 remove it from your .hyper.js plugins section

[janat08]

would be nice if they would've reversed the deletion/comment once fixing it.

[imdario]

Confirmed, it's hypercwd's fault if you create a new tab while connected to a remote SSH server (at least, for me).

@janat08 (and anyone who stumbles on this issue while looking for the error): type hyper u hypercwd in your hyper shell and it will be gone.

[franciscobern]

Perfect "hypercwd" removed, fixes it.

[dazrave]

Removing hypercwd worked for me also.

[Radiergummi]

Would everyone mind just using the +1 reaction instead of adding new "me too" comments? There's a lot of people involved in this thread that get useless notifications while they wait for an official fix. Thanks guys.

[giggio]

This is the related hypercwd error: https://github.com/hharnisc/hypercwd/issues/51
This issue should be closed and locked. There is nothing else to do here.