Sync status

What this server has read from GitHub and the other sources, and how fresh it is. The same data is at /api/v1/sync.

GitHub

Pull requests

33832 stored · every open one read · updates read up to 7m ago

Issues

10796 stored · every open one read · updates read up to 6m ago

History since 2020

still walking back; the state of nixpkgs fills in as it goes

Tokens

a server token · 0 lent by people who signed in

Passes

one every 10 minutes · the last took 8 minutes and ended 15m ago

nixpkgs and package health

Index

fa465a5e1bf7 · 36824 packages, 2136 NixOS modules, 105 teams · built 1h ago

Upstream versions

repology, read 1h ago · 18216 attributes behind upstream

Advisories

security tracker, read 1h ago · 1520 attributes with advisories

Hydra builds

asked when a package or module page is shown, kept one hour

Event log

Events

916 stored · newest from 8m ago · the Events API is polled, and GH Archive fills the gaps each hour

Faster with forwarded events

Today this server polls. A review, push or merge on GitHub shows here after the next pass: up to 18 minutes later (the interval plus the last pass). The Events API keeps only the last 300 events, so a busy hour loses some until GH Archive brings them, about an hour later.

If the NixOS organisation forwarded the nixpkgs webhooks here (an organisation webhook, or a GitHub App installed on the repository):

each change would show in seconds, not minutes;
no event would be lost in a burst;
the queues and the review credit would update the moment a review lands;
the passes would only check, so the rate limit would go to the history and to the issue bodies.

Maintainer Mode has no webhook receiver yet: GitHub sends webhooks only to the administrators of a repository. See docs/events.md.