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
isWrapped exception in terminal #59114
Comments
I'm hitting an error about isWrapped property in 1.28.0, is this the same issue you just fixed? In Chrome debug console:
|
@IlyaBiryukov yep, let me know if you see it again in Monday's build |
Seeing this in todays build. VS Code version: Code - Insiders 1.28.0-insider (5ba5f14, 2018-09-26T07:25:01.336Z) |
I guess my fix only covered one of the cases. The latest xterm.js should fix this due to the additional bound checking in xtermjs/xterm.js#1693, but since this is an error I expect to have minimal impact on the actual experience, there were some issues when upgrading xterm.js last and because we're so late in the iteration, I'd say we hold off on this until 1.29. |
Fixed in aaee349 |
@Tyriar This happens quite often (testing on Linux) and will make it difficult to spot other errors. I'd suggest to still fix this for the September milestone. |
This is annoying since it keeps bringing up the chrome debugging window. I'd said earlier it makes the terminal slow, I think that was not correct. But I do wonder if this is related to the fact that the terminal often isn't painting correctly. |
This is not showing up in our error telemetry, I don't have a repro and pulling in the fix in isolation is non-trivial so I'm removing candidate. |
xtermjs/xterm.js#1702
The text was updated successfully, but these errors were encountered: