-
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
Che-Theia with DevWorkspaces sometimes overwrites the DevWorkspace in-cluster object #21244
Comments
I notice that I cannot restart the devworkspace after adding a new remote from the editor. After running these steps:
I'm not able to start the devworkspace again: To add remotes, a workaround can be to add remotes in the Example: To add remote
|
Moving to P1 as it seems this can occur whenever Theia updates the DevWorkspace, and if it occurs the workspace ends up in a confusingly broken state that is hard to repair manually. |
I continue to encounter this issue randomly; fixing it is complicated as the flattened DevWorkspace is not intended for manual editing and in some cases results in my workspace failing to start consistently. |
To make it clear:
|
Describe the bug
Theia sometimes applies the contents of
$DEVWORKSPACE_FLATTENED_DEVFILE
to the cluster, overwriting the cluster object with its flattened equivalent. This breaks the connection between the workspace and any plugins defined in DevWorkspaceTemplates.This has the further issue that it's harder to e.g. change the editor in the DevWorkspace as the contents of e.g. the Theia plugin are included among the original components.
Che version
next (development version)
Steps to reproduce
che-url/#https://github.com/che-samples/golang-example/tree/devfilev2
ctrl+shift+p
toGit: Add Remote...
and enter e.g.https://github.com/golang/example.git
Expected behavior
If Theia modifies the Devfile, it should use
$DEVWORKSPACE_ORIGINAL_DEVFILE
as a base.Runtime
OpenShift
Screenshots
No response
Installation method
chectl/next
Environment
Linux
Eclipse Che Logs
No response
Additional context
Sample diff from following the reproducer above
The text was updated successfully, but these errors were encountered: