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

How to contribute #21401

Open
1 task done
tsadigovAgmail opened this issue May 14, 2022 · 8 comments
Open
1 task done

How to contribute #21401

tsadigovAgmail opened this issue May 14, 2022 · 8 comments
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sprint/current status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach

Comments

@tsadigovAgmail
Copy link

tsadigovAgmail commented May 14, 2022

Summary

I want to know how run che in debug mode and see internal working.

This description is old and does not work, commands do not exist, dev file links are broken
https://github.com/eclipse/che/blob/master/CONTRIBUTING.md

Relevant information

Just provide a plain exmplanation how your development environment is set up , so I can mimick it.

Related sub-tasks

@tsadigovAgmail tsadigovAgmail added the kind/question Questions that haven't been identified as being feature requests or bugs. label May 14, 2022
@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 May 14, 2022
@tolusha
Copy link
Contributor

tolusha commented May 16, 2022

Hello @tsadigovAgmail
The steps are the following:

  1. Update CheCluster CR: spec.server.cheDebug: true
  2. Forward debug port: chectl server:debug
  3. Connect to a localhost:8000 to debug a remote Che server

@ibuziuk ibuziuk added status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels May 16, 2022
@tsadigovAgmail
Copy link
Author

tsadigovAgmail commented May 16, 2022

Thanks @tolusha for the answer. I am sure for a gifted person like you this might be the answer.
But for non gifted person like me this seems to be not enough. So I cant agree @ibuziuk here.
I dont see how it provides alternative information to this doc https://github.com/eclipse/che/blob/master/CONTRIBUTING.md

Which subproject is this endpoint representing? Which platform is it built on? Even maybe how you set up the IDE?
I think kind of onboarding instructions would be great.
How do you provide an environment to a new member?

@ibuziuk ibuziuk mentioned this issue May 17, 2022
49 tasks
@tsadigovAgmail
Copy link
Author

tsadigovAgmail commented May 17, 2022

related issue

@tsadigovAgmail
Copy link
Author

tsadigovAgmail commented May 17, 2022

CONTRIBUTING.md file mentiones this
$ chectl workspace:start -f https://raw.githubusercontent.com/eclipse/che-theia/main/devfiles/che-theia-all.devfile.yaml or https://<CheInstance>/f?url=https://raw.githubusercontent.com/eclipse/che-theia/main/devfiles/che-theia-all.devfile.yaml

as mentionned above the command does not exist - chectl workspace:start
But I can try using the devfile from my che installation. And there I see the devfile link is broken.
`
Searching in commit history I found the file and also noticed generic change where XYZ-all.devfile.yaml files renamed to XYZ-dev.devfile.yaml which is not reflected in CONTRIBUTING.md and .repositories.yaml files.

So @Divine1 you may try just replacing all->dev in devfile names and try that way.
Lets see how it goes from that point.

https://<CheInstance>/f?url=https://raw.githubusercontent.com/eclipse/che-theia/main/devfiles/che-theia-dev.devfile.yaml

@tsadigovAgmail
Copy link
Author

Here is what I got, I am trying the commands with varying degree of success. Will go over doc again to see if I need to do any setup.

image

@Divine1
Copy link

Divine1 commented May 18, 2022

@tsadigovAgmail thank you.

normally i would like to do trail and errorapproach but i'm stuck with another issue related to setting up eclipse che on k8s cluster, the issue detail is present in this link #21404 .

i will verify your recommended approach once i find solution for the issue (#21404)

@tsadigovAgmail
Copy link
Author

related issue

@ibuziuk ibuziuk mentioned this issue Jun 8, 2022
64 tasks
@ibuziuk ibuziuk mentioned this issue Jun 28, 2022
68 tasks
@ibuziuk ibuziuk mentioned this issue Jul 19, 2022
51 tasks
@ibuziuk ibuziuk added sprint/current kind/task Internal things, technical debt, and to-do tasks to be performed. and removed sprint/next kind/question Questions that haven't been identified as being feature requests or bugs. labels Jul 19, 2022
@ibuziuk ibuziuk mentioned this issue Aug 5, 2022
67 tasks
@ibuziuk ibuziuk added the kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. label Aug 9, 2022
@che-bot
Copy link
Contributor

che-bot commented Apr 22, 2023

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 22, 2023
@che-bot che-bot closed this as completed Apr 29, 2023
@tolusha tolusha added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 1, 2023
@tolusha tolusha reopened this May 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sprint/current status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach
Projects
None yet
Development

No branches or pull requests

5 participants