-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Update to 1.71 #5535
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
Update to 1.71 #5535
Conversation
- // This is most likely due to ad blockers | ||
- fetch(telemetryEndpointUrl, { method: 'POST' }).catch(err => { | ||
- this.impl = NullTelemetryService; | ||
- }); |
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.
I actually have no idea what happened with this segment in the original version. I have not found any commit where this was removed or changed. Maybe sbd. finds the reason...
the cli fix seems to be fixed in upstream, the telemtry patch requires (again) some fixing and adjustments.
@benz0li feel free to give the CI artificats a try. From my point of view it looks fine. |
@fritterhoff Functionality [modified by patches] tested and found to work:
👉 Same as #5417 (comment). |
@fritterhoff Could you please check if rendering is working properly for you at https://vscode-r.jupyter.b-data.ch?: I get the following warning in the browser's web console:
When I reload the page with an open Terminal, it does not get rendered properly. |
I'll check it asap. Well.. yes the rendering seems to fail. I'll try it with my own containers. |
So I can at least point to the commit where this change was introduced: microsoft/vscode@2f72682 Have to debug that further 😉 |
So I tried again. Now it works fine, beside a rather slow loading. Also reloading works. I have no idea what actually failed yesterday. Maybe the browser only ran into a timeout or something like that. |
Everything works fine with Firefox as it uses the WebGL renderer. Safari falls back to the dom render, as canvas can not be loaded [and WebGL is 1.71.0ScreenshotLognothing about xterm 1.70.2ScreenshotLog
|
Damn it. Sadly I don't have the option to test safari. That will get complicated to reproduce/fix. Can you maybe test codespaces? |
I only made some quick checks using BrowserStack. Here Safari works fine but I'm not sure if they make any modifications or if I made did not test it enough. If i remember correct, @jsjoeio is also using a Mac. So maybe he can debug that a little bit more. I don't have access to a Macintosh device at all - sorry. |
Safari: Web Console(The link for Safari: Web Network👉 According to the network pane, |
No, unfortunately not. I am mainly using my self-hosted GitLab instance and a free account on both https://github.com and https://gitlab.com. |
Well... xterm has been updated to v5.0.0 (beta 32): Many issues with this version. ℹ️ v1.70.2 used xterm v4.20.0 (beta 20). |
I also saw the quite large amount of open issues but I'm not sure which actually are related to our problems. I only recognized that the upstream vscode project updated their dependency since the release of 1.71. |
Originally posted by @meganrogge in xtermjs/xterm.js#3357 (comment) |
Out of curiosity. What Safari version do you use? According to https://caniuse.com/webgl2 webgl should be supported by the latest Safari versions. |
Safari v15.6.1.
Yes it is. Disabled by default in VS Code: https://github.com/microsoft/vscode/blob/784b0177c56c607789f9638da7b6bf3230d47a8c/src/vs/workbench/contrib/terminal/browser/xterm/xtermTerminal.ts#L285 |
Ah... I missed the edit in your comment yesterday. |
So I can at least confirm that the rendering of the terminal has a bug on iPads too, even though it is not the same as mentioned by you @benz0li. |
It is the same issue. The Terminal looks like this after a reload: |
Cross reference: microsoft/vscode#160070 |
Sorry, we had yesterday off for holiday in the US! Can I just say this is such an awesome PR/conversation to come back to? Y'all are replacing me and @code-asher 😂 I have to tackle some other priorities but will get to this either today or tomorrow. And yes, I'm on macOS so I can test the Safari weirdness! Thank you two for getting the ball rolling! |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #5535 +/- ##
=======================================
Coverage 72.44% 72.44%
=======================================
Files 30 30
Lines 1673 1673
Branches 366 366
=======================================
Hits 1212 1212
Misses 398 398
Partials 63 63 Continue to review full report at Codecov.
|
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.
I think all of this looks fine. At least I don't see anything to be concerned about but I also have trouble reviewing these. I'll defer my review to @code-asher
+ const result: ResolverResult = { authority: { authority, host: host, port: port, connectionToken }, options }; | ||
RemoteAuthorities.set(authority, result.authority.host, result.authority.port); | ||
this._cache.set(authority, result); | ||
this._onDidChangeConnectionData.fire(); |
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.
note to self: this change is fine, right?
@@ -1,5 +1,7 @@ | |||
Add support for telemetry endpoint | |||
|
|||
Contains some fixes included in https://github.com/microsoft/vscode/commit/b108bc8294ce920fcf2ee8d53f97c3bcf3316e1c |
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.
Nice addition 👍🏼
Since upstream vs code "hot-fixed" the safari bug I would suggest to include this fix in code-server as well? |
@jsjoeio @benz0li I included the changes done by microsoft/vscode#160332 For simplicity I placed it in a single diff file. That can be removed in case of a new release/update. |
You rock. Thanks for doing that! I'm still reviewing this but should be done today. |
Looking really good! I need to test the safari patch and the last three and then we should be good. |
@fritterhoff I was talking to @code-asher about the Do you mind removing it in this PR? Otherwise I can do it in a followup PR. |
I think the x86-64 job is timing out. You can increase this to 20m here |
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.
I tested everything and it all looks good! @fritterhoff feel free to mark ready and then I can merge
Oops, fat finger click on the ready for review |
Done
Would do that in a new PR and remove it in the next release? |
Oh! Good call. I thought it was in this version but looks like we need to wait for the next release. |
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.
Woohoo!
Opened an issue to track |
|
@jsjoeio The footprint of There is grpc in |
That is a substantial increase. Thank you for pointing that out @benz0li! Let me and @code-asher dig in and see why that is. |
Hmm I am not sure; |
We figured it out using
|
As a first attempt the required fixes/changes for the code version 1.71.
Testing Plan
To test this locally:
Patches tested
The following patches were tested locally:
Fixes #5528