Add java final variable to existing constructor feature is gone. #3873

Activity

1. TechScar commented on Feb 6, 2025

   

   TechScar

   on Feb 6, 2025

   More actions

   Can confirm I have the same problem. Definitely been facing this issue for at least a few months now, if not since mid-2024. Which is a shame, because it was such a helpful feature.

   The Language Support for Java output prints the following error for me:

   [Error - 8:37:17 AM] Request textDocument/codeAction failed.
     Message: Internal error.
     Code: -32603 
   java.util.concurrent.CompletionException: java.lang.ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0
   	at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(Unknown Source)
   	at java.base/java.util.concurrent.CompletableFuture.completeThrowable(Unknown Source)
   	at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(Unknown Source)
   	at java.base/java.util.concurrent.CompletableFuture$Completion.exec(Unknown Source)
   	at java.base/java.util.concurrent.ForkJoinTask.doExec(Unknown Source)
   	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source)
   	at java.base/java.util.concurrent.ForkJoinPool.scan(Unknown Source)
   	at java.base/java.util.concurrent.ForkJoinPool.runWorker(Unknown Source)
   	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source)
   Caused by: java.lang.ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0
   	at org.eclipse.jdt.internal.ui.text.correction.proposals.InitializeFinalFieldProposalCore.<init>(InitializeFinalFieldProposalCore.java:79)
   	at org.eclipse.jdt.ls.core.internal.corrections.UnInitializedFinalFieldSubProcessor.createInitializeFinalFieldProposal(UnInitializedFinalFieldSubProcessor.java:41)
   	at org.eclipse.jdt.ls.core.internal.corrections.UnInitializedFinalFieldSubProcessor.createInitializeFinalFieldProposal(UnInitializedFinalFieldSubProcessor.java:1)
   	at org.eclipse.jdt.internal.ui.text.correction.UnInitializedFinalFieldBaseSubProcessor.addProposals(UnInitializedFinalFieldBaseSubProcessor.java:72)
   	at org.eclipse.jdt.ls.core.internal.corrections.QuickFixProcessor.process(QuickFixProcessor.java:165)
   	at org.eclipse.jdt.ls.core.internal.corrections.QuickFixProcessor.getCorrections(QuickFixProcessor.java:91)
   	at org.eclipse.jdt.ls.core.internal.handlers.CodeActionHandler.getCodeActionCommands(CodeActionHandler.java:190)
   	at org.eclipse.jdt.ls.core.internal.handlers.JDTLanguageServer.lambda$14(JDTLanguageServer.java:759)
   	at org.eclipse.jdt.ls.core.internal.BaseJDTLanguageServer.lambda$0(BaseJDTLanguageServer.java:87)
   	... 7 more
   

   I am running extension version 1.39.0 in VSCode version 1.96.4
2. datho7561

   added

   need info

   on Jun 24, 2026
3. datho7561 commented on Jun 24, 2026

   

   datho7561

   on Jun 24, 2026

   Contributor

   More actions

   Seems to be working for me now. I'm guessing something in the past year fixed this. Let me know if you can still reproduce this.
4. datho7561

   closed this as completedon Jun 24, 2026
5. TechScar commented on Jun 25, 2026

   

   TechScar

   on Jun 25, 2026

   More actions

   Wow, I had completely forgotten about this issue - you are right, it's been working for a while now. Always nice when bugs fix themselves 😄