Chapter 3. Bug fixes


3.1. Microsoft Visual Studio Code - Open Source che-resource-monitor extension not working

Before this update, the HOSTNAME environment variable could be overridden. This resulted in the Microsoft Visual Studio Code - Open Source extension che-resource-monitor not working properly. With this update, the HOSTNAME environment variable is copied to the DEVWORKSPACE_POD_NAME environment variable before the IDE is launched to create a backup source of the relevant data.

Additional resources

3.2. Workspaces from public GitHub Enterprise Server repositories fail to start

Before this update, workspaces from public GitHub Enterprise Server repositories failed to start if no OAuth or Personal Access Token (PAT) was configured. With this update, the issue is fixed.

Additional resources

3.3. Accessing OpenShift API from workspace failed

Before this update, accessing OpenShift API from a workspace in a disconnected cluster failed with the following error message: "HttpError: HTTP request failed". With this update, the issue is fixed.

Additional resources

3.4. GitHub Copilot could not connect to server

Before this update, the GitHub Device Authentication was not available in the command palette. This resulted in the following GitHub Copilot error: "Copilot could not connect to server. Extension activation failed: "Request failed with status code 401". With this update, the issue is fixed.

Additional resources

3.5. New projects lost after a workspace restart

Before this update, the Microsoft Visual Studio Code - Open Source launcher was adding projects from devfile.yaml to .vscode-workspace configuration file only during the initial workspace startup. If you added a new project (or dependent project) to the devfile and restarted the workspace using the "Restart Workspace from Local Devfile" option, the new project was not added to the configuration file. This resulted in you not seeing the project even though all the projects were cloned in the /projects folder. With this release, projects are correctly updated in the .vscode-workspace configuration file.

Additional resources

3.6. BitBucket OAuth 1.0 not displayed in Git Services tab

Before this update, BitBucket OAuth 1.0 was not displayed in the Git Services tab. With this update, the issue is fixed.

Additional resources

3.7. Custom Resource defaultPlugins not applied during workspace startup

Before this update, defaultPlugins defined in the Custom Resource were not applied during workspace startup. With this update, the issue is fixed. You can also add additional sidecar plugins using a devfile.yaml reference:

     devEnvironments:
       - editor: che-incubator/che-code/insiders
         plugins:
            - >-
              https://example.com/devfile.yaml

Additional resources

Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.