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.

Sign up for GitHub

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

Jump to bottom

Che-Code dogfooding flow requires fixes #21215

Closed
Tracked by #21745
azatsarynnyy opened this issue Feb 23, 2022 · 3 comments
Closed
Tracked by #21745

Che-Code dogfooding flow requires fixes #21215

azatsarynnyy opened this issue Feb 23, 2022 · 3 comments
Assignees
@azatsarynnyy
Labels
area/editor/vscode Issues related to the Code OSS editor of Che kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. sprint/current
Milestone
7.56

Comments

@azatsarynnyy
Copy link
Member

Is your task related to a problem? Please describe

There's a devfile for running Che-Code in Che, but it is not adapted for dogfooding.

  1. When running yarn watch command, the process is killed with the error Visual Studio Code is unable to watch for file changes in this large workspace.
  2. When running yarn build command, the Che-Code backend is restarted.

Describe the solution you'd like

  1. Need to adapt the Che-Code development image to allow yarn watch mode, by increasing the max_user_watches limit.
    See https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc
  2. Need to investigate how to fix building Che-Code in a dev container.

Describe alternatives you've considered

No response

Additional context

No response
@azatsarynnyy azatsarynnyy added kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. team/editors area/editor/vscode Issues related to the Code OSS editor of Che labels Feb 23, 2022
@azatsarynnyy azatsarynnyy mentioned this issue Feb 23, 2022
Closed
4 tasks
@azatsarynnyy azatsarynnyy added this to the 7.45 milestone Feb 23, 2022
@benoitf benoitf modified the milestones: 7.45, 7.46 Mar 17, 2022
@azatsarynnyy azatsarynnyy removed this from the 7.46 milestone Apr 19, 2022
@azatsarynnyy
Copy link
Member Author

Some fixes related to the dogfooding flow were contributed in che-incubator/che-code#113

@azatsarynnyy
Copy link
Member Author

I haven't met this issue for a while. We need to check if it still requires fixing the dogfooding flow or if it is not relevant anymore.

@azatsarynnyy azatsarynnyy changed the title Che-Code dogfooding devfile Che-Code dogfooding flow requires fixes Oct 11, 2022
@azatsarynnyy azatsarynnyy mentioned this issue Oct 11, 2022
Closed
67 tasks
@azatsarynnyy azatsarynnyy added this to the 7.56 milestone Oct 12, 2022
@azatsarynnyy azatsarynnyy self-assigned this Oct 12, 2022
@azatsarynnyy
Copy link
Member Author

I tested Che-Code Devfile by running different resource-consuming commands, like build, and watch. I haven't observed the issues detected earlier. All commands work well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@azatsarynnyy azatsarynnyy

Labels
area/editor/vscode Issues related to the Code OSS editor of Che kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. sprint/current
Projects
None yet
Milestone
7.56
Development

No branches or pull requests
3 participants
@benoitf @ibuziuk @azatsarynnyy