-
-
Notifications
You must be signed in to change notification settings - Fork 218
Closed
Labels
Layer: Logger EngineItems related to the core logging engineItems related to the core logging engineLogging Source: ApexItems related to using Logger within ApexItems related to using Logger within ApexLogging Source: FlowItems related to using Nebula Logger within FlowItems related to using Nebula Logger within FlowLogging Source: Lightning ComponentsItems related to using Nebula Logger using JavaScript within lightning components (lwc & aura)Items related to using Nebula Logger using JavaScript within lightning components (lwc & aura)Type: BugSomething isn't workingSomething isn't working
Milestone
Description
Package Edition of Nebula Logger
Unlocked Package
Package Version of Nebula Logger
v4.6.14
New Bug Summary
We were logging code that could occasionally result in the string being passed to the logger being null. When this occurs the Logger itself emits an exception:
System.NullPointerException: Attempt to de-reference a null object
The stack trace is:
Class.LogEntryEventBuilder.applyDataMaskRules: line 752, column 1
Class.LogEntryEventBuilder.setMessage: line 171, column 1
Class.Logger.debug: line 1570, column 1
The code that we had to produce this was of the form:
String results = someFunctionThatCanReturnNull();
Logger.debug(results); // Error thrown here
Metadata
Metadata
Assignees
Labels
Layer: Logger EngineItems related to the core logging engineItems related to the core logging engineLogging Source: ApexItems related to using Logger within ApexItems related to using Logger within ApexLogging Source: FlowItems related to using Nebula Logger within FlowItems related to using Nebula Logger within FlowLogging Source: Lightning ComponentsItems related to using Nebula Logger using JavaScript within lightning components (lwc & aura)Items related to using Nebula Logger using JavaScript within lightning components (lwc & aura)Type: BugSomething isn't workingSomething isn't working