Port @eclipse-che/theia-activity-tracker

[dkwon17]

This PR ports eclipse-che-theia-activity-tracker to che-code.

There were two main differences with https://github.com/eclipse-che/che-theia/tree/main/extensions/eclipse-che-theia-activity-tracker and the VS Code plugin introduced in this PR:

Tracking

Instead of front-end tracking like in che-theia, this PR tracks the following VS Code events using the extension API:

• vscode.workspace.onDidChangeTextDocument
• vscode.window.onDidChangeActiveTextEditor
• vscode.window.onDidChangeTextEditorSelection
• vscode.window.onDidChangeTextEditorViewColumn
• vscode.window.onDidChangeWindowState
• vscode.window.onDidChangeTerminalState
• vscode.window.onDidChangeActiveTerminal

Determining the che-machine-exec url

Instead using an EndpointService to determine the machine-exec port like for che-theia, this PR relies on an environment variable set by entrypoint-volume.sh which executes the machine-exec binary. The environment variable is read here.This was done because for Che-code, because for che-code, che-machine-exec is not running in its own container.

To test this PR:

Since there is no idling set up for Che-code at the moment, to test this PR, create a workspace with this che-code image: quay.io/dkwon17/che-code:idle. Here is the editor devfile v2: https://gist.githubusercontent.com/dkwon17/1a96b69643260c9af23553f740132157/raw/72fb81012aa03618490b91cf887ff6a5cd12a889/gistfile1.txt.

For example, to start a golang che sample workspace, go to:

{CHE_HOST}/#https://github.com/che-samples/golang-example/tree/devfilev2?che-editor=https://gist.githubusercontent.com/dkwon17/1a96b69643260c9af23553f740132157/raw/72fb81012aa03618490b91cf887ff6a5cd12a889/gistfile1.txt

When the workspace is running, the tools container of the workspace pod should log /activity/tick POST messages when interacting with the che-code editor. Requests are sent once a minute at most to che-machine-exec:

Signed-off-by: David Kwon dakwon@redhat.com

[dkwon17]

This PR is for eclipse-che/che#21513

[dkwon17]

This was done so that the VS Code extension could determine the machine exec port

[github-actions]

Pull Request images published ✨
image: quay.io/che-incubator-pull-requests/che-code:pr-65-amd64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-65-dev-amd64

[github-actions]

Pull Request images published ✨
image: quay.io/che-incubator-pull-requests/che-code:pr-65-amd64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-65-dev-amd64

[github-actions]

Pull Request images published ✨
image: quay.io/che-incubator-pull-requests/che-code:pr-65-amd64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-65-dev-amd64

[github-actions]

Pull Request images published ✨
image: quay.io/che-incubator-pull-requests/che-code:pr-65-amd64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-65-dev-amd64

[azatsarynnyy]

works well - the endpoint is requested regularly as expected

[dkwon17]

Thank you for the review @azatsarynnyy , I've made the changes

[azatsarynnyy]

Thank you @dkwon17 for this contribution.

[github-actions]

Pull Request images published ✨
image: quay.io/che-incubator-pull-requests/che-code:pr-65-amd64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-65-dev-amd64

[top1436]

@dkwon17 Thank you for your explanation.

"devEnvironments.secondsOfInactivityBeforeIdling" is right. my bad...

If che-code built-in extension checks "Activity", Another IDE cannot be applied by this option? ex) IntelliJ

In my exprience, Intellij is also applied this option and it stopped Intellij workspace after the seconds.

In IntelliJ IDE, Is it implemented a diffrent way?

[azatsarynnyy]

Hi @top1436
JetBrains editors in Che have no support yet for sending the user's activity to the machine-exec component that stops the workspaces.

[top1436]

@azatsarynnyy hi!
you mean in jetbrains editor, always inactivity state and workspace always stops after secondsOfInactivityBeforeIdling?

[azatsarynnyy]

@top1436 correct, if I haven't missed anything )

[top1436]

@azatsarynnyy
thank you! I think it needs to be fixed. Is there any plan to develop jetbrain plugin as che-code does?

[azatsarynnyy]

@azatsarynnyy thank you! I think it needs to be fixed. Is there any plan to develop jetbrain plugin as che-code does?

There're no plans to invest in the current (Projector-based) implementation of JetBrains editors for Che.
But we're going to look at JetBrains Gateway instead (eclipse-che/che#21412)