errael
errael
> null is actually a valid return value: ... so the JDK should probably check Maybe it was fixed. I happened all the time with JDK-11, and never with JDK-17....
@mbien, you might be familiar with this area. :-)
Wow, that's curious. That 2nd change by emi is particularly interesting. Is the code above used only for hints put into the 'rules/' directory by a user? Maybe the problem...
Here's something which is probably the same issue. ``` public void foo(List list) { final Object[] listeners = list.toArray(); //
Are you able to get a log of when it goes south. There discussion of this in https://lists.apache.org/thread/nsg2pdzrs3go9f4zlhy0gjs2hfxmbdbn But basically ``` Edit the netbeans.conf file in netbeans/etc/ to add: -J-Dorg.netbeans.NbClipboard.level=FINEST...
Fix for the NPE in #4703 . @lkishalmi , @sdedic Since I'm not sure what is proper behavior... Even the NPE fix could be handled differently by coming up with...
@mbien , can this be reopened? The "NPE" is fixed but the "visually inaccurate state" is pending; need some feedback on what is proper behavior. The opening comment outlines some...
> @sdedic agreed! I was just looking at this. I assume that VSCode failure on Travis isn't an issue? Retriggered it once - not looked in depth at why it...
I was going to close this since #4603 is merged. But until it's released... What's best practice for closing an issue?