Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Error: Failed to load plugins: Erro:request "getDeployedPluginIds' when a plugin is provided with a reference to meta.yaml file #14805

Closed
3 of 5 tasks
apupier opened this issue Oct 8, 2019 · 4 comments
Closed
3 of 5 tasks

Error: Failed to load plugins: Erro:request "getDeployedPluginIds' when a plugin is provided with a reference to meta.yaml file #14805

apupier opened this issue Oct 8, 2019 · 4 comments
Labels
area/editor/theia Issues related to the che-theia IDE of Che kind/bug Outline of a bug - must adhere to the bug report template. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.

Comments

@apupier
Copy link
Contributor

apupier commented Oct 8, 2019 •
edited by l0rd
Loading

Describe the bug

when using a component referencing a meta.yaml file like

  - id: >-
      https://raw.githubusercontent.com/apupier/che-plugin-registry/camelk/v3/plugins/redhat/vscode-camelk/latest/meta.yaml
    memoryLimit: 1G
    type: chePlugin

During first load, there is no complaint. The pod log is fine:

Starting the deployer with the list of resolvers [ LocalDirectoryPluginDeployerResolver {},
  GithubPluginDeployerResolver { unpackedFolder: '/tmp/github-remote' },
  HttpPluginDeployerResolver { unpackedFolder: '/tmp/http-remote' },
  VsCodePluginDeployerResolver { vscodeExtensionsFolder: '/tmp/vscode-extension-marketplace' } ]
Theia Endpoint 22/pid listening on port 2506
Found the list of default plugins ID on env: undefined
Found the list of plugins ID on env: local-dir:///plugins/sidecars/redhat_vscode_camelk_latest
Found the list of default plugins ID from CLI: undefined
unzipping the VS Code extension 'redhat.vscode-camelk.latest.ejskikaxwe.vscode-camelk-0.0.9-86.vsix' to directory: /tmp/vscode-unpacked/redhat.vscode-camelk.latest.ejskikaxwe.vscode-camelk-0.0.9-86.vsix
unzipping the VS Code extension 'redhat.vscode-camelk.latest.elastnllsu.vscode-kubernetes-tools-1.0.0.vsix' to directory: /tmp/vscode-unpacked/redhat.vscode-camelk.latest.elastnllsu.vscode-kubernetes-tools-1.0.0.vsix
PluginTheiaDirectoryHandler: accepting plugin with path /tmp/vscode-unpacked/redhat.vscode-camelk.latest.ejskikaxwe.vscode-camelk-0.0.9-86.vsix
Resolving "redhat.vscode-camelk.latest.ejskikaxwe.vscode-camelk-0.0.9-86.vsix" as a VS Code extension...
Resolved "redhat.vscode-camelk.latest.ejskikaxwe.vscode-camelk-0.0.9-86.vsix" to a VS Code extension "vscode-camelk@0.0.9" with engines: { vscode: '^1.33.0' }
PluginTheiaDirectoryHandler: accepting plugin with path /tmp/vscode-unpacked/redhat.vscode-camelk.latest.elastnllsu.vscode-kubernetes-tools-1.0.0.vsix
Resolving "redhat.vscode-camelk.latest.elastnllsu.vscode-kubernetes-tools-1.0.0.vsix" as a VS Code extension...
Resolved "redhat.vscode-camelk.latest.elastnllsu.vscode-kubernetes-tools-1.0.0.vsix" to a VS Code extension "vscode-kubernetes-tools@1.0.0" with engines: { vscode: '^1.31.0' }
unzipping the VS Code extension 'redhat_vscode_yaml.vsix' to directory: /tmp/vscode-unpacked/redhat_vscode_yaml.vsix
PluginTheiaDirectoryHandler: accepting plugin with path /tmp/vscode-unpacked/redhat_vscode_yaml.vsix
Resolving "vscode:extension/redhat.vscode-yaml" as a VS Code extension...
Resolved "vscode:extension/redhat.vscode-yaml" to a VS Code extension "vscode-yaml@0.5.3" with engines: { vscode: '^1.31.0' }
the accepted plugins are []
the acceptedFrontendPlugins plugins are []
the acceptedBackendPlugins plugins are [ PluginDeployerEntryImpl {
    originId: 'local-dir:///plugins/sidecars/redhat_vscode_camelk_latest',
    pluginId:
     'redhat.vscode-camelk.latest.ejskikaxwe.vscode-camelk-0.0.9-86.vsix',
    map: Map { 'package.json' => [Object] },
    changes:
     [ 'PluginVsCodeFileHandler', 'PluginVsCodeDirectoryHandler' ],
    acceptedTypes: [ 1 ],
    currentPath:
     '/tmp/vscode-unpacked/redhat.vscode-camelk.latest.ejskikaxwe.vscode-camelk-0.0.9-86.vsix/extension',
    initPath:
     '/plugins/sidecars/redhat_vscode_camelk_latest/redhat.vscode-camelk.latest.ejskikaxwe.vscode-camelk-0.0.9-86.vsix',
    resolved: true,
    resolvedByName: 'LocalDirectoryPluginDeployerResolver' },
  PluginDeployerEntryImpl {
    originId: 'local-dir:///plugins/sidecars/redhat_vscode_camelk_latest',
    pluginId:
     'redhat.vscode-camelk.latest.elastnllsu.vscode-kubernetes-tools-1.0.0.vsix',
    map: Map { 'package.json' => [Object] },
    changes:
     [ 'PluginVsCodeFileHandler', 'PluginVsCodeDirectoryHandler' ],
    acceptedTypes: [ 1 ],
    currentPath:
     '/tmp/vscode-unpacked/redhat.vscode-camelk.latest.elastnllsu.vscode-kubernetes-tools-1.0.0.vsix/extension',
    initPath:
     '/plugins/sidecars/redhat_vscode_camelk_latest/redhat.vscode-camelk.latest.elastnllsu.vscode-kubernetes-tools-1.0.0.vsix',
    resolved: true,
    resolvedByName: 'LocalDirectoryPluginDeployerResolver' },
  PluginDeployerEntryImpl {
    originId: 'vscode:extension/redhat.vscode-yaml',
    pluginId: 'vscode:extension/redhat.vscode-yaml',
    map: Map { 'package.json' => [Object] },
    changes:
     [ 'PluginVsCodeFileHandler', 'PluginVsCodeDirectoryHandler' ],
    acceptedTypes: [ 1 ],
    currentPath: '/tmp/vscode-unpacked/redhat_vscode_yaml.vsix/extension',
    initPath: '/tmp/vscode-extension-marketplace/redhat_vscode_yaml.vsix',
    resolved: true,
    resolvedByName: 'VsCodePluginDeployerResolver' } ]
