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.
I filed 59807, but I guess the evaluator thinks it is your fault. You may want to read through the description, in that issue for more descriptive info....
Created attachment 22599 [details] the stack trace
One thing to note here: The stack is CONTINOUSLY generated. So the IDE is UNUSABLE affter the versioning window opens.
I'm afraid that I can not do anything with that in VCS. I just use SharabilityQuery, which is a public API with no restriction on what can it be called on and how many times. I can not prevent from conflict marks, you will get them as well when updating outside of the IDE. IMO it would be best if the project system caches some results (at least the broken state so that the exceptions are not thrown over and over again). It looks like a dupl. of issue #47288 to me. *** This issue has been marked as a duplicate of 47288 ***
x
Contains no new info relative to issue #59807. (I suggested reporting a bug in vcscore if there were exceptions in VcsFileSystem, but I guess Vince misread the stack traces - the exceptions are not in VcsFileSystem as such.) *** This issue has been marked as a duplicate of 59807 ***
No, I misread your comment. I looked at the stack trace and saw that apisupport has a bug. That bug is pretty minor in isolation. The VcsFileSystem code triggers that bug with much more serious repercussions for the user. When issue 59807 [the root cause] got closed as a dup of an enhancement request, I figured I had better send this to the folks that were being the middleman between the root cause and the user action. Maybe they could fix their code in a way that would prevent the "hang". Based on the comments here, I guess we just have to hope that folks never have merge conflicts in their project.xml files that happen to "live" in a versioned file system.