This repository was archived by the owner on Sep 3, 2025. It is now read-only.
If an error is already handled and logged, do not re-log that same error. #5286
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
metroid-samus
deleted the
bugfix/do-not-double-log-genai-signal-analysis-errors
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
create_genai_signal_analysis_message()function manages and logs edge cases where a signal summary isn't generated. When no summary is produced, the function returns an empty list. The result fromcreate_genai_signal_analysis_message()is posted to a Slack channel. If the result is empty, Slack will generate an error. However, since this error has already been handled and logged, there is no need to log it again.