local path to deploy on remote instance [ '/tmp/vscode-unpacked/redhat.vscode-camelk.latest.ejskikaxwe.vscode-camelk-0.0.9-86.vsix/extension',
  '/tmp/vscode-unpacked/redhat.vscode-camelk.latest.elastnllsu.vscode-kubernetes-tools-1.0.0.vsix/extension',
  '/tmp/vscode-unpacked/redhat_vscode_yaml.vsix/extension' ]
Backend plug-in "vscode-camelk@0.0.9" from "/tmp/vscode-unpacked/redhat.vscode-camelk.latest.ejskikaxwe.vscode-camelk-0.0.9-86.vsix/extension/out/extension is now available"
Backend plug-in "vscode-kubernetes-tools@1.0.0" from "/tmp/vscode-unpacked/redhat.vscode-camelk.latest.elastnllsu.vscode-kubernetes-tools-1.0.0.vsix/extension/out/src/extension is now available"
Backend plug-in "vscode-yaml@0.5.3" from "/tmp/vscode-unpacked/redhat_vscode_yaml.vsix/extension/out/src/extension is now available"

if refreshing the page, there is an error in browser console log:

root ERROR Failed to load plugins: Error: Request 'getDeployedPluginIds' failed
    at Proxy.<anonymous> (https://static.developers.redhat.com/che/theia_artifacts/theia.3f7e45e….js:1:1789599)
    at e.<anonymous> (https://static.developers.redhat.com/che/theia_artifacts/theia.3f7e45e….js:1:2465936)

In combination of another issue forbidding to see Extension on first load but requiring a refresh as indicated in this comment, it is making it unusable.

Che version

  • latest

Steps to reproduce

  1. Add Workspace
  2. Select "Apache Camel based on SpringBoot
  3. Click "Create and proceed editing"
  4. Go to DevFile
  5. Add in components
  - id: >-
      https://raw.githubusercontent.com/apupier/che-plugin-registry/camelk/v3/plugins/redhat/vscode-camelk/latest/meta.yaml
    memoryLimit: 1G
    type: chePlugin
  1. Open Workspace
  2. wait...
  3. hit refresh
  4. Check browser console log

Runtime

minikube version: v1.3.1
commit: ca60a424ce69a4d79f502650199ca2b52f29e631
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-18T14:36:53Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.2", GitCommit:"f6278300bebbb750328ac16ee6dd3aa7d3549568", GitTreeState:"clean", BuildDate:"2019-08-05T09:15:22Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}

Installation method

  • chectl
    chectl server:start -p minikube -a operator

Environment

  • my computer
    • Windows
    • Linux
    • macOS
@apupier apupier added the kind/bug Outline of a bug - must adhere to the bug report template. label Oct 8, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Oct 8, 2019
@apupier apupier mentioned this issue Oct 8, 2019
Closed
@l0rd
Copy link
Contributor

l0rd commented Oct 8, 2019

@apupier when providing an external link to the meta.yaml you should use reference instead of id :

  - reference: https://raw.githubusercontent.com/apupier/che-plugin-registry/camelk/v3/plugins/redhat/vscode-camelk/latest/meta.yaml
    memoryLimit: 1G
    type: chePlugin

Maybe the error is related to that?

@l0rd l0rd added status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Oct 8, 2019
@apupier
Copy link
Contributor Author

apupier commented Oct 9, 2019

I tried using "reference" instead of "id", I have the exact same behavior

@apupier apupier added status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. and removed status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. labels Oct 9, 2019
@benoitf benoitf added area/editor/theia Issues related to the che-theia IDE of Che status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Oct 9, 2019
@benoitf
Copy link
Contributor

benoitf commented Oct 9, 2019

@apupier is that your che-theia image is using the same theia version than your sidecar image with theia endpoint image running inside ?

@apupier
Copy link
Contributor Author

apupier commented Oct 9, 2019

it was surely due to a mismatch of images.
The Docker image used was build 9 days ago, just when the new protocol was setup. I rebuilt the image and I don't reproduce.

Thanks for the help!

@apupier apupier closed this as completed Oct 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/editor/theia Issues related to the che-theia IDE of Che kind/bug Outline of a bug - must adhere to the bug report template. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@benoitf @l0rd @apupier @che-bot