Release Notes 2017.1
The following issues were addressed in version 2017.1:
1097613 -- Default settings in log4j.properties cause sync failure
Resolution: Certain synchronization operations require a larger log file to complete successfully. GitCentric increased the max log size to 100 MB in the log4j file. This issues has been resolved in the current release.
1101108 -- Commits page returns 500 Internal Server Errors when multi-byte characters in messages.
Resolution: When displaying the repository history with commit messages containing multi-byte characters, GitCentric would display a "500 Internal Server Error". This issue has been resolved in this release.
1104114,40990 -- Cloning of a repository via GitCentric is timing out
Resolution: The gerrit.config sshd.idleTimeout configuration has been restored in this release. It can be used to configure timeout on clone/pull/push operations. See the Gerrit Documentation for more information.
1104728, 41934 -- Problem pushing changes via GitCentric to AccuRev
Resolution: Customer reported that a push to AccuRev was failing.This issues has been resolved in the current release.
624310 -- Missing xercesImpl.jar causing product failure with error 'SAXParser not found'
Resolution: This issue has been resolved in this release.
624311 -- This issue has been described in several ways :
Unable to negotiate ... no matching key exchange method found "
ssh gets an error saying unable to agree on KeyAlgorithms" that's just a restatement of the error message. The KeyAlgorithms he refers to are the key exchange method or algorithm.
"sshd needs to support NOT just diffie-hellman-group1-sha1 [for the ssh key exchange]”that is what we do in the workaround to solve the problem on the GC server side
Resolution: Install GitCentric on any Linux server. Have a modern Linux (e.g. Ubuntu 16.04 or later) client communicate with that server via git clone/push/pull or via ssh commands. He will see the above errors. This issue has been resolved in this issue. (The workaround has been documented in Known Issues and Workarounds on page 31.)
624309 -- Simplify Code - Review
Resolution: Create a repository. Turn code review on (using the Administration > Repo > Basic tab). Then edit some ACLs for that repository. It is now not possible to turn code review off. Solution is to replace graphic user interface (GUI) check box for code review on/off with two ACL-only repositories: Code- Review, and Direct-Push. By re-parenting the user repository to one of these two, he can turn code review on or off. This issues has been resolved in the current release.
1102562, 2844963 -- Delete file and replace with a directory causes push error
Resolution: A certain sequence of git changes was causing a push error. This issues has been resolved in the current release.
1106810, 2873527, 43464 -- catalina.out growing without limit and fills the disk.
Resolution: The information that is written to the KandoBridge and KandoGerrit logs was duplicated in the tomcat, catalina.out file. Since catalina.out doesn't get rotated or limited, the disk would fill up. Changes in this release mean that catalina.out only gets output that isn't available in kandoBridge or kandoGerrit logs."