Apex Class & Trigger Trace Flags Not Saving.
Issue #1672
resolved
Tried saving a Apex Class Trace Flag and got this in the log:
07-15 20:14:06,375 [130066230] ERROR - llij.ide.plugins.PluginManager - Argument for @NotNull parameter 'element' of com/illuminatedcloud/intellij/psi/util/ApexPsiUtil.getStartOffset must not be null
java.lang.IllegalArgumentException: Argument for @NotNull parameter 'element' of com/illuminatedcloud/intellij/psi/util/ApexPsiUtil.getStartOffset must not be null
at com.illuminatedcloud.intellij.psi.util.ApexPsiUtil.$$$reportNull$$$0(SourceFile)
at com.illuminatedcloud.intellij.psi.util.ApexPsiUtil.getStartOffset(SourceFile)
at com.illuminatedcloud.intellij.refactoring.implementOverride.AbstractApexImplementOverrideMethodHandler.invoke(SourceFile:136)
at com.intellij.codeInsight.generation.OverrideMethodsHandler.invoke(OverrideMethodsHandler.java:42)
at com.intellij.codeInsight.actions.CodeInsightAction.lambda$null$0(CodeInsightAction.java:54)
at com.intellij.codeInsight.actions.CodeInsightAction.lambda$actionPerformedImpl$1(CodeInsightAction.java:60)
at com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:220)
at com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:178)
at com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:159)
at com.intellij.codeInsight.actions.CodeInsightAction.actionPerformedImpl(CodeInsightAction.java:51)
at com.intellij.codeInsight.actions.CodeInsightAction.actionPerformed(CodeInsightAction.java:29)
at com.intellij.openapi.actionSystem.ex.ActionUtil.performActionDumbAware(ActionUtil.java:280)
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher$1.performAction(IdeKeyEventDispatcher.java:609)
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.lambda$processAction$3(IdeKeyEventDispatcher.java:670)
at com.intellij.openapi.application.TransactionGuardImpl.performUserActivity(TransactionGuardImpl.java:94)
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.processAction(IdeKeyEventDispatcher.java:669)
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.processAction(IdeKeyEventDispatcher.java:619)
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.processActionOrWaitSecondStroke(IdeKeyEventDispatcher.java:516)
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.inInitState(IdeKeyEventDispatcher.java:470)
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.dispatchKeyEvent(IdeKeyEventDispatcher.java:219)
at com.intellij.ide.IdeEventQueue.dispatchKeyEvent(IdeEventQueue.java:896)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:841)
at com.intellij.ide.IdeEventQueue.lambda$null$8(IdeEventQueue.java:449)
at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:741)
at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$9(IdeEventQueue.java:448)
at com.intellij.openapi.application.impl.ApplicationImpl.runIntendedWriteActionOnCurrentThread(ApplicationImpl.java:831)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:502)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
Tried adding in a Start value for the trace flag but that didn’t work either.
Comments (5)
-
reporter -
reporter - edited description
-
repo owner I've made both of these more defensive against null objects and will include that in the next build.
-
repo owner - changed status to resolved
Resolving given the changes that were delivered several builds back. If you're still seeing this, please reopen with new logs.
-
repo owner - changed component to Log Analyzer
- Log in to comment
Also found this in there as well: