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.

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

Definition of the Che-Code editor in the ./che/che-editor.yaml file is ignored #22879

Closed
RomanNikitenko opened this issue Mar 14, 2024 · 12 comments · Fixed by eclipse-che/che-dashboard#1079
Assignees
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.

Comments

@RomanNikitenko
Copy link
Member

RomanNikitenko commented Mar 14, 2024

Describe the bug

Editor definition in ./che/che-editor.yaml is ignored:

  • I defined editor image here, so quay.io/devspaces/code-rhel8:3.12 should be used as an editor image
  • but it uses quay.io/che-incubator/che-code:insiders instead

Che version

7.83.0-SNAPSHOT

Steps to reproduce

  1. Go to the dashboard => Create Workspace => Import from Git
  2. Set Git repo URL: https://github.com/RomanNikitenko/web-nodejs-sample/tree/ubi9-devspaces-editor
  3. Click Create & Open
  4. Go to the Openshift console and check what image is used for the che-code-injector container

Expected behavior

Image defined for the che-code-injector component in the ./che/che-editor.yaml file should be used as an editor image.

Additional context

I reproduced it on the dogfooding instance

@RomanNikitenko RomanNikitenko added kind/bug Outline of a bug - must adhere to the bug report template. area/dashboard severity/P1 Has a major impact to usage or development of the system. labels Mar 14, 2024
@dmytro-ndp
Copy link
Contributor

dmytro-ndp commented Mar 14, 2024

@RomanNikitenko : thanks for reporting.

There is Che 7.83.0-SNAPSHOT on Che dogfooding instance for a few weeks already.
Are you sure it's Eclipse Che 7.82 issue, not Eclipse Che Next?

@RomanNikitenko
Copy link
Member Author

@dmytro-ndp
you are right, I've changed it, thank you!

@akurinnoy
Copy link
Contributor

Hi @RomanNikitenko ,

The che-server cannot properly resolve the link you provided because of the query parameter ...?rgh-link-date=2024-03-14T20%3A54%3A01Z. In this case, it resolves the devfile from the main branch.
As a workaround, you can use the repo link without a search param (https://github.com/RomanNikitenko/web-nodejs-sample/tree/ubi9-devspaces-editor) as it works as expected.

@RomanNikitenko
Copy link
Member Author

@akurinnoy
could you clarify where did you find the query parameter in my link?
I just put https://github.com/RomanNikitenko/web-nodejs-sample/tree/ubi9-devspaces-editor to the Git Repo URL field on the dashboard...

@akurinnoy
Copy link
Contributor

@RomanNikitenko

Screen.Recording.2024-03-15.at.10.33.01.mov

@RomanNikitenko
Copy link
Member Author

@akurinnoy
did you try to follow steps to reproduce?

@RomanNikitenko
Copy link
Member Author

dashboard_regression.mp4

@RomanNikitenko
Copy link
Member Author

@RomanNikitenko

Screen.Recording.2024-03-15.at.10.33.01.mov

I don't have any params like ...?rgh-link-date=2024-03-14T20%3A54%3A01Z in my reference on my side.
It would be nice if someone could check that reference to detect if a problem with the link on my side or on your side.

@akurinnoy
Copy link
Contributor

@RomanNikitenko

I don't have any params like ...?rgh-link-date=2024-03-14T20%3A54%3A01Z in my reference on my side.
It would be nice if someone could check that reference to detect if a problem with the link on my side or on your side.

I took a closer look, and it was added on my side by a browser extension, so I'm sorry for misleading you.

@akurinnoy
Copy link
Contributor

The introduction of the Editor Selector panel (eclipse-che/che-dashboard#1055) changed which editor is applied to a new workspace. After some discussions, we decided to do it as follows:

  • when the editor selector panel (Choose an Editor) is opened, the selected editor will override the editor definition in the factory repo;
  • when the editor definition panel (Use an Editor Definition) is opened and the fields are empty the editor definition in the factory repo will be applied.

So the workaround in your case should be as follows:

  • in the Editor Selector panel switch to Use an Editor Definition
  • paste the git repo URL
  • and click Create & Open

@akurinnoy
Copy link
Contributor

@RomanNikitenko,

At the moment @olexii4 is working on the issue for improving the Import from Git widget [1]. It looks like a good place to discuss changes in the UX.

[1] #22816

@RomanNikitenko
Copy link
Member Author

RomanNikitenko commented Mar 15, 2024

Thank you for the clarification - now I understand how it works.

At the same time, from my point of view, it's not obvious:

  • when the editor selector panel (Choose an Editor) is opened, the selected editor will override the editor definition in the factory repo;
  • when the editor definition panel (Use an Editor Definition) is opened and the fields are empty the editor definition in the factory repo will be applied.

Choose an Editor is open by default, but I don't want to select it - editor is defined in my repo (./che/che-editor.yaml) - I don't want to override it - how I can unselect it?
it looks like I should open Use an Editor Definition - but again - there are two fields that I don't need to define - editor is defined in my repo (./che/che-editor.yaml)...
so - I should open Use an Editor Definition and put nothing there to get editor definition that I already have in my repo (./che/che-editor.yaml) - this step is not obvious as for me...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants