No idle does not work ?

[batleforc]

Describe the bug

At the moment, the che-machine-exec that provide the .noidle does not work. i've followed #23529 and read the doc https://eclipse.dev/che/docs/stable/end-user-guide/proc_preventing-workspace-idling-for-long-running-commands/ but found a bigger problem. Both CheCode and JetBrainsIdeDevServer relies on che-machine-exec that does not include it.

https://github.com/che-incubator/che-code/blob/main/build/dockerfiles/assembly.Dockerfile#L15 7.56.0
https://github.com/che-incubator/jetbrains-ide-dev-server/blob/main/build/dockerfiles/Dockerfile#L39 7.70.0

And seems to be merged in eclipse-che/che-machine-exec#333 so 7.111 at the earliest

Che version

7.120@latest

Steps to reproduce

1. Create a project with a .noidle on help install or claude.
2. Wait for the idle timeout
3. See workspace closing
4. Search for any log related to the CLI watcher in /checode/entrypoint-logs.txt and found nothing

Expected behavior

For my long lived work to not stop or my helm install to not be stopped.

Runtime

Kubernetes (vanilla)

Screenshots

No response

Installation method

chectl/latest

Environment

Linux

Eclipse Che Logs

Additional context

No response

[batleforc]

Said nothing, i didn't see #23648 for VsCode, but maybe need to update for JetBrains ?

[vrubezhny]

@batleforc You're right, currently #23648 prevents the use of the latest Machine-exec on UBI-based images.

More is that using the latest version of CLI Activitity Tracker included into the latest Machine-exec (not released) couldn't give enough support for the interactive CLIs like the mentioned claude - if used and properly configured, it would track it only as normal long-running CLI (like npm, docker, gradle build, etc), not taking into account that it's an interactive one.

I'd suggest waiting for an upcoming Machine-exec release with auto-CLI activity tracking that the supports both normal long-running CLIs as well as the interactive ones.

You may try it out using the Editor Definition docker image (to be used on DevWorkspace creation instead of a CheCode or a JB's IDEA editors) made for POC: eclipse-che/che-machine-exec#363 (comment) (just note that the mentioned PR isn't a candidate for the upcoming release as there's some more changes to come) - I'm suggesting this Editor Definition to be tested as in this case you (as user) can fully control the CLI Activity Tracking enablement and configuration just via the .noidle configuration file.

See: https://redhat.atlassian.net/browse/CRW-11505 and https://redhat.atlassian.net/browse/CRW-11940 for more details on related upcoming changes.

[batleforc]

Hi @vrubezhny
Thanks for you answer, i had both Jetbrain's ide and VsCode in mind has lot's of our user has both. (the reason why i reopened the issue)

I've read your proposal over the addition to the global CRD, it would resolve most of our worries on this part (the global shutdown and the max process ages) and help keeping a level of health in the cluster.

I will try your pr on my personal time, thanks.

[vrubezhny]

@batleforc Just note that eclipse-che/che-machine-exec#363 is planned to be included to the coming 7.121 while the exposure the configuration to the global CRD is planned for the future (7.122/7.123) releases

[RomanNikitenko]

• che-code uses next machine-exec for the main branch: https://github.com/che-incubator/che-code/blob/main/build/dockerfiles/assembly.Dockerfile#L15
• about release branches: chore: align machine-exec version with che-code version at release che-incubator/che-code#780