advances the log query end time to the current time when refreshing the default live range
preserves an explicit end time when the user has selected one in the URL
applies the behavior consistently across request, access, action, and connection log pages
Why
The log pages initialize their default end time to now, but the refresh action reused that stale timestamp. For a user watching logs with the default range, refresh could keep querying the old upper bound instead of including newly written rows.
Verification
git diff --check
attempted npm run dev:check, but this checkout has no node_modules installed and npx tried to install the unrelated tsc package instead of using a local TypeScript compiler
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/fosrl/pangolin/pull/3154
**Author:** [@RitwijParmar](https://github.com/RitwijParmar)
**Created:** 5/26/2026
**Status:** ✅ Merged
**Merged:** 5/26/2026
**Merged by:** [@oschwartz10612](https://github.com/oschwartz10612)
**Base:** `main` ← **Head:** `codex/pangolin-refresh-live-log-window`
---
### 📝 Commits (1)
- [`6aa1d3b`](https://github.com/fosrl/pangolin/commit/6aa1d3b094af86148eea4a30960b7930b2ae59a3) fix(logs): refresh default end time
### 📊 Changes
**4 files changed** (+20 additions, -4 deletions)
<details>
<summary>View changed files</summary>
📝 `src/app/[orgId]/settings/logs/access/page.tsx` (+5 -1)
📝 `src/app/[orgId]/settings/logs/action/page.tsx` (+5 -1)
📝 `src/app/[orgId]/settings/logs/connection/page.tsx` (+5 -1)
📝 `src/app/[orgId]/settings/logs/request/page.tsx` (+5 -1)
</details>
### 📄 Description
## Summary
- advances the log query end time to the current time when refreshing the default live range
- preserves an explicit end time when the user has selected one in the URL
- applies the behavior consistently across request, access, action, and connection log pages
## Why
The log pages initialize their default end time to now, but the refresh action reused that stale timestamp. For a user watching logs with the default range, refresh could keep querying the old upper bound instead of including newly written rows.
## Verification
- git diff --check
- attempted npm run dev:check, but this checkout has no node_modules installed and npx tried to install the unrelated tsc package instead of using a local TypeScript compiler
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/fosrl/pangolin/pull/3154
Author: @RitwijParmar
Created: 5/26/2026
Status: ✅ Merged
Merged: 5/26/2026
Merged by: @oschwartz10612
Base:
main← Head:codex/pangolin-refresh-live-log-window📝 Commits (1)
6aa1d3bfix(logs): refresh default end time📊 Changes
4 files changed (+20 additions, -4 deletions)
View changed files
📝
src/app/[orgId]/settings/logs/access/page.tsx(+5 -1)📝
src/app/[orgId]/settings/logs/action/page.tsx(+5 -1)📝
src/app/[orgId]/settings/logs/connection/page.tsx(+5 -1)📝
src/app/[orgId]/settings/logs/request/page.tsx(+5 -1)📄 Description
Summary
Why
The log pages initialize their default end time to now, but the refresh action reused that stale timestamp. For a user watching logs with the default range, refresh could keep querying the old upper bound instead of including newly written rows.
Verification
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.