refactor: replace lazy query with polling query and fix overflow in log details sheet

[impoiler]

Summary

Improves log detail sheet reliability by switching from lazy loading to automatic polling for failed log fetches and fixes UI overflow issues in the sheet header.

Changes

• Replaced useLazyGetLogByIdQuery with useGetLogByIdQuery for automatic data fetching when the sheet opens
• Added polling mechanism that retries every 2 seconds when log fetch fails, stopping when successful
• Fixed horizontal overflow issues in the sheet header by adding overflow-x-hidden classes
• Exported useGetLogByIdQuery hook from the logs API

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (Next.js)
• Docs

How to test

1. Open the logs page and click on a log entry to view details
2. Verify the log details load automatically without manual triggering
3. Test with network issues or slow responses to confirm polling retry behavior
4. Check that long request IDs don't cause horizontal overflow in the sheet header

# UI
cd ui
pnpm i || npm i
pnpm test || npm test
pnpm build || npm run build

Screenshots/Recordings

N/A

Breaking changes

• Yes
• No

Related issues

N/A

Security considerations

None - this change only affects UI data fetching patterns and styling.

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]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8df7993a-5939-405e-b93c-12ec484412d1

📥 Commits

Reviewing files that changed from the base of the PR and between 0f7d254 and 28371c8.

📒 Files selected for processing (2)

• ui/app/workspace/logs/sheets/logDetailsSheet.tsx
• ui/lib/store/apis/logsApi.ts

---

📝 Walkthrough

Summary by CodeRabbit

• New Features

  • Log details now load automatically when opened, with automatic refreshing as needed.
  • Real-time polling (2s) runs automatically for logs that are processing or when errors occur; polling stops when no longer needed.

• Bug Fixes

  • Fixed horizontal overflow in the log details header and improved loader logic so content appears reliably when the correct log is loaded.

Walkthrough

Replaced an imperative lazy fetch with a declarative RTK Query (useGetLogByIdQuery) that runs only when the sheet is open and log.id exists; added polling control (0ms or 2000ms based on error/processing), adjusted loader gating, and suppressed header horizontal overflow.

Changes

Cohort / File(s)	Summary
Log Details Sheet ui/app/workspace/logs/sheets/logDetailsSheet.tsx	Swapped useLazyGetLogByIdQuery + manual fetchLog for `useGetLogByIdQuery(log?.id ?? "", { skip: !open
Logs API hooks ui/lib/store/apis/logsApi.ts	Exported the standard non-lazy hook useGetLogByIdQuery alongside the existing useLazyGetLogByIdQuery. No endpoint shape or tag changes.

Sequence Diagram(s)

sequenceDiagram
  participant Sheet as LogDetailsSheet
  participant Hook as useGetLogByIdQuery
  participant API as ServerAPI

  Sheet->>Hook: mount/open with skip: !open || !log?.id and pollingInterval
  Hook->>API: GET /logs/:id (polled per pollingInterval)
  API-->>Hook: 200 / log data (status: processing|complete) or error
  Hook-->>Sheet: isLoading / isError / data updates
  alt isError or data.status == "processing"
    Sheet->>Hook: set pollingInterval = 2000
  else
    Sheet->>Hook: set pollingInterval = 0
  end

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐇
I hopped from lazy calls to steady cheer,
Polling two seconds when the logs are near.
When errors grumble or processing stays,
I wait, I watch, in gentle ways—
A rabbit keeps the logs in gear.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main changes: replacing lazy query with polling and fixing overflow issues in the log details sheet.
Description check	✅ Passed	The description follows the template with all major sections completed: summary, changes, type of change, affected areas, testing instructions, and checklist items marked.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ 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 03-30-fix_added_poll_to_the_log_details_sheet_for_ongoing_request_logs

---

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

[impoiler]

• refactor: replace lazy query with polling query and fix overflow in log details sheet #2381 👈 (View in Graphite)
• refactor: extract copy-to-clipboard logic into reusable hook #2379
• fix: prevent edit mode activation when clicking interactive elements in message views #2377
• fix: add explicit type="button" to navigation and action buttons #2353
• main

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

[greptile-apps]

Confidence Score: 4/5

Safe to merge for typical usage, but two reliability issues from prior review threads remain unaddressed and could cause unnecessary server load in edge cases.

The two issues highlighted in previous review threads — infinite polling on persistent errors and stale pollingInterval on log navigation — are still present in the code. Both are P1-level reliability concerns: a 404 or server error will cause indefinite 2-second polling for the lifetime of the open sheet, and navigating from an errored log to a new one triggers immediate polling before the new log has a chance to fail. These don't affect the happy path but are real defects on the changed code paths.

ui/app/workspace/logs/sheets/logDetailsSheet.tsx — polling lifecycle management (lines 88–96)

Important Files Changed

Filename	Overview
ui/app/workspace/logs/sheets/logDetailsSheet.tsx	Replaces lazy query with polling-capable query; two unresolved reliability issues remain from prior review (no retry cap on persistent errors, pollingInterval not reset on log ID change). Overflow fix via overflow-x-hidden is straightforward and correct.
ui/lib/store/apis/logsApi.ts	Exports the new useGetLogByIdQuery hook alongside the existing lazy variant — minimal, correct change.

_{Reviews (4): Last reviewed commit: "Fix: Added poll to the log details sheet..." | Re-trigger Greptile}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@ui/app/workspace/logs/sheets/logDetailsSheet.tsx`:
- Around line 88-95: Polling is currently only enabled on errors; change the
logic so pollingInterval is set when the log is in a "processing" state or when
isError is true. Update the effect that calls setPollingInterval to check
log?.status === PROCESSING (import the PROCESSING constant from
ui/lib/constants/logs.ts) || isError and set pollingInterval (e.g. 2000)
accordingly. Also stop using !isFetching as the readiness gate during refetches
— rely on the presence of fullLog or the query's isLoading flag for initial load
and avoid gating rendering on isFetching to prevent UI flicker during background
polling.

🪄 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3b6346a3-61bd-45ce-b045-280b879a41b0

📥 Commits

Reviewing files that changed from the base of the PR and between ff789b8 and 101b7c9.

📒 Files selected for processing (2)

• ui/app/workspace/logs/sheets/logDetailsSheet.tsx
• ui/lib/store/apis/logsApi.ts

[akshaydeo]

Merge activity

• Mar 30, 9:25 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Mar 30, 9:29 AM UTC: Graphite rebased this pull request as part of a merge.
• Mar 30, 9:30 AM UTC: @akshaydeo merged this pull request with Graphite.

The base branch was changed.