Skip to content
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

lib: return informative error for invalid extremum input #65

Merged
merged 1 commit into from
May 30, 2024
Merged

Conversation

efd6
Copy link
Collaborator

@efd6 efd6 commented May 30, 2024

Please take a look.

@efd6 efd6 added the enhancement New feature or request label May 30, 2024
@efd6 efd6 requested a review from andrewkroh May 30, 2024 01:18
@efd6 efd6 self-assigned this May 30, 2024
@efd6 efd6 added the Team:Security-External Integrations Label for the Security External Integrations team label May 30, 2024
Copy link
Member

@andrewkroh andrewkroh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@efd6 efd6 marked this pull request as ready for review May 30, 2024 01:22
@efd6 efd6 merged commit 0148715 into dev May 30, 2024
6 checks passed
kcreddy added a commit to elastic/integrations that referenced this pull request Aug 23, 2024
…rror (#10861)

Fix `max()` calculation on empty resources leading to error.

Due to change made in [`mito`](elastic/mito#65), the 
`max()`function now returns an error message `no extremum of empty list` 
when it is applied on empty `[]` list. This `mito` change is applied to `8.15.0` 
Stack. While this error message is extremely useful, the current CEL program in 
`ti_crowdstrike` doesn't check for empty list. This leads to an error while otherwise 
could have been a `null` value in Stack version `< 8.15.0`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Team:Security-External Integrations Label for the Security External Integrations team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants