-
-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Null pointer Exception #447
Labels
Feature: Tags
Items related to Nebula Logger's tagging/labeling functionality
Layer: Logger Engine
Items related to the core logging engine
Type: Bug
Something isn't working
Milestone
Comments
@ramagrubhubGithub thanks for reporting this! I think this is a fairly small bug - I'll try to fix this in one of the upcoming releases. |
jongpie
added
Feature: Tags
Items related to Nebula Logger's tagging/labeling functionality
Layer: Logger Engine
Items related to the core logging engine
labels
Feb 2, 2023
jongpie
added a commit
that referenced
this issue
Mar 7, 2023
…ck when processing LogEntryTagRule__mdt rules
jongpie
added a commit
that referenced
this issue
Mar 15, 2023
… configurable fields in Slack plugin (#452) * Added overload method LogEntryEventBuilder.setRecord(Map<Id, SObject>) to support logging maps of SObjects. Other types of maps, as well as Set<SObject>, are currently considered out of scope * Updated System.debug() calls in Logger.cls to start with 'Nebula Logger' instead of just 'Logger' for clarity * Updated formula field LogEntry__c.LoggingLevelWithImage__c to use a different emoji for INFO vs lower levels (DEBUG, FINE, FINER, and FINEST) * Added inline help text about thresholds to all of the limits formula fields on LogEntry__c * Added new AnimationRule metadata to enable confetti on the Log__c path component * Fixed #447 by updating LogEntryEventHandler to have an extra null check when processing LogEntryTagRule__mdt rules * Fixed #453 by simplifying Logger.getUserSettings() to always use default field values, and making LoggerSettingsController responsible for handling prod-specific settings. Some default field values on LogEntry__c have also been updated to provide the most detailed settings OOTB. This also led to the creation of the new public method Logger.createSettings(). * Updated SlackLoggerPlugin.cls to leverage a new field set, Log__c.SlackNotificationFields, to support customization of the fields shown in Slack notifications. This field set can either be directly modified (although changes may be reverted during upgrades), or by creating & specifying another field set in the custom metadata record LoggerParameter.SlackLogNotificationFieldSet * Renamed the remote site setting Slack.remoteSite-meta.xml to LoggerSlack.remoteSite-meta.xml to consistently have some variation of the word "Log" in all metadata * Fixed some dependabot alerts in package-lock.json * Commented-out all asserts in the Experience Cloud site's test classes. These are copies of the classes that Salesforce typically auto-creates when Experience Cloud is first enabled in an org - they've started failing in the pipeline, and they have 0 relevance to Nebula Logger's functionality, so commenting-out the asserts is good enough for now * Switched to installing sfdx bummer plugin in the pipeline, instead of using linked version. There seems to be an ongoing issue with newer versions of sfdx that causes issues with linking plugins - @W-12652231 * Added new extra test class NebulaLogger_E2E_Tests to test full end-to-end (E2) tests to verify certain features & behaviors, as well as to provide examples to Apex developers of how to test their usage of Nebula Logger. This just has some basic tests for now - it'll evolve over the next few releases
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature: Tags
Items related to Nebula Logger's tagging/labeling functionality
Layer: Logger Engine
Items related to the core logging engine
Type: Bug
Something isn't working
Package Edition of Nebula Logger
Unlocked Package
Package Version of Nebula Logger
v4.7.8
New Bug Summary
Getting a Null pointer Exception inside ruleCriteriaMet(LogEntryEventHandler Class) when there is no value for the matching field(Log [Entry). We are using a Log Entry Tag rule based on the Origin__c field and when rule Criteria is excecuted it is having null value and comparison throwing a null pointer Exception.
The text was updated successfully, but these errors were encountered: