feat: persist logs page-size preference in localStorage and exclude error_details from list query

[impoiler]

Summary

This PR fixes a Cloud Run 500 error caused by the /api/logs response exceeding the 32MB body limit when many error-status log rows are returned, and replaces the auto-calculated table page size with a user-controlled, localStorage-persisted page size preference.

Changes

• Exclude error_details from the logs list query: The error_details column is dropped from listSelectColumns in rdb.go because it can carry unbounded provider error payloads. With 25+ such rows, the combined response body can exceed Cloud Run's 32MB limit and return a 500. The full error detail remains available via the individual log detail endpoint (GET /api/logs/{id}).
• Replace auto-sized page size with a user preference: The useTablePageSize hook (which inferred page size from container height) is replaced by useTablePageSizePreference, which stores the user's chosen page size in localStorage under a per-table key (e.g. bifrost.logs.pageSize). The preference is hydrated lazily after mount to avoid SSR/hydration mismatches and defaults to 25.
• Add a "Rows per page" dropdown to the logs table footer: A ComboboxSelect with options [10, 25, 50, 100, 200] is added to the pagination controls, allowing users to explicitly choose how many rows to load per page. The selection is persisted across sessions.

Type of change

• Bug fix
• Feature

Affected areas

• Core (Go)
• UI (React)

How to test

1. Navigate to the logs table in the UI.
2. Confirm a "Rows per page" dropdown appears in the pagination footer with options 10, 25, 50, 100, and 200.
3. Select a page size, reload the page, and verify the selection is restored from localStorage.
4. Confirm that log list responses no longer include error_details in the payload, and that the full error is still visible when opening an individual log entry.
5. Verify that workspaces with many error-status logs no longer trigger 500 responses from /api/logs.

# Core
go test ./framework/logstore/...

# UI
cd ui
pnpm i
pnpm test
pnpm build

Screenshots/Recordings

Before: Page size was inferred from container height with no user control.
After: A "Rows per page" dropdown is shown in the pagination bar, and the selection persists across page reloads.

Breaking changes

• No

The error_details field is removed from list responses but remains available on the detail endpoint. Clients relying on error_details in the list response will need to fetch individual log entries to retrieve it.

Related issues

Closes the Cloud Run 32MB body limit 500 error on /api/logs.

Security considerations

No new auth, secrets, or PII exposure. Removing error_details from the list response reduces the amount of potentially sensitive provider error data sent in bulk responses.

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

[coderabbitai]

📝 Walkthrough

Walkthrough

The log list query no longer returns error_details. The logs table now persists a user-selected page size in localStorage, applies it to pagination, resets pagination when changed, and displays a rows-per-page selector.

Changes

Log list projection

Layer / File(s)	Summary
Exclude error details from list queries framework/logstore/rdb.go	listSelectColumns() removes error_details from list responses and documents the intentional exclusion.

Logs pagination preference

Layer / File(s)	Summary
Define persisted page-size preference ui/lib/hooks/useTablePageSizePreference.ts	Adds default page-size options and a hook that reads validated values from and writes selections to localStorage.
Wire page-size selection into logs pagination ui/app/workspace/logs/views/logsTable.tsx	Replaces measured page sizing with the persisted preference, resets the offset when the size changes, removes container measurement, and adds the rows-per-page selector.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Suggested reviewers: akshaydeo

Sequence Diagram(s)

sequenceDiagram
  participant User
  participant LogsTable
  participant PageSizePreference
  participant localStorage
  participant Pagination
  User->>LogsTable: select rows-per-page value
  LogsTable->>PageSizePreference: update selected page size
  PageSizePreference->>localStorage: persist selected page size
  LogsTable->>Pagination: update limit and reset offset
  Pagination->>LogsTable: render updated page controls

Loading

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly covers the two main changes: persisting logs page size and excluding error_details from the list query.
Description check	✅ Passed	The description matches the template well, covering summary, changes, type, affected areas, testing, screenshots, breaking changes, issues, and security.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 07-17-feat_configurable_page_size_for_logs_table

---

_{Comment @coderabbitai help to get the list of available commands.}

[impoiler]

