fix(logs): Correct inverted maxPages condition for infinite query

The ternary condition in maxPagesForLogsInfiniteQuery was inverted. When there are fewer than 500 rows locally, we should use the higher limit (300 pages) to collect sufficient data from sparse logs. When there are more rows cached, use the lower limit (30 pages) to conserve memory.

Also fixed the JSDoc comment on LOCAL_LOG_ROWS_FOR_EXPANDED_INFINITE_PAGES to correctly reference MAX_LOGS_INFINITE_QUERY_PAGES_EXPANDED.

Co-authored-by: Armen Zambrano G. <armenzg@users.noreply.github.com>

Author: cursoragent

static/app/views/explore/logs/constants.tsx

@@ -22,7 +22,7 @@ export const DEFAULT_TRACE_ITEM_HOVER_TIMEOUT_WITH_AUTO_REFRESH = 400; // With a
 export const MAX_LOGS_INFINITE_QUERY_PAGES = 30; // This number * the refresh interval must be more seconds than 2 * the smallest time interval in the chart for streaming to work.
 /** Larger page cap once enough rows are cached (see useInfiniteLogsQuery). */
 export const MAX_LOGS_INFINITE_QUERY_PAGES_EXPANDED = 300;
-/** Below this many rows in the client cache, use {@link MAX_LOGS_INFINITE_QUERY_PAGES}. */
+/** Below this many rows in the client cache, use {@link MAX_LOGS_INFINITE_QUERY_PAGES_EXPANDED}. */
 export const LOCAL_LOG_ROWS_FOR_EXPANDED_INFINITE_PAGES = 500;
 
 /**

static/app/views/explore/logs/useLogsQuery.tsx

@@ -414,8 +414,8 @@ function maxPagesForLogsInfiniteQuery(client: QueryClient, queryKey: QueryKey):
   const rows =
     cached?.pages?.reduce((n, page) => n + (page[0]?.data?.length ?? 0), 0) ?? 0;
   return rows < LOCAL_LOG_ROWS_FOR_EXPANDED_INFINITE_PAGES
-    ? MAX_LOGS_INFINITE_QUERY_PAGES
-    : MAX_LOGS_INFINITE_QUERY_PAGES_EXPANDED;
+    ? MAX_LOGS_INFINITE_QUERY_PAGES_EXPANDED
+    : MAX_LOGS_INFINITE_QUERY_PAGES;
 }
 
 export function useInfiniteLogsQuery({