Skip to content

Conversation

gitdoluquita
Copy link
Contributor

Details can be nil if, for example, no logs are found. This PR prevents this tool from panicking.

@gitdoluquita gitdoluquita requested a review from a team as a code owner May 13, 2025 19:31
Copy link
Contributor

@csmarchbanks csmarchbanks left a comment

Choose a reason for hiding this comment

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

If this is an expected state when no logs are found should this just return nil instead of an error?

@sd2k
Copy link
Collaborator

sd2k commented May 15, 2025

Yeah I don't think this should be returning an error, it's a successful response just with no results.

@gitdoluquita gitdoluquita force-pushed the fix-epl-empty-details-panic branch from dd13c30 to 4c85dc1 Compare May 15, 2025 13:42
@gitdoluquita gitdoluquita requested review from csmarchbanks and sd2k May 15, 2025 13:43
@gitdoluquita
Copy link
Contributor Author

Good call! I'm still a bit unsure on what we should error and what we should raise as an error to the LLM to pickup, but I think in this case the message is clear enough.

@gitdoluquita gitdoluquita merged commit 2f163bc into main May 15, 2025
10 checks passed
@gitdoluquita gitdoluquita deleted the fix-epl-empty-details-panic branch May 15, 2025 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants