Release Notes

All platforms - PlasticX, GluonX: Fixed issues with Turkish language

When the system language was set to Turkish, there was some issues like unhandled exceptions and bad arrangement of controls in the GUI.

We fixed this issue, and now everything works in the same way, regardless of the system language.

All platforms - PlasticX: Fix subviews close button not visible

In PlasticX, when shrinking a subview (for example, annotate view), text header would eventually hide the close button

We fixed this issue in all subviews, close button won't disappear anymore. Also, text trimming was added to the header text.

Cloud Server: Backups could block access to a repository indefinitely.

When the Plastic SCM server puts a repository in read-only mode before backing it up, it first stalls new write operations and then waits for already running write operations to finish. There is a long-running read operation that was wrongly identified as a write operation. Because that long-running operation could be active for days, the server was unable to finish the repository backup, while still rejecting new write operations.

This is now fixed. First of all, this long-running operation is now correctly identified as a read operation, so it doesn't prevent the backup of the repository. And to prevent something like this from happening in the future, the server now has timeouts when waiting for write operations to end.

Plastic, PlasticX: Fixed users & group resolution on permissions working with multiple servers

The permissions dialog resolved the users and groups on the default server (the one used to configure the server). When the permissions dialog was shown from a different server and that server used an Active Directory authentication, the user and groups were not properly resolved. The SID was shown instead. Now, the users and group names are correctly shown.

All clients: find owner='me' condition works fine with multiple servers.

The shelve view didn't show your shelves in the workspaces that pointed to a different server than the default one (the default server is the one set in the client configuration). It happened only when the servers have different authentications.

The problem was that owner='me' condition was wrongly resolved against the default server. Now, it's properly resolved on the query target server.