-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
None
-
False
-
Resolving this issue as the original problem has been fixed. Container contributions epic can be tracked [upstream](https://github.com/eclipse/che/issues/21736)
-
Rejected
-
Workaround Exists
-
- The workspace starts successfully if the editor is Theia or IntelliJ
- The workspace starts successfully if cpuLimit/Request uses the m unit (.e.g. cpuLimit: '1000m')
schemaVersion: 2.1.0
metadata:
name: java-guestbook
components:
- name: tools
container:
image: quay.io/devfile/universal-developer-image:ubi8-0e189d9
cpuLimit: '1'
Using a Devfile such as the one above and using the URL parameter `che-editor=che-incubator/che-code/insiders` the following error is returned (c.f. the screenshot attached to the issue):
Getting workspace detail data failed. Failed to start the workspace java-guestbook, reason: 1 error occurred: * error parsing cpuLimit requirement for component tools: quantities must match the regular expression '^([+-]?[0-9.]+)([eEinumkKMGTP]*[-+]?[0-9]*)$'
This issue is related to che-code DevWorkspace Handler and can be fixed there but the devworkspace handlers are supposed to be retired with the introduction of DevWorkspaces' containersContributions.
Rather than fixing che-code DevWorkspace Handler we are going to stop using it in the Dashboard and add containersContributions in the IDE definitions in the plugin registry.
UPDATE: this issue has been addressed upstream before the introduction of containersContributions
