Chapter 3. Bug fixes

Before this update, including a Bitbucket Personal Access Token (PAT) in workspaces on a OpenShift Dev Spaces installation with Bitbucket OAuth integration resulted in a "Backend is not available" error message. With this update, it’s possible to log in to the User Dashboard without issues.

From time to time, you could encounter multiple "401 Unauthorized" errors when opening a workspace with the Visual Studio Code - Open Source ("Code - OSS") editor. The defect has been fixed in this release.

Previously, after configuring container registries (quay.io, docker.io, etc.) from the User Dashboard and starting a workspace, you were not automatically logged into the configured registries. The defect has been fixed in this release.

Previously, strict validation prevented workspace creation from URLs such as user1@repository.example.com:/home/user1/repositories/myrepo.git. The defect has been fixed in this release.

In this release, the parsing error of the .code-workspace file that contains extra commas has been fixed:

{
	"folders": [
		{
			"name": "che-code",
			"path": "/projects/che-code",
		},
	]
}

An empty project used to be displayed in the project tree of the Visual Studio Code - Open Source ("Code - OSS") editor, if several starter projects were defined in the devfile. The defect has been fixed in this release.

Before this release, if GitHub OAuth configuration secrets were set up for both SaaS and Enterprise, and if the authorization agreement was accepted for only one of the providers, the authorization status was duplicated for both providers on the Git Services tab. The defect has been fixed in this release.

Before this release, you could encounter many processes labeled <defunct> in the workspace container while working in Visual Studio Code - Open Source ("Code - OSS").

Before this release,GOPATH and GOCACHE environment variables were not correctly set when running dedicated commands defined in a devfile. This resulted in failed tasks, for tasks such as the go build task. The defect has been fixed in this release.

Previously, mounting files using a ConfigMap, Secret, or PVC that conflict with stow directory files resulted in the stow command failure during the execution of the $HOME directory persistence. The defect has been fixed in this release.