- edited description
Support for VS Code Remote Development
Getting this error message after attaching to a running container (using VSCode remote)
Cannot activate the &;Atlassian for VSCode (Official)' extension because it depends on the 'Git' extension, which is not loaded. Would you like to reload the window to load the extension?#39
Each time I reload the window, it happens again
Using VSCode insiders. Software versions:
Version: 1.34.0-insider
Commit: 473af338e1bd9ad4d9853933da1cd9d5d9e07dc9
Date: 2019-05-01T05:15:04.403Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Linux x64 4.15.0-47-generic
Comments (31)
-
reporter -
Account Deactivated @jorgearevalo_reclamador The extension has a dependency on the git extension which is shipped by default with VSCode. Can you try enabling the git extension manually. You can view them by running
Extensions: Show Built-in Extensions
from the command palette.Also can you try running any other git command from the command palette and let us know if that is working correctly?
-
reporter Hi @pbusam thanks for your response.
Git extension is enabled, and cannot be disabled. But git commands are not working. For example, git log opens a new tab with no output, and git fetch / git pull don’t show output at all.
I can properly attach to a running container, but extension is not loaded.
Updated VSCode to the last version. No changes.
Version: 1.34.20-insider
Commit: 57b550c559b945eb9d871dbf2b2e4cb9e31e2551 -
Account Deleted @{557058:a30b5736-f3cf-41d7-aad0-99c9ffac78ce} what @Jorge Arevalo is trying to do is running on the VSCode insiders and using the new Remote Development feature. In his case is using Remote Development with containers. What is happening is that VSCode is partially executing on a remote server.
This what I think is going on, git is running on the remote container and no locally and the Git extension can’t handle that remote connection. So VSCode disables that and “Atlassian for VSCode” will not load
Here’s some Tips and Tricks
https://code.visualstudio.com/docs/remote/troubleshooting
Developing Remote Extensions
https://code.visualstudio.com/api/advanced-topics/remote-extensions
-
Also getting this, only when using the new Remote Development feature.
-
I’m getting this same message, using regular VS Code with the Remote Development. I do not see any helpful output in any debugging or output views.
-
reporter Still happening. I think @{557058:a037002c-3cbb-490f-a7e4-8987b77a7b9d} is right about what’s happening. But can’t confirm it.
-
I can confirm that I am also getting this same error when trying to use with the “Remote - SSH” VS Code remote development. I’m on a stable build of VS Code:
Version: 1.35.1 (system setup)
Commit: c7d83e57cd18f18026a8162d042843bda1bcf21f
Date: 2019-06-12T14:30:02.622Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.18362 -
Issue
#167was marked as a duplicate of this issue. -
I can confirm that I’m getting this issue as well when using Remote Developer.
-
Same problem for me
-
any ETA for fixing this issue ?
-
reporter - edited description
-
It looks it is not compatible with remote development yet. However I was able to use it using SSH adding the setting below and tweaking the Jira login host when prompted:
"remote.extensionKind": {
"ms-azuretools.vscode-cosmosdb": "ui",
"msjsdiag.debugger-for-chrome": "workspace"
}
More information on how to test here:
https://code.visualstudio.com/api/advanced-topics/remote-extensions
-
@Arturo Linares - Could you please elaborate on “tweaking the Jira login host when prompted”.
I tried adding the given code block to my settings.json, but this makes no difference. Note that the code-block you’ve pasted is the example from the VSCode remote development article, and hav nothing to do with this Atlassian extension!!
I have also tried adding
"atlassian.atlascode": "ui",
` to theremote.extensionKind
block, but that makes no difference either.Thanks
-
I may have made some progress…
- Add
"atlassian.atlascode": "workspace",
` to theremote.extensionKind
block insettings.json
(you’ll need to add the block first if it doesn’t exist) - Install the extension to your remote (SSH) workspace
- Close VS Code
- Open a new (or existing) local project in VS Code
- Add the extension to that project too (which will add it to your host system)
- Re-open your remote SSH workspace
- You should be prompted to authenticate to Atlassian automatically. If not, click the little “jira” link in the status bar (left-hand-side”
- The “Authenticate” button should now work - if you didn’t do the additional step of adding the extension to your host as well, then you’ll find that your browser opens to 127.0.0.1:34145 and then does nothing!
After the above steps, I thin all is working as expected - but time will tell!
Otherwise the Jira extension port may need opening between the remote and host.
UPDATE:
A better option for steps 3 -5 above is to forward the port to your remote SSH. E.g, BEFORE STEP 1:
Add a port forward rule to your ssh config. E.g,
Host localhost User root HostName 127.0.0.1 IdentityFile ~/.ssh/id_rsa LocalForward 127.0.0.1:31415 127.0.0.1:31415
You should then be able to continue as follows:
- Install the extension to your remote (SSH) workspace
- Re-load your remote SSH workspace
- You should be prompted to authenticate to Atlassian automatically. If not, click the little “jira” link in the status bar (left-hand-side”
- Clicking the authenticate button should now work (you’ll get redirected to Atlassian to authenticate)
- Add
-
@Toby Bisco Adding
"remote.extensionKind": { "atlassian.atlascode": "workspace" }
to settings.json and installing the extension again worked great for me- I’d been struggling to get this to work with the WSL Remote extension. Thx! -
reporter I guess the solution proposed by @Toby Bisco works for SSH connection but not for attaching to a running container (I tried adding
"atlassian.atlascode": "workspace",
` to theremote.extensionKind
block insettings.json
but didn’t work)Thx anyway!
-
This seems to be an easy fix, the package.json just needs a another variable with “extensionKind”: "workspace"
-
- changed status to open
-
Account Deactivated @Jorge Arevalo Could you try the following steps and let us know if it works?
- After you attach to a running container, run
Preferences: Open settings (JSON)
and add the following:
"remote.extensionKind": { "atlassian.atlascode": "workspace" },
- Run
Remote-Containers: Open Container Configuration File...
and add the following to forward the port:
"appPort": [ 31415 ]
- After you attach to a running container, run
-
reporter @{557058:a30b5736-f3cf-41d7-aad0-99c9ffac78ce} it works!
I had to restart VSCode after following the steps, but the error message dissapeared. Just a couple of details:
- The Jira and Bitbucket (Official) extension (former Atlassian for VSCode extension) wasn’t installed inside the container, but I could install it using the Install in attached container button
- After installing the extension, the container configuration file looks like this
{ "appPort": [ 31415 ], "workspaceFolder": "MY_WORKSPACE_FOLDER", "extensions": [ "atlassian.atlascode", "MORE_EXTENSIONS_HERE", ] }
Many thanks!
-
Account Deactivated @Jorge Arevalo Thanks for trying it out. Glad that worked
(The port is only used during the authentication flow. So feel free to remove the
appPort
configuration and add it if you want to authenticate again) -
reporter @{557058:a30b5736-f3cf-41d7-aad0-99c9ffac78ce} thanks for the tip
So, can this ticket be closed as solved?
-
I wouldn't say so. The solutions posted here are workarounds at best.
Get Outlook for Androidhttps://aka.ms/ghei36
-
Issue
#169was marked as a duplicate of this issue. -
Account Deactivated @Jorge Arevalo I agree with @Bogdan Calapod. We'll keep this issue open to track the
VS Code remote developement support
in general. -
Account Deactivated - changed title to Support for VS Code Remote Development
- marked as enhancement
-
reporter Ok, fair enough
-
Account Deactivated We have released version 2.1.2 of the extension which makes it run as a workspace extension by default. The authentication screen also detects if a remote workspace is open and prompts to do authentication in a non-remote workspace. This works because the secrets/passwords are persisted in local OS rather than remote environment https://code.visualstudio.com/api/advanced-topics/remote-extensions#persisting-secrets.
We are closing this issue. Please report any new issues by creating a new Bitbucket issue or by using the
Send Feedback
button in the extension's settings screen. -
Account Deactivated - changed status to resolved
- Log in to comment
Getting this error message attaching to a running container
Cannot activate the 'Atlassian for VSCode (Official)' extension because it depends on the 'Git' extension, which is not loaded. Would you like to reload the window to load the extension?
Each time I reload the window, it happens again
Using VSCode insiders. Software versions:
Version: 1.34.0-insider
Commit: 473af338e1bd9ad4d9853933da1cd9d5d9e07dc9
Date: 2019-05-01T05:15:04.403Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Linux x64 4.15.0-47-generic