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

#537 Ongoing durations: an end that is "now"

–

  • github
  • github/openchronology/timeline-app
  • github/openchronology/timeline-app#537
  • issue
  • state:closed
  • label:enhancement

Part of #533. Open work items (an assigned issue, a card in progress, a shift not yet clocked out), and history such as "2022–present", need a duration whose end is **now**, still moving, until it is closed. ## Proposal A third kind of duration endpoint, beside a fixed time and `{"moment": id}`: ```json { "id": "issue-412", "start": "1762560000", "end": { "ongoing": true }, "metadata": { "title": "Fix the login loop" } } ``` - **Meaning.** The end is the current time. Closing the duration replaces it with a fixed time (or a moment anchor). Only an `end` may be ongoing. - **Not "uncertain".** An end that happened at an unknown time is a precision question and is out of scope here. - **Only where "now" exists.** Accepted only on timelines whose time display is Gregorian, where a coordinate maps to Unix seconds through the preset's origin and scale. Elsewhere validation refuses it with a clear message. - **Indexes.** An ongoing end is stored as unbounded in the interval trees (browser `durationTree`, the server's AVL index, `native-store/src/intervals.rs`), so cached extents never go stale. It is cut off at the current time only when a band is resolved for a window. - **Drawing.** The band runs to "now" and ends with a fade or an arrow, so it does not read as ending at the view's edge. The duration dialog gets **Ongoing** as a third endpoint choice, and its details say "ongoing". - **Formats and API.** `.ochx`, `.och` (SQLite), the HTTP API and OpenAPI schema, merges and history, and export and conversion (`och-convert`). - **Summaries.** Collapsed-duration summaries and counts treat an ongoing duration as ending now. ## Done when - Ongoing durations round-trip through every format and the API, and are refused on non-Gregorian timelines. - They draw to the current time and keep growing while the page is open. - Tests cover validation, the three interval trees, window queries and summaries. - `docs/durations.md` describes them. https://github.com/openchronology/timeline-app/issues/537

Related

Open #537 Ongoing durations: an end that is "now" in the timeline

#537 Ongoing durations: an end that is "now"