• feat: persist logs page-size preference in localStorage and exclude error_details from list query #5327 👈 (View in Graphite)
• fix: simplify ApiKeySelectorView visibility condition for enforceVirtualKeys #5313
• fix: extend chat↔responses pricing fallback to work bidirectionally #5276
• docs: update audit log archival to document windowed, manifest-based archival with tuning fields #5234
• feat: add archiveInterval, archiveGracePeriod, and archiveMaxObjectBytes audit log archival config options #5229
• fix: reject out-of-range tool_sync_interval minutes to prevent nanosecond unit confusion overflow #5255
• fix: send only disabled on toggle and convert tool_sync_interval units in cache #5254
• feat: add prompt_tokens and completion_tokens to search stats #5245
• feat: show prompt/completion token breakdown in logs stats card #5244
• feat: add throughput column and trend to model rankings tab and CSV export #5195
• feat: add throughput (tokens/sec) to model rankings and trend data #5194
• feat: add throughput (tokens/sec) histogram endpoints and dashboard metrics #5181
• feat: add throughput (tokens/sec) charts to overview and provider usage dashboard tabs #5180
• fix: replace fan-out attribution with single-owner additive rollup and "Unassigned" bucket for dimension rankings #5168
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Confidence Score: 5/5

This looks safe to merge.

• Stored page sizes are limited to the values offered by the dropdown.
• Invalid stored values fall back to the default size.
• No blocking issues remain in the updated code.

Important Files Changed

Filename	Overview
framework/logstore/rdb.go	Removes unbounded error details from log-list projections while preserving detail retrieval.
ui/app/workspace/logs/views/logsTable.tsx	Adds page-size controls and synchronizes the persisted preference with pagination.
ui/lib/hooks/useTablePageSizePreference.ts	Adds SSR-safe localStorage hydration and validates stored values against the allowed sizes.

_{Reviews (4): Last reviewed commit: "feat: Configurable page size for logs ta..." | Re-trigger Greptile}

[coderabbitai]

🧹 Nitpick comments (1)

ui/lib/hooks/useTablePageSizePreference.ts (1)

1-1: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Remove the "use client" directive — this project uses TanStack Router, not Next.js App Router.

The "use client" directive is a Next.js-specific construct that has no effect in the current Vite/TanStack Router toolchain. Introducing it can confuse contributors about the project's routing framework. Based on learnings, the UI code under ui/ should not include Next.js App Router conventions such as "use client" directives.

♻️ Proposed fix

-"use client";
-
 import { useCallback, useEffect, useState } from "react";

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@ui/lib/hooks/useTablePageSizePreference.ts` at line 1, Remove the top-level
"use client" directive from useTablePageSizePreference.ts, leaving the hook
implementation unchanged and preserving the existing TanStack Router/Vite
conventions.

Source: Learnings

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@ui/lib/hooks/useTablePageSizePreference.ts`:
- Line 1: Remove the top-level "use client" directive from
useTablePageSizePreference.ts, leaving the hook implementation unchanged and
preserving the existing TanStack Router/Vite conventions.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 3533eba4-125c-4b0d-bfca-5d1e8628c25c

📥 Commits

Reviewing files that changed from the base of the PR and between b30b2fb and 90632b8.

📒 Files selected for processing (3)

• framework/logstore/rdb.go
• ui/app/workspace/logs/views/logsTable.tsx
• ui/lib/hooks/useTablePageSizePreference.ts

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@ui/lib/hooks/useTablePageSizePreference.ts`:
- Around line 27-31: Update useTablePageSizePreference to restrict the
defaultPageSize, hydrated localStorage value, and setPageSize input to values
included in DEFAULT_PAGE_SIZE_OPTIONS. Fall back to the supported default when
validation fails, and ensure the returned pageSize never reaches LogsDataTable
as an unsupported value.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 29fb0cb0-ca8a-4dc8-b9f2-b1c982f014d1

📥 Commits

Reviewing files that changed from the base of the PR and between 90632b8 and 7df1167.

📒 Files selected for processing (3)

• framework/logstore/rdb.go
• ui/app/workspace/logs/views/logsTable.tsx
• ui/lib/hooks/useTablePageSizePreference.ts

🚧 Files skipped from review as they are similar to previous changes (2)

• ui/app/workspace/logs/views/logsTable.tsx
• framework/logstore/rdb.go

[Pratham-Mishra04]

Merge activity

• Jul 17, 11:05 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jul 17, 11:53 AM UTC: Graphite rebased this pull request as part of a merge.
• Jul 17, 11:54 AM UTC: @Pratham-Mishra04 merged this pull request with Graphite.

The base branch was changed.