What stands between routewatch and a 1.0 release candidate. Every open bug is fixed before any release-candidate tag (sneak/project-management#32). The state is kept in the comments here.
Model: opus-5-5
What stands between routewatch and a 1.0 release candidate. Every open bug is fixed before any release-candidate tag (https://git.eeqj.de/sneak/project-management/issues/32). The state is kept in the comments here.
Model: opus-5-5
clawbot
self-assigned this 2026-10-14 22:25:51 +02:00
Waiting for a review: #82 (critical), #83, #79 (after two reworks), #85. PR 83 lets a handler's batch grow without limit while a write runs; its reviewer weighs that against the 5 GiB memory budget.
Waiting for a rework: #80 (two findings, and a rebase).
Open issues with no PR: #56 (critical, after 55), #74 and #76 (streamer, unblocked), #75 (after 55), #69 (after 65), #72 (README and TODO.md, last; plan on the issue).
Live run of the code before these fixes (00e51d2, 5 hours): memory peaked at 616 MiB, the database reached 6.9 GB with 15.8 million live routes, and the prefix handler dropped a fifth of its updates. The live tables keep one row per prefix and peer, so they keep growing toward peers times prefixes. Disk size at steady state, and start-up time on a large database against upaas's 60-second health check, are still to be measured on the fixed code.
State on 2026-10-14, when this repository's manager slot ended. `next` is green.
Done on `next`: https://git.eeqj.de/sneak/routewatch/issues/53, https://git.eeqj.de/sneak/routewatch/issues/54, https://git.eeqj.de/sneak/routewatch/issues/57, https://git.eeqj.de/sneak/routewatch/issues/67, https://git.eeqj.de/sneak/routewatch/issues/68, https://git.eeqj.de/sneak/routewatch/issues/71, https://git.eeqj.de/sneak/routewatch/issues/73.
Open PRs:
- Waiting for a review: https://git.eeqj.de/sneak/routewatch/pulls/82 (critical), https://git.eeqj.de/sneak/routewatch/pulls/83, https://git.eeqj.de/sneak/routewatch/pulls/79 (after two reworks), https://git.eeqj.de/sneak/routewatch/pulls/85. PR 83 lets a handler's batch grow without limit while a write runs; its reviewer weighs that against the 5 GiB memory budget.
- Waiting for a rework: https://git.eeqj.de/sneak/routewatch/pulls/80 (two findings, and a rebase).
Open issues with no PR: https://git.eeqj.de/sneak/routewatch/issues/56 (critical, after 55), https://git.eeqj.de/sneak/routewatch/issues/74 and https://git.eeqj.de/sneak/routewatch/issues/76 (streamer, unblocked), https://git.eeqj.de/sneak/routewatch/issues/75 (after 55), https://git.eeqj.de/sneak/routewatch/issues/69 (after 65), https://git.eeqj.de/sneak/routewatch/issues/72 (README and `TODO.md`, last; plan on the issue).
Live run of the code before these fixes (`00e51d2`, 5 hours): memory peaked at 616 MiB, the database reached 6.9 GB with 15.8 million live routes, and the prefix handler dropped a fifth of its updates. The live tables keep one row per prefix and peer, so they keep growing toward peers times prefixes. Disk size at steady state, and start-up time on a large database against upaas's 60-second health check, are still to be measured on the fixed code.
Next unit: reviews of https://git.eeqj.de/sneak/routewatch/pulls/82 and https://git.eeqj.de/sneak/routewatch/pulls/83, then https://git.eeqj.de/sneak/routewatch/issues/56.
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.
What stands between routewatch and a 1.0 release candidate. Every open bug is fixed before any release-candidate tag (sneak/project-management#32). The state is kept in the comments here.
Model: opus-5-5
State on 2026-10-14, when this repository's manager slot ended.
nextis green.Done on
next: #53, #54, #57, #67, #68, #71, #73.Open PRs:
Open issues with no PR: #56 (critical, after 55), #74 and #76 (streamer, unblocked), #75 (after 55), #69 (after 65), #72 (README and
TODO.md, last; plan on the issue).Live run of the code before these fixes (
00e51d2, 5 hours): memory peaked at 616 MiB, the database reached 6.9 GB with 15.8 million live routes, and the prefix handler dropped a fifth of its updates. The live tables keep one row per prefix and peer, so they keep growing toward peers times prefixes. Disk size at steady state, and start-up time on a large database against upaas's 60-second health check, are still to be measured on the fixed code.Next unit: reviews of #82 and #83, then #56.
Model: opus-5-5