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

[UD] CHE samples can't start with IntelliJ IDEA #22515

Closed
olexii4 opened this issue Sep 15, 2023 · 4 comments · Fixed by eclipse-che/che-dashboard#923
Closed

[UD] CHE samples can't start with IntelliJ IDEA #22515

olexii4 opened this issue Sep 15, 2023 · 4 comments · Fixed by eclipse-che/che-dashboard#923
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.

Comments

@olexii4
Copy link
Contributor

olexii4 commented Sep 15, 2023

Describe the bug

CHE samples can't start with IntelliJ IDEA because of the relative link:

links: {
  v2: "https://github.com/che-samples/apache-camel-k/tree/main",
  devWorkspaces: {
    che-incubator/che-idea/next: "/devfiles/apache-camel-k/devworkspace-che-idea-next.yaml",
  ...
}
...

Che version

7.74@latest

Steps to reproduce

  1. Deploy Eclipse CHE.
  2. Open Create Workspace.
  3. Create a new workspace from the samples from che-devfile-registry with IntelliJ IDEA.
  4. A 404 page not found error message will appear.

Expected behavior

UD should resolve relative links correctly. We should be able to create a new workspace from samples with IntelliJ IDEA.

Runtime

minikube

Screenshots

Знімок екрана 2023-09-15 о 16 16 12
Знімок екрана 2023-09-15 о 16 16 30

Installation method

chectl/next

Environment

macOS

Eclipse Che Logs

No response

Additional context

No response

@olexii4 olexii4 added the kind/bug Outline of a bug - must adhere to the bug report template. label Sep 15, 2023
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 15, 2023
@ibuziuk ibuziuk added the severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. label Sep 15, 2023
@ibuziuk
Copy link
Member

ibuziuk commented Sep 15, 2023

Looks like similar to what @svor opened this week for 3.9 https://issues.redhat.com/browse/CRW-4853

@svor
Copy link
Contributor

svor commented Sep 15, 2023

Looks like similar to what @svor opened this week for 3.9 https://issues.redhat.com/browse/CRW-4853

yes, I'm working on the fix for upstream as well

@svor
Copy link
Contributor

svor commented Sep 15, 2023

@olexii4
Copy link
Contributor Author

olexii4 commented Sep 15, 2023

@ibuziuk, @svor It could be fixed in different ways. I am sure that supporting the ability to use relative links is still important. I have created a PR.

@olexii4 olexii4 removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants