Change:
Issue Type: <bBug</bI have been seeing hangs happen on and off since 1.33 was in insiders, but never pinpointed anything. And while I still haven't pinpointed anything the frequency has increased (even at the very end of 1.33). I have noticed that the hangs very often coincide with kicking off a task (usually it is a compound task). How best can I help capture information to get to the bottom of it? When it happens the window is hung completely so I can't open devtools or anything like that. VS Code version: Code - Insiders 1.34.0-insider (, 2019-04-08T05:19:58.162Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<!-- generated by issue reporter --
Can you check the Process Explorer? Also see
Unfortunately it hangs completely -- I can't do anything until it hangs for long enough and I get the , dialog.
I haven't seen any hangs in 1.33 so I don't have any ideas about what might be causing it. If it's happening that often, can you keep the dev tools open and try to quickly grab a trace next time it freezes? I will try running compound tasks periodically to see if I can make it happen.
I was able to get it to hang again with the devtools open !
Thanks for getting the stack trace! any chance you remember what was happening when the hang occured? looks like this is happening in the terminal.
It usually seems to happen during the following workflow: to open the build task menu (since I have multiple build tasks) Pick the composite task below, which kicks off 2 terminals (split) Some time passes Kill both terminals by using the trash can icon Rinse & repeat Here is my
This is happening for me with no special build workflow, just using the integrated terminal to run miscellaneous scripts. Somewhat of a showstopper for someone that uses the integrated terminal heavily.
I'm having trouble reproducing this via launching 2 tasks in a split terminal, any more details on a repro? FYI the get console process list error in should be harmless.
it often takes me a bunch of times trying it, but I can get it to reproduce pretty reliably. I'm using today's insiders () and my terminal shell is powershell core v6.2.0. Here are my terminal settings if that helps any: I also noticed that it seems more reproducible when there is an existing terminal to the mix: Open a terminal (if one isn't already opened) Ctrl+Shift+B to open the build task menu (since I have multiple build tasks) Pick the composite watch task below, which kicks off 2 terminals (split) Kill both terminals by using the trash can icon Sometimes kill the existing terminal with the trash can icon Rinse & repeat I've reproduced it as quickly as 3 iterations of this loop, but sometimes it is more like 6-10 times. EDIT: I've also reproduced this many times with and without all extensions disabled
Tried with those settings about 30-40 times and couldn't get it to happen. Does running in a extenral command prompt work when this is happening?
It seems to work:
told me less than I was hoping
Is there anything else I can do to help? Not sure how to really debug this. I can screenshare or something if that helps too
Since yesterday I've been seeing the same hangs, but now by just running my GitLens pack command in the terminal () without any of the split terminal stuff or anything special (no opening or closing terminals either). It seems to hang when my pack script calls out to . Since yesterday, its happened about 6 times.
Now I've seen it a few more times just running from within the terminal.
I logging to every call in the terminal that goes out to native code. After the next insiders build goes out (1.35.0-insiders), for those seeing the issues could you: Set the log level (via F1) to "trace" Trigger the crash Find the renderer log file, this is near your settings file, for Windows it should look something like this: There should be "IPty#..." logs towards the bottom, the last few of those is what I'm interested in. If you can trigger a few times and check the log file to see if it's the same that would also be useful.
FYI if you're hitting this you can workaround is by disabling the conpty backend in settings:
Terminal hangs and gives me this. Other terminals and editors are working fine. <details<pre[uncaught exception]: TypeError: Cannot read property 'copyCellsFrom' of undefined onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- /usr/share/code/resources/app/out/bootstrap- TypeError: Cannot read property 'copyCellsFrom' of undefined at Buffer.reflowSmaller () at () at () at () at () at () at e.resize () at (/usr/share/code/resources/app/out/vs/code/electron-browser/workbench/anonymous function).setTimeout () onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- Uncaught TypeError: Cannot read property 'copyCellsFrom' of undefined at Buffer.reflowSmaller () at () at () at () at () at () at e.resize () at (/usr/share/code/resources/app/out/vs/code/electron-browser/workbench/anonymous function).setTimeout () /usr/share/code/resources/app/out/bootstrap- [uncaught exception]: TypeError: Cannot read property 'get' of undefined onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- /usr/share/code/resources/app/out/bootstrap- TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- Uncaught TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at /usr/share/code/resources/app/out/bootstrap- [uncaught exception]: TypeError: Cannot read property 'set' of undefined onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- /usr/share/code/resources/app/out/bootstrap- TypeError: Cannot read property 'set' of undefined at () at EscapeSequenceParser.printHandler () at () at () at Terminal.innerWrite () at onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- Uncaught TypeError: Cannot read property 'set' of undefined at () at EscapeSequenceParser.printHandler () at () at () at Terminal.innerWrite () at /usr/share/code/resources/app/out/bootstrap- [uncaught exception]: TypeError: Cannot read property 'get' of undefined onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- /usr/share/code/resources/app/out/bootstrap- TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- Uncaught TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at /usr/share/code/resources/app/out/bootstrap- [uncaught exception]: TypeError: Cannot read property 'get' of undefined onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- /usr/share/code/resources/app/out/bootstrap- TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- Uncaught TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at /usr/share/code/resources/app/out/bootstrap- [uncaught exception]: TypeError: Cannot read property 'get' of undefined onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- /usr/share/code/resources/app/out/bootstrap- TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- Uncaught TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at /usr/share/code/resources/app/out/bootstrap- [uncaught exception]: TypeError: Cannot read property 'get' of undefined onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- /usr/share/code/resources/app/out/bootstrap- TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- Uncaught TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at /usr/share/code/resources/app/out/bootstrap- [uncaught exception]: TypeError: Cannot read property 'get' of undefined onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- /usr/share/code/resources/app/out/bootstrap- TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- Uncaught TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at /usr/share/code/resources/app/out/bootstrap- [uncaught exception]: TypeError: Cannot read property 'get' of undefined onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- /usr/share/code/resources/app/out/bootstrap- TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- Uncaught TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at /usr/share/code/resources/app/out/bootstrap- [uncaught exception]: TypeError: Cannot read property 'get' of undefined onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- /usr/share/code/resources/app/out/bootstrap- TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- Uncaught TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at /usr/share/code/resources/app/out/bootstrap- [uncaught exception]: TypeError: Cannot read property 'get' of undefined onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- /usr/share/code/resources/app/out/bootstrap- TypeError: Cannot read property 'get' of undefined at TextRenderLayer.forEachCell () at TextRenderLayer.drawBackground () at TextRenderLayer.onGridChanged () at at Array.forEach (<anonymous) at Renderer.renderRows () at RenderDebouncer.innerRefresh () at onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- Uncaught TypeError: Cannot read property 'get' of undefined at TextRenderLayer.forEachCell () at TextRenderLayer.drawBackground () at TextRenderLayer.onGridChanged () at at Array.forEach (<anonymous) at Renderer.renderRows () at RenderDebouncer.innerRefresh () at /usr/share/code/resources/app/out/bootstrap- [uncaught exception]: TypeError: Cannot read property 'get' of undefined onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- /usr/share/code/resources/app/out/bootstrap- TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- Uncaught TypeError: Cannot read property 'get' of undefined at () at CursorBlinkStateManager.renderCallback () at /usr/share/code/resources/app/out/bootstrap- [uncaught exception]: TypeError: Cannot read property 'copyCellsFrom' of undefined onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- /usr/share/code/resources/app/out/bootstrap- TypeError: Cannot read property 'copyCellsFrom' of undefined at Buffer.reflowSmaller () at () at () at () at () at () at e.resize () at (/usr/share/code/resources/app/out/vs/code/electron-browser/workbench/anonymous function).setTimeout () onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- Uncaught TypeError: Cannot read property 'copyCellsFrom' of undefined at Buffer.reflowSmaller () at () at () at () at () at () at e.resize () at (/usr/share/code/resources/app/out/vs/code/electron-browser/workbench/anonymous function).setTimeout () /usr/share/code/resources/app/out/bootstrap- [uncaught exception]: TypeError: Cannot read property 'copyCellsFrom' of undefined onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- /usr/share/code/resources/app/out/bootstrap- TypeError: Cannot read property 'copyCellsFrom' of undefined at Buffer.reflowSmaller () at () at () at () at () at () at e.resize () at (/usr/share/code/resources/app/out/vs/code/electron-browser/workbench/anonymous function).setTimeout () onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- Uncaught TypeError: Cannot read property 'copyCellsFrom' of undefined at Buffer.reflowSmaller () at () at () at () at () at () at e.resize () at (/usr/share/code/resources/app/out/vs/code/electron-browser/workbench/anonymous function).setTimeout () /usr/share/code/resources/app/out/bootstrap- [uncaught exception]: TypeError: Cannot read property 'data' of undefined onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- /usr/share/code/resources/app/out/bootstrap- TypeError: Cannot read property 'data' of undefined at BufferLine.copyCellsFrom () at Buffer.reflowSmaller () at () at () at () at () at () at e.resize () at (/usr/share/code/resources/app/out/vs/code/electron-browser/workbench/anonymous function).setTimeout () onUnexpectedError @ /usr/share/code/resources/app/out/bootstrap- Uncaught TypeError: Cannot read property 'data' of undefined at BufferLine.copyCellsFrom () at Buffer.reflowSmaller () at () at () at () at () at () at e.resize () at (/usr/share/code/resources/app/out/vs/code/electron-browser/workbench/anonymous function).setTimeout () </pre</details
that's probably related to This issue I'm pretty sure is a native crash, not a JS exception.
How can I debug this?
Disabling doesn't help. <details</detailsAlthough, maybe, it does. The terminal died but the window survived.
fixed that exception just now in
FYI I do expect disabling conpty to fix this, something is going wrong in one of the calls to the native side, I just need people who can reproduce the problem to follow the steps in to find which native call(s) are causing the crash.
I've tried to reproduce this LOTS of times in both insiders and stable, but I can't reproduce this at all anymore. My guess is that one of the recent Windows updates patched something that was causing the hang.
while I can't repro this normally anymore, I am able to get it to happen, if I start a task that generates a LOT of output (e.g. running a full project lint with a CRLF / LF check the wrong way) and if I kill the task (using the trash can) while its still going, it seems to hang vscode every time. And unfortunately I don't see any logging that really looks interesting -- I don't even see any calls that correspond to the task starting up. (Though I do see some from the terminal starting much earlier) I do see this: But it seems to be in the logs regardless
And they're back. Same scenario (no idea why they went away for a while there) Here's the logs (or at least the end of it -- if you need the full log let me know) Here you can see I started 2 terminal tasks, and killed them. It looks like the hanging line is trying to resize the terminal after its been killed
Thanks I think that specifically is related to the introduction of the asynchronous spawning of the process introduced in Specifically this line is the issue as it doesn't set : That change was in May but there was another crash I just fixed for winpty () that could have just as easily happened in conpty, so maybe that was the one you were seeing in April?
We get a EBADF from ioctl on macOS which bricks the terminal when this happens: , trying to resize a not yet existing terminal I think? Also related to the async change.
now that the Remote Development is available in the stable VSCode, I have tried there and the terminal works fine there, so the issue seems to be in a difference between stable and insider, probably the bit you are referring to. Thanks
if the window is using remote development this crash would not happen as the terminal process is on the remote side.
for clarity, I was talking about , which you closed as duplicated of this one. In my case I never had a crash, I just got stuck on "Starting ...", this is not happening now that this has been made available in the stable version but is still the case in the insider version. Thought that knowing this may be helpful.
I'm not sure this is still happening after the fixes to ensure invalid dimensions aren't used for resizing, does anyone still see this in Insiders?
I don't know, if its related, but freezes are still happening for me with latest portable insiders build (vanilla). The freeze always happens when I close an open integrated terminal (via the trash symbol). And it was just one terminal open / no split panels. I cannot consistently reproduce it. My highly professional test case (): Typing 'asdf' (arbitrary input), press enter, repeat this 30 times or better more so that there is effectively just a bunch of terminal output produced. After that, shutting this terminal down freezes my VS code window completely, which results in windows asking me to reopen or close it. Sometimes I had to reopen terminal and repeat to see it hang. Tried also with developer tools and process explorer open, no error log and nothing consuming much CPU, it just gets unresponsive. My environment: Windows 10 Powershell as default terminal, but also happened with cmder in my other environment VSCode-win32-x64-1.36.0-insider
the issue I opened "VSCode doesn't save changes to file after running a process in terminal " is closed and marked duplicate of this, but I'm not using insider build. just regular one I downloaded from microsoft site. 1.35 and it happens in certain reproducible way. it happens every time following the steps. here
this issue is not restricted to insiders only
Occasional Windows 7 is hung up when I use VS Code integrated-terminal, When I logout Windows 7 SP1, then the dialog displayed: ! Windows 7 is OK after I close this dialog. The versions are 1.3X stable I used.
this issue had seemingly been resolved for me, after you made a few fixes, but since 1.38-insiders, it seems to have come back again.
there was a workaround for , do you use tasks as it could still possibly happen for tasks?
It definitely happens a LOT more frequently with tasks, but a couple of times I've had it happen when typing in the terminal
it happened just when typing in the terminal? I think the hang we identified happened because conpty has a race condition when you close the terminal too fast and we used a special flag that only tasks uses now.
Yeah, it crashed once for sure (and I'm pretty sure there was another time) where I was just starting to type a command (though I might have killed a terminal just before it). But in all the other cases now, it happens when a task starts -- usually my prettier/lint task (using yarn as the launcher)
FYI (in case you unsubscribed)
I just had it happen again, this time I just killed a terminal that was started from my watch task, which brought me back to my last opened terminal and I started typing my next command and I got about 15 characters in before vscode hung completely. Happened again -- exactly the same scenario
Looks like we need to be fixed in Windows, I'm hoping the fix can get pulled into 1903
if you get it to happen without using tasks can you create a process dump file? You should be able to do this via task manager: <img width="306" alt="Screen Shot 2019-08-22 at 11 10 23 AM" src="https://user-"You'll need to do this on the hanging conhost process which should be under VS Code. There may be multiple of these, you'll know the right one if when you kill it the UI becomes responsive again.
This seemingly went away (was fixed), but sometime since 1.41 or the last couple (few?) Windows insiders builds -- this is back.
So it looks like what was fixed, was reverted: And that timeline somewhat lines up with my experience.
I just wanted to emphasize how critical this issue is - any time I terminate a process in VSCode - it hangs and I have to wait for VSCode to restart. as reported in issue
I see there are dozens of other tickets referencing this same issue. I haven't read through all of them so I'm not sure what the status of this bug is, but since this ticket is still open (after a year) and since I'm still experiencing said issues constantly, with the most recent occurrence happening approximately 4 minutes ago, I'm assuming it hasn't been resolved yet. This happens to me all the time. It happens on my Windows desktop. It happens on my Windows laptop. I've never once had it happen on my Macbook. I can recreate this issue 95% of the time by having multiple terminal instances open, and then clicking on the "kill terminal" (garbage icon) on 1 of them in rapid succession. Please let me know where to find the logs I need to provide you with in order to help you fix this. is more aligned with what I've been experiencing but said ticket was closed with a reference to this one.
I also run into this issue frequently. The fix I use is to change the settings as follows: ! Disabling Conpty
Reliable repro: Run the following task on Windows and kill the terminal while it's outputting:
Has this still not been fixed?
I'm experiencing similar issues to . It seems like this mostly happens to Windows users - would using WSL be a possible workaround?
It is still happening to me, I just ran a script, tried to kill the terminal using dustbin button & it hanged and asks to reopen , Its very old bug, still not fixed.
Actually, I tried not firing up and closing terminals too frequently and it's been working fine for me.
I don't understand why it's happening. I tried to trace down the cause, but no benefit. Terminals of some files closing , some causing crash, tried disabling extensions, a new installation of vs code with default settings & everything I could, but no use. There is no errors in the code, Other terminals working properly, no crash, also tried in pycharm, no crash in there too. Only crashing while closing the vs code terminal (and that too only on some files), that's frustrating. Is it some specific thing or what, I don't understand, my brain is also crashing after a whole day of tracing the cause of crash. Do anyone have any idea, why it's happening & how could it be solved? If no solution, any workarounds?
I have this problem for a long time and have found a basic fix - simply uncheck the "Windows Enable Conpty" in the settings and you're good: [image: ] Ecto Ruseff <:
I don't know what conpty is. Will it cause any other errors? Or I will loose some features after disabling it? I know it could be offtopic, but I'm seriously confused here.
I’m not aware of any negative affect. I’ve been using it for years and am very happy :) On Tue, Dec 29, 2020 at 19:23 Ecto Ruseff <:
I'll try and report back here. Update: It worked. Disabling windows Conpty worked. No crash after that.
will the node-pty fix you have just commited will reach vs-code insiders first ? In other words how can I get it the quickest way possible ? Thanks for your help and making VScode better and better. It is much appreciated. Regards
I was hoping it would get to insiders today but there was some more changes needed to be made. You can follow for updates, when that's merged it should show up in the next insiders.
Unfortunately this is going back on the backlog due to issues I had trying to get create workers inside an packaged module. More context: The good news is that since conpty is now hosted in a separate process, when this hang occurs it will only take down all the terminals and it also gets detected and allows you to recover without a restart: !
Hi I am able to get the terminal to crash reliably with the following simple Python script on Windows: I run that script at the terminal by typing "python " "intranetserver" is replaced with a server on my intranet and I have set up SSH key authentication with Windows OpenSSH (now included in Windows 10), so the command runs without password prompt. I am able to run the ssh command directly at my VSCode terminal without issue (I see server login messages followed by "Testing ssh call"). However, if I run the Python 3 script above, the terminal will crash shortly after the ssh call. This seems to be an issue with subprocesses exiting after being run under the terminal. The number of lines that get output will vary. When the terminal crashes, the output is corrupted a bit: ! Pressing enter does nothing. Pressing CTRL+C does not work. I have tried disabling conpty, but it still crashes (and ANSI color no longer works). I am using PowerShell 7, but I tried system PowerShell and Command Prompt and it still crashes in every case. I have numerous extensions, but tried disabling the PowerShell extension which didn't help. I am using regular build version 1.54.2 Edit: Hmm... I found that by passing shell=True to Python's method, it works without freezing. I don't know what that means.
If it is of any help
Verified after weeks of usage and also no reports

Discussion:
.pipe(jsFilter) .pipe(util.rewriteSourceMappingURL(sourceMappingURLBase)) .pipe(jsFilter.restore) <del> .pipe(createAsar(path.join(process.cwd(), 'node_modules'), ['**/*.node', '**/vscode-ripgrep/bin/*', '**/node-pty/build/Release/*', '**/*.wasm'], 'node_modules.asar')); </del> <ins> .pipe(createAsar(path.join(process.cwd(), 'node_modules'), [ '**/*.node', '**/vscode-ripgrep/bin/*', '**/node-pty/build/Release/*', '**/node-pty/lib/worker/conoutSocketWorker.js', '**/node-pty/lib/shared/conout.js', '**/*.wasm' ], 'node_modules.asar')); </ins> let all = es.merge( packageJsonStream,

"native-is-elevated": "0.4.3", "native-keymap": "2.2.1", "native-watchdog": "1.3.0", <del> "node-pty": "0.10.1", </del> <ins> "node-pty": "0.11.0-beta7", </ins> "nsfw": "2.1.2", "spdlog": "^0.13.0", "sudo-prompt": "9.2.1",

"jschardet": "3.0.0", "minimist": "^1.2.5", "native-watchdog": "1.3.0", <del> "node-pty": "0.10.1", </del> <ins> "node-pty": "0.11.0-beta7", </ins> "nsfw": "2.1.2", "spdlog": "^0.13.0", "tas-client-umd": "0.1.4",

resolved "https://registry.yarnpkg.com/node-addon-api/-/node-addon-api-3.1.0.tgz#98b21931557466c6729e51cb77cd39c965f42239" integrity sha512-flmrDNB06LIl5lywUz7YlNGZH/5p0M7W28k8hzd9Lshtdh1wshD2Y+U4h9LD6KObOy1f+fEVdgprPrEymjM5uw== <del> node-pty@0.10.1: version "0.10.1" resolved "https://registry.yarnpkg.com/node-pty/-/node-pty-0.10.1.tgz#cd05d03a2710315ec40221232ec04186f6ac2c6d" integrity sha512-JTdtUS0Im/yRsWJSx7yiW9rtpfmxqxolrtnyKwPLI+6XqTAPW/O2MjS8FYL4I5TsMbH2lVgDb2VMjp+9LoQGNg== </del> <ins> node-pty@0.11.0-beta7: version "0.11.0-beta7" resolved "https://registry.yarnpkg.com/node-pty/-/node-pty-0.11.0-beta7.tgz#aed0888b5032d96c54d8473455e6adfae3bbebbe" integrity sha512-uApPGLglZRiHQcUMWakbZOrBo8HVWvhzIqNnrWvBGJOvc6m/S5lCdbbg93BURyJqHFmBS0GV+4hwiMNDuGRbSA== </ins> dependencies: nan "^2.14.0"

util "^0.11.0" vm-browserify "^1.0.1" <del> node-pty@0.10.1: version "0.10.1" resolved "https://registry.yarnpkg.com/node-pty/-/node-pty-0.10.1.tgz#cd05d03a2710315ec40221232ec04186f6ac2c6d" integrity sha512-JTdtUS0Im/yRsWJSx7yiW9rtpfmxqxolrtnyKwPLI+6XqTAPW/O2MjS8FYL4I5TsMbH2lVgDb2VMjp+9LoQGNg== </del> <ins> node-pty@0.11.0-beta7: version "0.11.0-beta7" resolved "https://registry.yarnpkg.com/node-pty/-/node-pty-0.11.0-beta7.tgz#aed0888b5032d96c54d8473455e6adfae3bbebbe" integrity sha512-uApPGLglZRiHQcUMWakbZOrBo8HVWvhzIqNnrWvBGJOvc6m/S5lCdbbg93BURyJqHFmBS0GV+4hwiMNDuGRbSA== </ins> dependencies: nan "^2.14.0"