Reference the Line of Another File in the Same Review
In the chat box of file foo.cc I would like to reference a specific line in file bar.cc.For example, I have bar.cc:line 12 written in my code collab chat box. In this case, code-collab only recognizes and allows the jump to bar.cc, but not to the line. I would like a featurewhere a designer canwrite a reference to line 12 in bar.cc and Collaborator automatically auto-links the to the correct line.
Client Maintenance - upgrade to latest version compatible with the server
The Code Collaborator client is compatible with a fairly wide range of server versions. The client is aware of the associated server. Ideally, the client tool could auto update when enabled to the current version that is compatible with the associated server version.java.net.SocketException: Connection reset by peer: socket write error
Hello, - Collaborator Enterprise v13.2.13200 Server - Collaborator client v12.4.12400 - SCM system is configured to PTC Integrity The PTC Integrity change package has 96 new files and 48 updated files The total size of the files is rather small ~ 4.2 MB When creating a review from ccollabgui.exe, when executing command ccollab addchangelist, the following java exception is raised. Please see the two attached files for more error details. ERROR: Executing command `ccollab addchangelist`: Error occurred: ERROR: Executing command `ccollab addchangelist`: java.io.IOException: java.net.SocketException: Connection reset Error occurred: java.io.IOException: java.net.SocketException: Connection reset com.smartbear.collaborator.client.exceptions.CollabClientException: java.io.IOException: java.net.SocketException: Connection reset Error occurred: com.smartbear.collaborator.client.exceptions.CollabClientException: java.io.IOException: java.net.SocketException: Connection reset at com.smartbear.collaborator.json.api.AbstractApi.sendBatch(AbstractApi.java:95) .... .... javax.net.ssl.SSLException: java.net.SocketException: Connection reset Error occurred: javax.net.ssl.SSLException: java.net.SocketException: Connection reset at sun.security.ssl.Alert.createSSLException(Unknown Source) Error occurred: at sun.security.ssl.Alert.createSSLException(Unknown Source) at sun.security.ssl.TransportContext.fatal(Unknown Source) Error occurred: at sun.security.ssl.TransportContext.fatal(Unknown Source) at sun.security.ssl.TransportContext.fatal(Unknown Source) Error occurred: at sun.security.ssl.TransportContext.fatal(Unknown Source) at sun.security.ssl.TransportContext.fatal(Unknown Source) Error occurred: at sun.security.ssl.TransportContext.fatal(Unknown Source) at sun.security.ssl.SSLSocketImpl.handleException(Unknown Source) Error occurred: at sun.security.ssl.SSLSocketImpl.handleException(Unknown Source) at sun.security.ssl.SSLSocketImpl.access$400(Unknown Source) Error occurred: at sun.security.ssl.SSLSocketImpl.access$400(Unknown Source) at sun.security.ssl.SSLSocketImpl$AppInputStream.read(Unknown Source) Processing change 12345678:1. Suppressed: java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(Unknown Source) at java.net.SocketOutputStream.write(Unknown Source) at sun.security.ssl.SSLSocketOutputRecord.encodeAlert(Unknown Source) ... 36 more
Hidden or read-only Review Custom Fields
We have developed an integration from a document-management system that uses one review custom field to store foreign document id and version information. When the review is created this information is provided from the other system through the JSON API. Obviously we do not want the GUI Client users to change this field, but currently Collaborator does not allow this. To make life easier in this kind of use cases, I propose Collaborator admin section to have following extra (boolean) settings for review custom fields: hidden, only to be modified/read through the API read-only, visible in GUI, butmodifiable only through the API
Manually specified file version selector names when uploaded from client via Git
Problem: I upload changes as a commit range in git between a reference branch (master) and my current HEAD. I then later need to rebase my current HEAD against an updated reference branch (master) and re-upload the changes. It cannot be differentiated in the file version selector during a review which versions of the file are reference branch (master) and which are HEAD versions. Generically, client tool uploaded differences from git commit ranges automatically label all versions of files as seen in file version selector drop down, with check-in time and non-human readable git object hash (not commit hash) only. Rebasing changes against the latest version of the reference branch, or merging the latest version of the reference branch into the changes, between a first and second upload to a review causes the "before" version from the reference branch to be different during the second uploaded of files and have a newer timestamp than the "after" version of the file from the first upload. The "before" versions therefore can't be differentiated from the "after" versions in the drop down. Solution: Add optional command line argument for "addgitdiffs" that will allow user specified names to be added to the before and after versions of all files included in the commit range. Conflicting names are automatically appended with standard "(1)", "(2)", etc for a given file based on upload order. For example, if I have changes on a "work" branch that originally forked from "master" branch and changed fileA and fileB, my upload command would be ccollab addgitdiffs --before-name="master" --after-name="work" ask master...work which would upload all changes made on the work branch since it split from master by uploading fileA and fileB from the commit on the master branch right before the work branch split, and fileA and fileB from the head of the work branch (currently). The extra arguments would add labeling for all the files from master as "master" and those coming from the work branch as "work" (new). When my review continues for a while and I need to rebase my work branch against the since-updated master branch I'll need to re-upload my changes relative to the new reference point on the master branch. Running the same command as before accomplishes that but causes a problem. When the differences in fileA are viewed without this feature, what's seen in the file version selector drop down is (larger numbers with the timestamps indicate newer timestamps): "<git object hash> <commit timestamp 1>" <---- from master branch in first upload "<git object hash> <commit timestamp 2>" <---- from work branch in first upload "<git object hash> <commit timestamp 3>" <---- from master branch in second upload "<git object hash> <commit timestamp 4>" <---- from work branch in second upload With the recommended feature this list becomes much more clear: "master <git object hash> <commit timestamp 1>" <---- from master branch in first upload "work <git object hash> <commit timestamp 2>" <---- from work branch in first upload "master(1) <git object hash> <commit timestamp 3>" <---- from master branch in second upload "work(1) <git object hash> <commit timestamp 4>" <---- from work branch in second upload
Allow Admins to close reviews
Bringing back an old thread - I'd like anyone with Admin privileges to be able to move a review to Completed. We've had several instances where someone has left the company, or is on extended leave, and their roles is required to move a review to completed. On solution is to shuffle roles - while that will allow a review to close, it's "not right". If the author of a document is out sick - yes I can assign the author role to someone else - but now you are fudging the review records in order to get the closure. Later when an auditor comes in we have to give a song and dance as to why the roles in the review don't represent the actual roles the staff members have. We shouldn't need to alter the records to move things forward. The review is more than a record of defects - it's a record of who did what, and we shouldn't need to compromise that to get around a technical glitch.
Collaborator client/Visual Studio addin and admin rights
Hi, We are using Collaborator 10.0 and Visual Studio addin with VS 2015. For some reason we are experiencing problems using the client GUI and VS addin if we don't run them with administrator rights. Without admin rights, the client GUI starts but the Add Changes/Shelvesets/Changesets buttons don't do anything. In Visual Studio, the Collaborator pane shows up but doesn't show any reviews and the Add files to review and New review from changes buttons are dead. When we start the client or Visual Studio as administrator, we have no problems. Is it a feature that admin rights are required or should they work also without them? Any advice to fix this would be nice. Thanks a lot, - Dukeman
Unable to install Code collaborator client
I was using code collaborator for a while and it suddenly stopped working and the application was not opening up. I uninstalled and while trying to reinstall getting the error as below. "java.lang.RuntimeException: java.lang.reflect.InvocationTargetException" Also tried to reinstall Java but didn't work. Using Java 1.8 Error Log Exception: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at com.install4j.runtime.installer.frontend.GUIHelper.invokeOnEDT(GUIHelper.java:704) at com.install4j.runtime.installer.frontend.WizardScreenExecutor.register(WizardScreenExecutor.java:265) at com.install4j.runtime.installer.ContextImpl.registerScreenConfigs(ContextImpl.java:744) at com.install4j.runtime.installer.ContextImpl.registerScreens(ContextImpl.java:732) at com.install4j.runtime.installer.controller.Controller.start(Controller.java:83) at com.install4j.runtime.installer.Installer.runInProcess(Installer.java:57) at com.install4j.runtime.installer.Installer.main(Installer.java:45) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:85) at com.exe4j.runtime.WinLauncher.main(WinLauncher.java:94) at com.install4j.runtime.launcher.WinLauncher.main(WinLauncher.java:25) Caused by: java.lang.reflect.InvocationTargetException at java.desktop/java.awt.EventQueue.invokeAndWait(EventQueue.java:1367) at java.desktop/java.awt.EventQueue.invokeAndWait(EventQueue.java:1342) at com.install4j.runtime.installer.frontend.GUIHelper.invokeOnEDT(GUIHelper.java:700) ... 13 more Caused by: java.lang.IllegalArgumentException: Malformed \uxxxx encoding. at java.base/java.util.Properties.loadConvert(Properties.java:654) at java.base/java.util.Properties.load0(Properties.java:454) at java.base/java.util.Properties.load(Properties.java:404) at com.smartbear.beans.ConfigUtils$1.run(ConfigUtils.java:371) at com.smartbear.beans.ConfigUtils.withLockFile(ConfigUtils.java:310) at com.smartbear.beans.ConfigUtils.loadProfileConfigProps(ConfigUtils.java:364) at com.smartbear.beans.ConfigUtils.loadConfigFiles(ConfigUtils.java:546) at com.smartbear.ccollab.installer.CollaboratorSetupScreen.createComponent(CollaboratorSetupScreen.java:215) at com.install4j.runtime.installer.frontend.ScreenEnvelope.initContentComponent(ScreenEnvelope.java:338) at com.install4j.runtime.installer.frontend.ScreenEnvelope.init(ScreenEnvelope.java:68) at com.install4j.runtime.installer.frontend.ScreenEnvelope.<init>(ScreenEnvelope.java:46) at com.install4j.runtime.installer.frontend.WizardScreenExecutor$3.run(WizardScreenExecutor.java:268) at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:303) at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740) at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
Git Repository Name on review with multiple git repository.
When you add several changes from git via GUI client to one review there is no way to understand which repository the file belongs to. For example(screen in attache), if several commits contain files with the same name, you can only understand which repository they refer to using a hash. The screenshot shows an example when all 3 files with the same name refer to different repositories. Adding the name of the repository, and not just the file with changes, would help us a lot. Thanks for attention!