Release Notes

Public

8.0.16.3816: Dec 05 2019

New

Windows, Linux - Plastic: We made the server combo box on the repository (and Cloud) view wider, so it shows long server address without truncating.

New

All platforms - Plastic: Did you run into some cryptic error messages such as "find is not supported for object '19'" or "The method CreateCodeReviewComment is not supported"? It's likely coming from your outdated server! It doesn't support the new code review comment, but your shiny, up-to-date client does. We improved that so the client will output readable messages to let you that you need to upgrade your server.

New

Windows - Gluon: Incoming changes: the context menu for the new 'Incoming changes" view is now available.

It allows you to perform the following operations:

* Merge selected conflicts.

* Merge selected files keeping source.

* Merge selected files keeping destination.

* Diffs yours with incoming.

* Diff incoming changes.

This feature is experimental. You need to manually activate it by adding the following line to the client.conf configuration file.

On Windows, you can find it in %LocalAppData%\plastic4\client.conf:

<EnableGluonIncomingChanges>yes</EnableGluonIncomingChanges>

New

All platforms, Server: We made the server more robust by fixing a couple of potential problems when timeouts happen.

1) Now, if the server detects a timeout while reading a request, it will close the connection. Before this change it kept the connection open and continued reading - which could lead to strange readings and logs. Not critical, but it is better now.

2) The server could abandon connections that could stay idle until the client closed them. Now this is fixed. We are not sure this was ever find in production.

New

All platforms - Plastic & Gluon: Diffing files with an external tool is now faster. This applies to diffing 2 revisions of a file from the item history, file conflicts during a mergeā€¦

This boost in performance comes from optimizing server calls. There was one in particular that could take even a few seconds when working with big trees (i.e. more than 100k items) in a server that uses a SQL-based backend. The server doesn't execute those calls anymore in this scenario.

By the way, we recommend you to migrate your SQL backend to our Jet backend! It's really faster and our recommended choice. Take a look at 'The story of Jet: Plastic's super-fast repo storage'.

New

Windows - Plastic: We improved the 2D revision tree for revisions added in merge sources. Those displayed blank diagrams, not very useful. They'll now load the added revision and its related changes, just like any other revision in the merge!

New

All platforms - Server: Socket receive timeout now defaults to 10 seconds.

In case you need to change it: edit remoting.conf configuration file located in the server directory and make sure your line looks like this:

channel type="PlasticPipe.Remoting.Tcp.PlasticTcpChannel, plasticpipe" port="8084" name="normal" socketReceiveTimeout="15000"

To increase to 15 seconds: socketReceiveTimeout="15000"

To make it wait forever: socketReceiveTimeout="-1"

We added this to make the server more robust in case of connection problems.

Bug

All platforms - Plastic & Gluon: The embedded diff/content view in the Pending Changes View sometimes failed with the error Cannot download revision XXX from server: Data cannot read/write to Plastic Cloud. There was an authentication issue.... The error appeared when you changed the selected change, which triggered the diff/content refresh. It happened if your workspace pointed to a cloud repository and you kept open the Pending Changes View for 1 day or longer.

Bug

Windows - Plastic Proxy: When you upgrade the Proxy using the installer, it removes the old version before copying the new one. But it was removing configuration files by mistake too! In particular, plasticcached.conf, plasticcached.remoting.conf, and plasticcached.remoting.conf . This caused losing settings such as the cache size or directory. It is now fixed!

Bug

All platforms - Server. SQL backends: Checkin operations could fail with the error The object is currently locked.... It appeared when you or another user interrupted a checkin operation previously (e.g. killing the Plastic client) in the middle of the confirm step. This happened because the server couldn't detect the original operation as abandoned. Now it's fixed.

The same problem could also affect replication operations.

Oh, and by the way, this error only affects server versions 8.0.16.3766 or higher.

Bug

Windows - Plastic: We disabled the two history-related items in the workspace explorer context menu, applying only to added items. It doesn't make a lot of sense to display the history of items you are about to add, right?