Chapter 3. Bug fixes

Starting from this release, there is a dedicated warning message for clusters that are behind a proxy, if you did not add the KUBERNETES_SERVICE_HOST environment variable to the no_proxylist environment variable.

Previously, a sporadic warning message could show up while Cloud Development Environment (CDE) was starting from a raw devfile. The defect has been fixed in this release.

Previously, the DevWorkspace 'storage-type' attribute was temporarily removed when restarting the Cloud Development Environment (CDE) from the local devfile. The defect has been fixed in this release.

Previously, revoking the GitHub token from the dashboard could fail with an "OAuth token for provider GitHub was not found" error message under certain conditions. The defect has been fixed in this release.

Previously, under certain conditions, a "TypeError: Cannot assign to read only property 0 of object `[objectArray]`" error message would appear when navigating to the User Preferences Git Services tab. The defect has been fixed in this release.

Before this release, when you started a Cloud Development Environment (CDE) for a Bitbucket server private repository based on an SSH URL, the start was interrupted with an unexpected warning. The defect has been fixed in this release.

Previously, ServiceAccount token located at the path /var/run/secrets/kubernetes.io/serviceaccount/token was cached on the User Dashboard end and was not refreshed properly. The defect has been fixed in this release.

Regression related to the automatic restart from the local devfile for SSH URLs has been fixed in this release.

Kubeconfig format corruption after switching clusters and restarting the Cloud Development Environment (CDE) has been fixed in this release.

Previously, there was a "Cannot add property controller.devfile.io/bootstrap-devworkspace, object is not extensible" error when you tried to create a workspace with an SSH URL from the Dev Spaces dashboard. This defect has been fixed in this release.

Previously if devEnvironments.persistUserHome.enabled and devEnvironments.persistUserHome.disableInitContainer were both true, and if there was a file in the /home/user directory that would cause a stow conflict, the stow command would still run and fail due to the conflict. With this release, UBI and UDI entrypoint automatically add conflicting files into the /home/tooling/.stow-local-ignore to prevent the stow failure.

When creating new terminals in the Visual Studio Code - Open Source ("Code - OSS") editor with the New Terminal (Select a Container) option, the initial directory was not the current project directory (ex. /projects/<project-name>). This defect has been fixed in this release.

Before this release, there was an issue affecting Visual Studio Code - Open Source ("CODE - OSS") after you upgraded Dev Spaces from version 3.17.0 to 3.18.0. An outdated version of the IDE appeared when you opened a workspace previously created from a sample in Dev Spaces 3.17.0. This issue has been fixed in this release.

Before this release, there was an issue affecting the automatic setup of Git user.name and user.email in the `gitconfig file after you configured your access token (PAT) or OAuth. If you opened User Dashboard > Gitconfig page after PAT or OAuth configuration, you received the following error message: "Author identity unknown." The issue has been solved in this release.