lkishalmi commented on issue #1061: [NETBEANS-168] Simple least intrustive 
patch prevent IDE to burn CPU on broken symlinks.
URL: 
https://github.com/apache/incubator-netbeans/pull/1061#issuecomment-462105285
 
 
   Well, I've seen this one happening while accidentally caught it on the 
debugger.
   As File.exists() returns false on a broken symlink, any change triggers a 
refresh in a watched folder that has a broken symlink triggers this code 
resulting a folder children refresh which again triggers this code over and 
over.
   
   Can I merge this PR with the failing tests I've created? I'm sorry but I was 
not able to make the required test. Also we need to think about how we are 
eventually handle broken symlinks, as my tests at least could point out there 
is an inconsistency.
   Also this really be part of 11.0 as Gradle Projects are definitely triggers 
this issue. 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Reply via email to