-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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.
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
Commands are not displayed in the sidecar component #20498
Comments
This problem arises from the code in containers-service.ts#41:
The code tries to match the the name fields from "componentStatus" and "devfile.components". However, the names don't match for plugins: For example if I assign the alias "jsdebug" to the a plugin, the name on componentStatus.name is something like 'jsdebugxyz', while I belive the correct thing would be to have the component name in the |
does it make sense to have a field |
@svor would it be better to rethink this issue in devfile 2.x context? |
we have a customer request for this: https://issues.redhat.com/browse/CRW-2052 |
@tsmaeder could you please clarify a bit why it works for dev component and doesn't work for plugin component. |
Because for non-plugin components, the name is the same in both the both instances: for example, it's "mvn" not "mvnxyz". |
That is how runtime of such a workspace is looks like
Can you explain what is missing? I can't see |
@skabashnyuk re: ComponentStatus maybe @benoitf can shed some light on the mapping of the che server web API and the API here: https://github.com/eclipse-che/che-theia/blob/8e61ae25ca90bdab2bba99a40fe48b6fa97c62ef/extensions/eclipse-che-theia-remote-api/src/common/devfile-service.ts#L15 I'm not familiar with that area of the code, t.b.h. (and there is no doc on those interfaces 🤷 ) However, the problem remains how to map |
hello, maybe the missing important piece of the discussion is that devfileV1 is converted to devfile v2 syntax and then we consume always devfile v2 objects on plug-ins/extensions in CheTheia This might explain why people argue it's devfile v1 and other devfile v2 As a bug is reported on a devfile v1 then it's probably a bug in the converter. Probably need to look at https://github.com/eclipse-che/che-theia/blob/909e6974240a6c137647dafe09dc23a8af7638e0/extensions/eclipse-che-theia-remote-impl-che-server/src/node/che-server-devfile-service-impl.ts#L591 and add a test usecase there: https://github.com/eclipse-che/che-theia/blob/909e6974240a6c137647dafe09dc23a8af7638e0/extensions/eclipse-che-theia-remote-impl-che-server/tests/node/che-server-devfile-service-impl.spec.ts (in any case if there is a bug about a devfile v1 it's located in eclipse-che-theia-remote-impl-che-server implementation) |
this bug is only about devfile v1 |
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
Describe the bug
The Workspace view displays commands only for dev component, but they are not displayed for sidecar plugins.
For example if a devfile contains a component like:
and a command:
This command won't be displayed in the Workspace view.
Che version
7.36@latest
Steps to reproduce
Expected behavior
Python sidecar's command Second command should be displayed in the Workspace view
Runtime
minikube
Screenshots
Installation method
chectl/latest
Environment
Linux
Eclipse Che Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: