Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-1310

Workspace activity checker doesn't work for workspace based on "Intellij IDE" editor

XMLWordPrintable

    • False
    • False
    • +
    • Undefined
    • Workaround Exists
    • Hide

      Increase default inactivity timeout to several hours when install CRW, e.g. 5 hours:

      custom-resource-patch.yaml
      spec:
  server:
    customCheProperties:
      CHE_LIMITS_WORKSPACE_IDLE_TIMEOUT: '18000000'
      Show
      Increase default inactivity timeout to several hours when install CRW, e.g. 5 hours: custom-resource-patch.yaml spec: server: customCheProperties: CHE_LIMITS_WORKSPACE_IDLE_TIMEOUT: '18000000'
    • Hide

      Environment:

      • CodeReady deployde by the crwctl with tls and oAuth support
      • OCP 4.5 cluster
      • server image - quay.io/crw/server-rhel8:2.5-4
      • devfile registry image - quay.io/crw/devfileregistry-rhel8:2.5-9
      • plugin regidtry image - quay.io/crw/pluginregistry-rhel8:2.5-12

      Steps to reproduce:

      Expected behavior:
      Workspace has the "RUNNING" status after the "CHE_LIMITS_WORKSPACE_IDLE_TIMEOUT" if during this period any actions were performed inside IDE.

      Observed behavior:
      Workspace has status "STOPPED" after the "CHE_LIMITS_WORKSPACE_IDLE_TIMEOUT" even if actions inside IDE were performed.

      Show
      Environment: CodeReady deployde by the crwctl with tls and oAuth support OCP 4.5 cluster server image - quay.io/crw/server-rhel8:2.5-4 devfile registry image - quay.io/crw/devfileregistry-rhel8:2.5-9 plugin regidtry image - quay.io/crw/pluginregistry-rhel8:2.5-12 Steps to reproduce: Go to the dashboard and create custom workspace using devfile https://github.com/che-incubator/che-editor-intellij-community/blob/master/devfiles/workspace.yaml Wait until workspace with the Intellij Ide editor is started Create project and start worjing with it Pay attention that workspace will be stopped after timeout defined in the "CHE_LIMITS_WORKSPACE_IDLE_TIMEOUT" even if user performs actions inside IDE. Expected behavior: Workspace has the "RUNNING" status after the "CHE_LIMITS_WORKSPACE_IDLE_TIMEOUT" if during this period any actions were performed inside IDE. Observed behavior: Workspace has status "STOPPED" after the "CHE_LIMITS_WORKSPACE_IDLE_TIMEOUT" even if actions inside IDE were performed.

      Workspace activity checker doesn't work for workspace based on "IntelliJ IDE" editor

              vzhukovs-1 Vladyslav Zhukovskyi (Inactive)
              iokhrime Ihor Okhrimenko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: