Plan: the calculation is a correct average, not a count. Route churn is the number of prefixes announced or withdrawn, averaged over about the last minute, so a quiet minute gives a fraction such as 0.1. The status page will show "Route Churn/min" instead: the whole number of prefixes announced or withdrawn in the last full minute. The other per-second figures on / and /status (updates and messages per second) run in the thousands, so they will show whole numbers, with no decimal.
Model: opus-5-5
Plan: the calculation is a correct average, not a count. Route churn is the number of prefixes announced or withdrawn, averaged over about the last minute, so a quiet minute gives a fraction such as 0.1. The status page will show "Route Churn/min" instead: the whole number of prefixes announced or withdrawn in the last full minute. The other per-second figures on `/` and `/status` (updates and messages per second) run in the thousands, so they will show whole numbers, with no decimal.
Model: opus-5-5
Built as the plan above says, in #169. The figure is route_churn_per_min in the stream object of /api/v1/stats, which replaces route_churn_per_sec.
Model: opus-5-5
Built as the plan above says, in https://git.eeqj.de/sneak/routewatch/pulls/169. The figure is `route_churn_per_min` in the `stream` object of `/api/v1/stats`, which replaces `route_churn_per_sec`.
Model: opus-5-5
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.
Check the calculation. It's coming up with decimal number, which is obviously incorrect (how can 0.1 of a route churn?).
Plan: the calculation is a correct average, not a count. Route churn is the number of prefixes announced or withdrawn, averaged over about the last minute, so a quiet minute gives a fraction such as 0.1. The status page will show "Route Churn/min" instead: the whole number of prefixes announced or withdrawn in the last full minute. The other per-second figures on
/and/status(updates and messages per second) run in the thousands, so they will show whole numbers, with no decimal.Model: opus-5-5
Built as the plan above says, in #169. The figure is
route_churn_per_minin thestreamobject of/api/v1/stats, which replacesroute_churn_per_sec.Model: opus-5-5