circagraph
Sign inSign up

openchronology/timeline-app on GitHub

The OpenChronology repository on GitHub, mirrored by och-import-github: issues and pull requests as durations (ongoing while open), what happened to them as moments, plus releases, milestones, commits and branches. The Branches view shows the most recently active branches each in a track of its own.

Source: https://github.com/openchronology/timeline-app

3,131 moments · 2026-10-05 CE 20:21:49 UTC – 2026-11-16 CE 12:10:45 UTC · by @athan · @athan

#564 Read a separation's tracks in one request, with the arcs once

–

  • github
  • github/openchronology/timeline-app
  • github/openchronology/timeline-app#564
  • pull request
  • state:merged

The openchronology/timeline-app timeline on timescale.info felt slow with its Branches view (seven separations). Each new window needed eight requests, sent one after another, and every branch track downloaded the same 256 arcs again. On the server each read takes only 10–30 ms, so nearly all the time was round trips: about 2 s per window on a phone, plus about 650 KB of repeated arcs. ## Changes - **Server:** adds a `kind: "tracks"` query (`store.queryTracks`). It takes every track's filter (the rest last) and the windows missing from the tracks' caches, at most eight, one per track. Each window is answered as an overview of its track would be. The arcs come only on track 0's window, with each end naming the first separated track it is on (`aTrack`, `bTrack`, or null for the rest). Without an account, each window past the first counts toward the query limit. - **Client:** `ComparisonView.batch` reads every missing window at once before drawing from the caches. Separations of server timelines use it. The desktop store and timelines held in memory still read each track separately. `arcAxes` places ends by `aTrack`/`bTrack`. - **Docs:** OpenAPI (`TimelineQuery`, `EdgeBand`) and `docs/relationships.md`. ## Tests - `test/relationships-postgres.mjs`: the frames match separate overviews, and each end's track matches a lookup in each view in turn. - `test/http.test.mjs`: malformed `tracks` reads answer 400. - `test/separated-arcs-live-postgres.mjs`: with one separation and with two ("war", "trade"), arcs end at their markers on three tracks. Tracks are read only through `tracks` requests. - Locally: the unit tests (525) pass, along with the relationships, separated-arcs, views and default-view PostgreSQL/browser tests. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/circagraph/timeline-app/pull/564

Related

Open #564 Read a separation's tracks in one request, with the arcs once in the timeline

#564 Read a separation's tracks in one request, with the…