Greptile Summary

This PR addresses a specific edge case in streaming aggregations where empty or null hits arrays could cause issues in the dashboard panel data loader. The change adds defensive null/empty checks in three critical locations within usePanelDataLoader.ts before copying search result hits when streaming aggregations are enabled.

The modifications target three different response handling scenarios:

1. Partition-based streaming aggregations (lines 594-598) - Checks if searchRes?.data?.hits?.length > 0 before updating state.data
2. Histogram response handling (lines 704-710) - Validates searchRes?.content?.results?.hits?.length > 0 before state updates
3. Streaming histogram hits (lines 760-766) - Similar validation for streaming histogram data

Each check follows the same pattern: only update state.data[currentQueryIndex] when there are actual hits with content, preventing the assignment of empty arrays that could confuse the UI about loading states versus truly empty result sets. This is particularly important for real-time streaming scenarios where partial results arrive in chunks and preserving existing data until meaningful results arrive is crucial.

The change integrates well with the existing codebase's error handling patterns and maintains the streaming aggregation functionality while making it more robust against edge cases where the backend might return valid metadata but no actual data points.

Confidence score: 4/5

• This PR is safe to merge with minimal risk as it only adds defensive checks without changing core logic
• Score reflects simple defensive programming changes that reduce potential runtime issues without introducing complexity
• No files require special attention as the changes are straightforward null checks with consistent patterns

_{1 file reviewed, 2 comments}

_{Edit Code Review Bot Settings | Greptile}