This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
We've run collab for a week now, and we're getting into the habit of unshare / reshare, rejoin channel or even restart NB on a round the clock basis. Worse yet, for most of the time when out-of-sync happens the file is only edited by a single remote user! Ctrl+Z sometimes helps as a workaround. Tested on NB5 QBuild 200512011057 and Collab as of 01/12
Did you take into account the delay before unlocking the region? It takes several seconds (configurable) and there was at least one version with 20s region unlock time, IIRC.
Not particularly sure about what do you mean by that; we have been giving a few minutes every time in hope of a "self-repair" (see below). When files are out-of-sync we mean that extra characters / lines (even up to a whole repetition section of javadocs + method signature) creeps into the code and destroy the integrity of the whole source file, definitely not the restuls of any intermediate state of normal (intended) editting.
Simple scenario for reproducing this problem is: 1. Share (well known) SwingWorker class 2. Open the file (not necessary to be opened on both sides at once) 3. Quickly delete all javadocs from top to bottom (select block, delete, select..) The file on other size will have wrong lines missing, so it seems like wrong offsets are computed in case more than one block is locked at once. This "wrong offset" problem seems to cause other issues, I'll dup them to this one.
*** Issue 69392 has been marked as a duplicate of this issue. ***
The problem occurs in case you create two overlapping regions. Example: 1. you delete line 3, lines 1-5 get locked 2. you delete line 7, lines 5-9 get locked the line 5 is part of two regions, which confuses the system.
It is slightly better in trunk now (#69392 part fixed at least), but it is still possible to break the document coherrency.
reproducible on Lin
Fixed collab/filesharing/src/org/netbeans/modules/collab/channel/filesharing/eventhandler/DocumentChangeHandler.java,v1.3 collab/filesharing/src/org/netbeans/modules/collab/channel/filesharing/filehandler/CollabFileHandlerSupport.java,v1.7 collab/filesharing/src/org/netbeans/modules/collab/channel/filesharing/filehandler/CollabRegionSupport.java,v1.5 and few other files already commited before.
Fix backported to release50 with the other modified files: collab/filesharing/src/org/netbeans/modules/collab/channel/filesharing/eventhandler/DocumentChangeHandler.java,v1.2.4.1 collab/filesharing/src/org/netbeans/modules/collab/channel/filesharing/filehandler/CollabFileHandlerSupport.java,v1.4.2.1 collab/filesharing/src/org/netbeans/modules/collab/channel/filesharing/filehandler/CollabJavaFileHandler.java,v1.2.4.1 collab/filesharing/src/org/netbeans/modules/collab/channel/filesharing/filehandler/CollabRegionSupport.java,v1.2.4.1 collab/filesharing/src/org/netbeans/modules/collab/channel/filesharing/filehandler/CollabTextFileHandler.java,v1.1.20.1 collab/filesharing/src/org/netbeans/modules/collab/channel/filesharing/filehandler/CollabXMLFileHandler.java,v1.1.20.1
The fix should be available on Dev AU as Collab/filesharing v1.5 and 5.0 beta AU as Collab/filesharing v1.1.3
will perform testings once these files are published on AUC ;)
One additional fix was added, Dev AU: Collab/filesharing v1.6 5.0beta AU: Collab/filesharing v1.1.4
Ok - but until I can successfully download the Collab module from the dev AUC (which is currently not possible with NB5.1 200601231900) I couldn't quite go round and test it ^^"
I know. I've been told by release engineering the modules will be built/pushed today (this night prague time), so stay tuned.
OK, the 5.0 modules are now available at 5.0beta AU. The trunk (5.5dev) modules are still not available :-( Please try to verify with 5.0
erm.... does it mean the 5.0 RC2 build? coz my friend claims to be unable to find the collab on the AUC there...
Yes, 5.0RC2, but _beta_ AU, that is, you have to invoke the update center and check the (by default unchecked) beta AU (the last entry). Once we verify the modules, they'll move to official stable AU...
Tried hard to break it, but failed ;) Thanks very much for the hard work~