Chapter 3. Bug fixes

Previously, the persistUserHome CheCluster Custom Resource property was not working with the per-workspace storage strategy. The defect has been fixed in this release and now you can use the persistUserHome option with both the per-user and the per-workspace storage strategies.

Find more details about the property in the official documentation.

Before this release, there was a sporadic defect affecting workspace startup after using the "Restart Workspace from local Devfile" functionality from che-code. The following error message would appear: "You can only have 1 running workspace at a time". With this release, the issue is fixed.

Before this release, workspace startup from a Bitbucket Server private repository using OAuth2 failed with the "Repository/Devfile URL is missing" error. With this release, the issue is fixed.

Referencing an editor using che-editor URL parameter could result in a CORS-related network error. The defect has been fixed in this release.

Previously, when a developer created a Personal Access Token from the User Preferences, there was no validation of the Git URL. If the URL was invalid it led to login and dashboard usage issues due to a java.net.URISyntaxException: Illegal character exception. To resolve the access issue, you had to manually intervene with the generated secret. The defect has been fixed in this release.

Before this release, trailing spaces were not trimmed in the input field of the "Import from Git" widget resulting in the "URL or SSHLocation is not valid" error.

Previously, the Revoke OAuth button continued to be active after the execution. The defect has been fixed in this release.