Chapter 7. Known issues

There is a known issue affecting the use of IntelliJ IDEA Ultimate IDE on the arm64 architecture. When you start a workspace in the IDE, the following error message appears: "504 Gateway Time-out". There is no workaround available.

There is a known issue with using the Ansible sample on the `arm64`architecture. The Ansible sample fails to start and the following error message appears: "Error creating DevWorkspace deployment: Detected unrecoverable event FailedPostStartHook: PostStartHook failed." There is no workaround available.

There is a known issue where the .NET sample fails to start on the arm64 architecture because there is no quay.io/devspaces/dotnet-90 image available for arm64. There is no workaround available.

There is a known issue affecting workspaces in Dev Spaces deployed to OpenShift Platform 4.18. When you start the workspace, the following error message appears: "Error creating DevWorkspace deployment: Container tools has state ImagePullBackOff".

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.

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.

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.

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.