Kayvan Sylvan

> Good news - [PR](https://github.com/coder/code-server/pull/5624) is pretty much good to go. We should be able to wrap it up Monday assuming all goes well. Would you like me to try...

What's the easiest way for me to test this?

> That'll load code-server with the changes. Then you could try using any basic extension that uses asExternalUri and it should work. I think Tabnine will need changes upstream after...

Looks like my Debian instance wasn't updated to NodeJS16. Fixed that and now seeing this: ``` $ yarn add @coder/code-server-pr@4.7.1-5624-6ae9dec77528bc9af1b1de503d56ea5318bab99b yarn add v1.22.19 info No lockfile found. [1/4] Resolving packages......

I see the new code with the proxy server auto-forwarding is in code-server, do you know what needs to happen with tabnine extension to use it?

The tabnine web code should be changed to use something like {baseURL}/proxy/5555 instead of 127.0.0.1:5555 for the tabnine hub, since this PR went into the base code-server: https://github.com/coder/code-server/pull/5624 @jsjoeio

https://github.com/OniOni/node-idevice/pull/6/files

What needs to happen to fix this now? The latest code-server is now using the /proxy port forwarding, as you can see here:  @jsjoeio ?

I'm using TabNine on my VSCode Web self-hosted instance running in the cloud. The details are here: https://github.com/ksylvan/remote-coding

This issue is still occurring with the latest TabNine and code-server