-
Notifications
You must be signed in to change notification settings - Fork 36.4k
[email protected] #274736
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
[email protected] #274736
Conversation
- Updates conpty microsoft/node-pty#811 - Adds Buffer support to API microsoft/node-pty#812 Part of #269213
|
@anthonykim1 this seems to be locking up the pty host somehow |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the node-pty dependency from version 1.1.0-beta35 to ^1.1.0-beta39 and removes a type casting workaround that is no longer necessary with the newer version.
Key changes:
- Upgraded
node-ptyto version^1.1.0-beta39in all package manifests - Removed the
as anytype cast when writing binary data to the pty process, along with associated TODO and eslint-disable comments
Reviewed Changes
Copilot reviewed 3 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| src/vs/platform/terminal/node/terminalProcess.ts | Removed as any cast and related comments when writing Buffer to pty process, now that node-pty supports Buffer type natively |
| package.json | Updated node-pty dependency version to ^1.1.0-beta39 |
| package-lock.json | Updated lock file with new node-pty version and integrity hash |
| remote/package.json | Updated node-pty dependency version to ^1.1.0-beta39 for remote package |
| remote/package-lock.json | Updated remote lock file with new node-pty version and integrity hash |
Files not reviewed (1)
- remote/package-lock.json: Language not supported
|
@Tyriar Are you still getting the odd behavior? Things seem fine maybe except for |
|
I think so, we need to manually test on Windows when we try updating. |
Part of #269213