Release Notes

Public

7.0.16.2613: Sep 25 2018

New

Print ServerStats every 10 minutes instead of every 30 seconds. This is the information in the log dumping memory usage, process info and more. It was creating 3 million lines per hour on some big customers so we decided clean some of the info. No more info about caches is dumped.

New

All clients: Added macOS 10.14 Mojave support!

Warning: We noticed that there might be graphical issues at this point regarding the Dark Theme. While we're on it, you can run /Applications/PlasticSCM.app/Contents/MacOS/PlasticSCM directly, which should display everything correctly.

New

We detected on a client running a server that uses a MySQL backend, that the MySQL fails under heavy load with unexpected errors (like saying that an existing column doesn't exist).

When those errors happen reading the license info, the server is terminated as the license info is corrupted.

Now the server will no longer shutdown when the license info is corrupted. It will inform the client that the operation cannot be done because the license info is corrupted but the server will continue running.

We also protect the license info from unexpected backend issues, so the license info should not be corrupted anymore.

New

macOS/linux GUI: Diff viewer: When clicking a line involving a difference, the diff navigation counter is updated. This allow navigate the differences by clicking in the diff's textboxes, and not only using the navigation buttons (first, previous, next, last).

Bug

WebAdmin: The "License token" text box doesn't show the whole token in some cases because of the width of the box. Fixed.

Bug

Semantic SCM: our semantic parsers (for Java and C++ languages) did not work with Java version 10 because of the way we checked that the correct JVM version was installed. Fixed.

Bug

Server: The license auto-renewal using license tokens wasn't working after our website migration of 2018-09-18. Our new website required TLSv1.2, not enabled in .NET Framework apps by default. We manually added TLSv1.1 and TLSv1.2 support in our server process, which should make the auto-renewal work again!