| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
✨ Coder.com for PR #4840 deployed! It will be updated on every commit.
|
Sorry, something went wrong.
Codecov Report
@@ Coverage Diff @@
## main #4840 +/- ##
==========================================
+ Coverage 69.72% 69.73% +0.01%
==========================================
Files 29 29
Lines 1645 1649 +4
Branches 363 363
==========================================
+ Hits 1147 1150 +3
- Misses 424 425 +1
Partials 74 74
Continue to review full report at Codecov.
|
Sorry, something went wrong.
There was a problem hiding this comment.
🎉 🎉 🎉
Sorry, something went wrong.
|
Re-run e2e tests after merging: #4857 |
Sorry, something went wrong.
Need to add back in |
Sorry, something went wrong.
|
I believe the e2e tests are failing because we need to update VS Code (waiting on another PR) |
Sorry, something went wrong.
Sorry, something went wrong.
|
@ericzhucode what is the output when you run code-server --version? |
Sorry, something went wrong.
Sorry I forgot to update this comment. After cherry-pick this commit and build code server again, it's working perfectly now and no disconnection occurred. |
Sorry, something went wrong.
|
@ericzhucode hooray!!! Really happy it's working. Thank you for confirming! 🎉 |
Sorry, something went wrong.
* chore: add ipc hook to e2e script * refactor: allow codeServerArgs in e2e tests * feat: add --cert e2e extension test * fix: wrap websocket in proxy * fixup: remvoe ignoreHTTPSErrors * fixup: make codeServerArgs readonly * fixup! add back ignoreHTTPSErrors
| Back | FazBrowse Home | New Git URL |
Summary
This PR fixes a regression introduced in 4.0.1. Previously in 3.12.0, using the --cert flag allowed you to use code-server locally over HTTPS. The regression broke that functionality causing the ExtensionHost to repeatedly reconnect and fail. We fixed this by wrapping the socket in our SocketProxyProvider before passing back to VS Code. This is because TLSSockets cannot be passed to child processes.
Changes
Context
We didn't have a test for this feature so the regression was introduced in 4.0.1. We've now added a new e2e test which uses the --cert flag and attempts to use an extension. This will only work if the ExtensionHost is working properly. Therefore, this will prevent new regressions.
After adding the new e2e test, we tested it against the 3.12.0 build and it worked as expected:
extension-proof.mp4Here is that same test passing against code-server using a local dev build with the regression fixed:
4.0.2-proof.mp4We also took extensive notes and whiteboarded the flow here to help us arrive at the solution.
Fixes #4693