RomanNikitenko
RomanNikitenko
I think the cause of the problem is: - `che-remote` extension has `axios` dependency - `che-remote` extension has `devworkspace-generator` dependency which also depends on the `axios` library - `typescript` "thinks"...
I've changed the severity as the Dev Sandbox is considered as a dogfooding environment
Tested 15 GiB Build failed as well...
I wanted to check the full development cycle for the che-code on Developer Sandbox but I faced a problem on the `npm install` step: I created an issue for that...
Actually, it's not a bug, it is not supported on the `devworkspace-operator` level. https://github.com/devfile/devworkspace-operator/blob/main/docs/unsupported-devfile-api.adoc thanks @ibuziuk for clarifying that!
> but it was not shown in the existing one could you share version of the editor? `Help` => `About`
@tolusha please take a look
@AObuchow it's possible to create a workspace from a `raw` devfile, like https://raw.githubusercontent.com/RomanNikitenko/web-nodejs-sample/refs/heads/testPR/devfile.yaml But I agree about > It's unintuitive how giving the direct path to a devfile in a...
I can not reproduce the problem using editor image built based on https://github.com/che-incubator/che-code/pull/547. So, the problem will be fixed by https://github.com/che-incubator/che-code/pull/547
@AObuchow @dkwon17 so, if I understand correctly, the suggestion is - exclude the command from the devfile task list using hard-coded id. correct?