Chapter 7. Known issues 7.1. Workspaces using JetBrains IDEs ignore idling timeouts There is a known issue with the desktop versions of JetBrains IDEs. Workspaces using these IDEs ignore idling timeouts specified by CheCluster properties such as secondsOfRunBeforeIdling , and secondsOfInactivityBeforeIdling . There is currently no workaround available. Additional resources CRW-8297 7.2. JetBrains editors cause workspace startup failure on IBM Power and IBM Z There is currently a known issue affecting the use of the desktop versions of JetBrains IDEs with IBM Power, and IBM Z architectures. The downloaded JetBrains IDE binaries are not multi-arch, causing workspace startup to fail. There is currently no workaround available. Additional resources CRW-8296 7.3. Workspaces created with ubi9-based samples as a tool container fail to start with JetBrains IntelliJ IDEA (desktop) There's currently a known issue with starting workspaces created with ubi9-based samples (ubi9-minimal, ubi-init, and ubi9) in the desktop version of JetBrains IntelliJ IDEA. The IDE does not load, causing the start of the workspace to fail after a period of time. Currently, there is no workaround available. Additional resources CRW-8294 7.4. Error when re-opening a running workspace in JetBrains IntelliJ IDEA (desktop) There is currently a known issue affecting workspaces running in the desktop version of JetBrains IntelliJ IDEA. If you close the IDE while the workspace is still running, you will receive the following error messages after re-opening the IDE: "There was an error in the connection provider", and "No connection handle was returned". There are multiple workarounds available. Workaround Open the workspace locally using the JetBrains Gateway plugin for Dev Spaces. Restart the workspace. Restart the computer. Additional resources CRW-8292 7.5. Non-admin users can't fetch list of workspaces with the JetBrains Gateway plugin There is currently a known issue affecting workspaces created by non-admin users and the JetBrains Gateway plugin. If you create workspaces in Dev Spaces as a non-admin user and use the same account to access Dev Spaces locally on your computer through the JetBrains Getaway plugin, the fetched list of workspaces will be empty. There is currently no workaround available. Additional resources CRW-8287 7.6. Workspaces using JetBrains IntelliJ IDEA editor fail to start in air-gapped environment There's currently a known issue affecting workspaces using JetBrains Intellij IDEA in an air-gapped environment. If you choose JetBrains IntelliJ IDEA as your editor and try starting a workspace, the workspace startup will fail. A workaround is available. Workaround Whitelist JetBrains editor binary CDN host download-cdn.jetbrains.com . Additional resources CRW-8254 7.7. Issues with starting a new workspace from a URL that points to a branch of a repository that doesn't have a devfile There is a known issue affecting repositories without a devfile.yaml file. If you start a new workspace from a branch of such repository, the default branch (e.g. 'main') is used for project cloning instead of the expected branch. Additional resources CRW-6860 7.8. Refresh token mode causes cyclic reload of the workspace start page There is a known issue when experimental refresh token mode is applied using the CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN property for the GitHub and Microsoft Azure DevOps OAuth providers. This causes the workspace starts to reload the dashboard cyclically, creating a new personal access token on each page restart. The refresh token mode works correctly for 'GitLab' and 'BitBucket' OAuth providers. Additional resources CRW-6859 7.9. Debugger does not work in the .NET sample Currently, the debugger in Microsoft Visual Studio Code - Open Source does not work in the .NET sample. Workaround Use a different image from the following sources: Custom UBI-9 based Dockerfile devfile.yaml Additional resources CRW-3563

Commands: