Chapter 3. Bug fixes


Before this update, enabling the persistence of the home directory broke the Universal Developer image home directory, PATH, and environment variables. With this update, this issue is fixed.

Additional resources

Before this update, re-opening an existing workspace resulted in a "No PersonalAccessTokenFetcher configured" error message. With this update, the token is refreshed on a workspace restart.

Additional resources

Before this update, rejecting SCM authorization led to an error appearing at workspace start. With this update, the workspace starts correctly.

Note

If you reject the authorization, you can not use git push in the workspace without an additional setup.

Additional resources

Before this update, an "Unauthorized" error message would occasionally appear at the 'Open IDE" phase of the workspace start. With this update, the issue is fixed.

Additional resources

Before this update, the "Bearer Token Authorization" error would occasionally appear in the dashboard. With this update, retry request implementation solves the issue.

Additional resources

Before this update, it was not possible to start a workspace based on the Microsoft Azure DevOps Git repositories with white space characters in the URL. With this update, the issue is fixed.

Additional resources

Before this update, builds would fail because of missing common tooling config directories. With this update, the following directories are pre-created in the default UDI with the correct permissions allowing users to write into them from the workspace:

  • Maven: /home/user/.m2/
  • Pip: /home/user/.config/pip/
  • Cargo: /home/user/.cargo/
  • PHP: /home/user/.composer/
  • .NET: /home/user/.nuget

Additional resources

Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

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.

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 Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top