mesh-issues: a milestone or commit link moves no issue and keeps no worker current (issue 1781) #510

2026-10-26T20:16:23Z

mesh-tools commented

2026-10-26 20:16:23 +00:00

Issue 1781. Seeding the milestones linked 188 issues at once, and every one of them read as moved at the seed's minute (moved in list rows and in knowledge-base.progress). On an issue being worked on, the link also counted as its worker's activity.

A milestone link only places an issue, and a commit link only names what fixed it. Neither is work on the issue. So lastMoved leaves them out, and link no longer counts them as the worker's activity, whether a link is added or removed. Each link keeps its own time, so for an issue without a worker the real moved time comes back with no change to stored data.

The overwritten activity times of the 22 issues being worked on stay as they are. Notes 10 and 11 on issue 1781 list them and say why.

Tests: TestListSaysWhenEachIssueMovedAndKeepsTheLinkedOnes is extended. An issue being fixed and then linked to a milestone and a commit keeps its moved time and its worker's activity time. It fails with tracker.go reverted. The unit suite passes and go vet -tags integration is clean. Try try-1793041943691783937 passed at 21:14 CET.

Reviewed-by: review-1781b@shanks at 854dbfb3f3

Issue 1781. Seeding the milestones linked 188 issues at once, and every one of them read as moved at the seed's minute (`moved` in list rows and in `knowledge-base.progress`). On an issue being worked on, the link also counted as its worker's activity. A milestone link only places an issue, and a commit link only names what fixed it. Neither is work on the issue. So `lastMoved` leaves them out, and `link` no longer counts them as the worker's activity, whether a link is added or removed. Each link keeps its own time, so for an issue without a worker the real moved time comes back with no change to stored data. The overwritten activity times of the 22 issues being worked on stay as they are. Notes 10 and 11 on issue 1781 list them and say why. Tests: `TestListSaysWhenEachIssueMovedAndKeepsTheLinkedOnes` is extended. An issue being fixed and then linked to a milestone and a commit keeps its moved time and its worker's activity time. It fails with tracker.go reverted. The unit suite passes and `go vet -tags integration` is clean. Try try-1793041943691783937 passed at 21:14 CET. Reviewed-by: review-1781b@shanks at 854dbfb3f3f073b235163e0c5d6dc7e9d440deba

mesh-tools added 1 commit 2026-10-26 20:16:23 +00:00

mesh-issues: a milestone or commit link moves no issue and keeps no worker current (issue 1781)

mesh/delivery merged: source.main moved to novox/mesh-catalog@7c5c29421f02

Details

mesh/check being carried to 854dbfb3f3f0 on 7c5c29421f02 | from 3690c149c4ad

854dbfb3f3

The seed linked 188 issues at once and every one read as moved at the seed's minute, hiding when each
really moved; on a worked issue the link also counted as its worker's activity. These links only place
an issue, so last-moved and the worker's activity leave them out.

mesh-tools commented

2026-10-26 20:16:29 +00:00

Delivery novox/mesh-catalog@854dbfb3f3f0 — merged since 2026-10-26T20:17:11Z

Source — source.main moved to novox/mesh-catalog@7c5c29421f. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

2026-10-26 20:16 (new) → proposed (announced): novox/mesh-catalog#510's head announced
2026-10-26 20:16 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-10-26 20:17 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/mesh-catalog@854dbfb3f3f0` — **merged** since 2026-10-26T20:17:11Z **Source** — source.main moved to novox/mesh-catalog@7c5c29421f02. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-10-26 20:16 (new) → proposed (announced): novox/mesh-catalog#510's head announced - 2026-10-26 20:16 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-10-26 20:17 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools merged commit 7c5c29421f into main

2026-10-26 20:17:10 +00:00

mesh-tools deleted branch fix/1781-moved-ignores-milestone-links

2026-10-26 20:17:10 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#510