Skip to content

fix: write an implied timestamp range into the query on a page request - #3981

Closed
chasers wants to merge 1 commit into
fix/search-server-scrollfrom
fix/load-more-implied-range
Closed

chasers wants to merge 1 commit into
fix/search-server-scrollfrom
fix/load-more-implied-range

Conversation

@chasers

@chasers chasers commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

Stack 6/7 — "Load more" pagination fixes.

  • Problem: a query with no t: filter pages with a fixed 60 second window.
  • Fix: use the range the chart draws. c:group_by(t::minute) means the last 120 minutes.
  • The first page request writes that range into the query. The URL then shows what is on screen.

🤖 Generated with Claude Code

https://claude.ai/code/session_01YBPF1knvgfghTSdxuYryGL

@chasers
chasers added this pull request to stack #3983 September 14, 2026 18:44
@chasers
chasers force-pushed the fix/load-more-implied-range branch from 7e676ac to ed75590 Compare September 14, 2026 19:20
@chasers
chasers force-pushed the fix/search-server-scroll branch from 80bcc16 to 40058df Compare September 14, 2026 19:20
A query with no `t:` filter now gets one on the first page request. The range
is the one the chart already draws. The aggregate query charts
`default_period_tick_count/1` periods back from now, so
`c:group_by(t::minute)` means the last 120 minutes.

The page window also uses that implied range, not a fixed 60 seconds.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YBPF1knvgfghTSdxuYryGL
@chasers
chasers force-pushed the fix/search-server-scroll branch from 40058df to e7a01b8 Compare September 17, 2026 19:30
@chasers
chasers force-pushed the fix/load-more-implied-range branch from ed75590 to 692e932 Compare September 17, 2026 19:30
@chasers
chasers removed this pull request from stack #3983 September 17, 2026 21:09
chasers added a commit that referenced this pull request Sep 17, 2026
Squashes the nine-PR load more stack into one commit: #3976, #3977, #3978,
#3979, #3980, #3981, #3982, #3984 and #3986. Merged as a unit so that main
never carries the intermediate states that #3984 corrects.

Pagination

- Keep the "Load more" spinner up until the page query returns.
- Bound a page request to the window in view and say so on the button.
- Store one page window per search in `EventPagination`. The label, the
  query, the cursor shift and the range growth all read it. The window no
  longer doubles on each click.
- Set the page window from a tail result too. A soft pause, play and pause
  used to leave the window nil and drop the next page request.
- Write an implied timestamp range into the query on a page request.
- Keep a one-sided `t:` bound when a page request makes the range explicit.
- Clamp a "next" range extension at now. Each empty click used to push the
  range max another window into the future.
- Cap the cursor of an empty "next" page at the request time.
- Remove timestamp clauses that can never match.
- Stop hiding the load more buttons on a short page.
- Disable the other button while a page request runs.
- Drop a page result or page error that no request waits for.
- Clear the page spinner when a search fails to parse.
- Log a page request that the LiveView drops.

Scrolling

- The LiveView drives every scroll. Every initial event page and every tail
  append pushes `scroll-to-bottom`. The server owns scroll intent. The hook
  owns viewport stability.

Cleanup

- Remove the unused sentinel row: the extra fetched row, `fetch_limit/0`
  and the `has_more?` field that nothing reads.
- Build the chart range in the search timezone. An implied range is no
  longer UTC written as local time.
- Remove the 750ms LiveView latency simulator in dev.

Tests

- Cover event pagination against a bigquery source and a postgres source.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@chasers

chasers commented Sep 17, 2026

Copy link
Copy Markdown
Contributor Author

Merged as part of the squashed stack in #3986, which landed on main as 9c9913b. The whole stack merged as one unit so that main never carried the intermediate states that #3984 corrects. This PR's commits are all included there.

@chasers chasers closed this Sep 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants