1. Atlassian Labs Avatar Atlassian Labs
  2. Partner Integrations
  3. atlascode
  4. Issues

Latest VS code update breaks plugin

Issue #375 resolved
Chris Liotta created an issue

After installing Version: 1.43.0 of VSCode, the Atlassian plugin no longer shows in the extensions bar. Atlassian Commands also do not work in the command pallet. I have tried reinstalling the extension.

Comments (14)

  1. Nick Rundquist

    Sorry to hear you’re having problems. I have couple of questions to help us figure out what’s going wrong:

    Which OS are you on?
    Are you using the remote development feature of VS Code or running locally?

  4. Chris Liotta reporter

    Nothing at launch, but get this error “command 'atlascode.bb.createPullRequest' not found” when running from command pallet.

  5. Nick Rundquist

    The Atlassian extension requires the Red Hat YAML extension to be installed. Is it possible that the YAML extension has somehow been uninstalled or deactivated?

  7. Nick Rundquist

    Can you check the extension host logs and see if there’s anything related to “atlascode” in there? You can view the logs by going to the “View” menu and selecting “Output” and then selecting “Log (Extension Host)” from the drop-down menu on the right side. You might need to scroll down to the bottom of the drop-down.

  8. Chris Liotta reporter

    I am seeing an error:

    ‌

    [2020-03-10 15:21:49.191] [exthost] [error] Error: ENOENT: no such file or directory, open '/Users/christopherliotta/.vscode/extensions/atlassian.atlascode-2.4.9/resources/html/reactView.html'
    at Object.openSync (fs.js:447:3)
    at Object.func (electron/js2c/asar.js:140:31)
    at Object.func [as openSync] (electron/js2c/asar.js:140:31)
    at Object.readFileSync (fs.js:349:35)
    at Object.fs.readFileSync (electron/js2c/asar.js:542:40)
    at Object.fs.readFileSync (electron/js2c/asar.js:542:40)
    at /Users/christopherliotta/.vscode/extensions/atlassian.atlascode-2.4.9/build/extension/extension.js:1:4199071
    at Generator.next (<anonymous>)
    at /Users/christopherliotta/.vscode/extensions/atlassian.atlascode-2.4.9/build/extension/extension.js:1:4196767
    at new Promise (<anonymous>)
    at Tp (/Users/christopherliotta/.vscode/extensions/atlassian.atlascode-2.4.9/build/extension/extension.js:1:4196512)
    at Ip (/Users/christopherliotta/.vscode/extensions/atlassian.atlascode-2.4.9/build/extension/extension.js:1:4196801)
    at Function._callActivateOptional (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:722:204)
    at Function._callActivate (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:721:862)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:720:960
    at async Promise.all (index 0)

    ‌

  10. Chris Liotta reporter

    I’ve copied the resource folder from the repo to my local. This fixes the issue. I am not sure why the folder doesn’t get added when installing the plugin

  13. Nick Rundquist

    We had a problem with our build process last week that led to some bad deployments, but 2.4.9 wasn’t affected.

    Thanks for bringing this up and letting us know what the ultimate resolution was. Please let us know if this happens again with a future upgrade.

  15. Log in to comment
Assignee
–
Type
bug
Priority
major
Status
resolved
Component
–
Votes
0
Watchers
1