-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
GH-815: Bumped up the node-pty version. #816
Conversation
The new version is intentionally 0.7.1 to be sync with VSCode. Signed-off-by: Akos Kitta <kittaakos@gmail.com>
So the only reason is to be in sync ? why do we want to be ? |
@@ -4,7 +4,7 @@ | |||
"description": "Theia process support.", | |||
"dependencies": { | |||
"@theia/core": "^0.2.0", | |||
"node-pty": "^0.7.0" | |||
"node-pty": "^0.7.1" |
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.
why not 0.7.2?
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.
They have a broken build. But this did not fix anything. So does not matter.
Did not fix anything. I am closing this. |
I think in general it is good to upgrade our deps to latest releases, since usually they include fixes. |
See also #817 since RawProcess/TerminalProcess have more testing into the process exit etc... It may fix the issue. |
Cool, thanks! Let me try. It is just complicated to bundle an application from the Theia source. |
Test flakiness was caused by microsoft/node-pty#159 (fixed in 0.7.3). |
The new version is intentionally 0.7.1 to be sync with VSCode.
Closes #815.
Signed-off-by: Akos Kitta kittaakos@gmail.com