CodeTogether-Inc / CodeTogether-Live

Repository for issues, documentation and more for codetogether.com and associated VS Code extension and Eclipse plugins.
Other
103 stars 12 forks source link

[VS Code plugin, On-premises] Can't join a session #339

Closed krzikalla closed 3 years ago

krzikalla commented 3 years ago

I use VS Code (v 1.61.0) remote extension, windows client, linux server. When I want to join a session I get the message:

CodeTogether requires access to VS Code Proposed APIs to provide Terminal sharing, quick open for files, 
search in workspace and more. Enabling access allows CodeTogether to use these services for a richer 
experience. Would you like to enable now?

I click Enable. Then I get

Reconnect to the Remote System to restart the VS Code Server to finish enabling access for full CodeTogether services.

I click Reload Window. The window is reloaded, then the first question pops up again. Seems to be an endless loop.

If I click No for the first question, the window loads with an apparently empty session. I don't even see an open editor.

In the runtime status of the extension I see two errors reading: Cannot read property 'endEmitted' of undefined The logs are silent (as far as I can tell).

TimWebb commented 3 years ago

Are you still seeing this issue? We made a number of fixes in the proposed API clean up in the 5.0 release.

For now we are unable to reproduce this issue. I'll close out this card but please do reopen it with details if you are still seeing this with 5.0.

americk0 commented 2 years ago

I'm having the exact same issue. I'm running on WSL 2 with Ubuntu 18 LTS and this issue seemed to pop up sometime in the last 2 months

TimWebb commented 2 years ago

@americk0 Thanks for letting us know.

Can you confirm if it is actively happening every time for you right now? And that you are running on CT 5.0 version?

americk0 commented 2 years ago

Strange. In an attempt to get it to work earlier today I uninstalled it from WSL, reinstalled it but locally on Windows this time and then closed all my VS Code windows and opened a new one and got pulled away before I could test it again. I just tested it after seeing your comment and it was working so I uninstalled it again, reinstalled it on WSL again, and closed all my VS Code windows again and then opened a new window in WSL, opened one of my project folders, and I was able to start a session.

I can confirm that I'm using v5.0.0. Whatever it was, it's working for me now. Thanks for the reply

AmineAyachi commented 2 years ago

start vscode as administrator so that it can perform the required actions then reload it to finish the process

krzikalla commented 2 years ago

With the update to VS COde 1.63 the issue has popped up again. Code together version is 5.0.0-b01127. Starting as administrator isn't possible for me.

brianvfernandes commented 2 years ago

@krzikalla please update to the latest release, 5.0.3, we have specific fixes in this area for VS Code 1.63 and it should resolve this issue.

brianvfernandes commented 2 years ago

@krzikalla if you're using CodeTogether on premises, please download and install this extension alongside your existing CodeTogether extension. This should fix the issue, no matter what version of CodeTogether you're using (you can stick to 5.0.0-b01127). Your company would also have received detailed instructions about this fix via email yesterday. Do let us know if you require further assistance.

DerAlSem commented 3 months ago

Latest version, using it with Cursor:

CodeTogether Live requires access to VS Code Proposed APIs to provide Terminal sharing, quick open for files, search in workspace and more. Enabling access allows CodeTogether Live to use these services for a richer experience. Would you like to enable now?

ENABLE

Reload the VS Code window now to finish enabling all CodeTogether Live services.

RELOAD

And start over. Feel free to ask for any additional info required.