plugin status reports a live daemon build as "interrupted mid-build — run plugin retry" #346

Closed
opened 2026-10-08 21:58:04 +02:00 by buildagent · 1 comment
Member

Field report from zammad-dev (A1X code-index-dev, 2026-10-08), on 0.34.1.

What happened. The daemon (pid 855440) was building generation 5 after the upgrade. At that moment project_overview showed pending_state "building" with 6,518 of 10,208 files done. Yet code-index plugin status printed:

activation owed: generation 5 was interrupted mid-build — code-index plugin retry

That advice is wrong for a build that is still running. The reporter correctly did not run retry, because the daemon was the activation owner. A less careful user would have started a second activation against a live one.

Expected. When a live process holds the activation (the daemon is alive and owns the build), status should say so, e.g. building generation 5 (owner: daemon pid …, 6,518/10,208 files), and offer no retry advice. The "interrupted" wording, with its retry hint, belongs only to a build whose owner is gone.

Outcome, for the record. v0.34.1 fixed #334 in the field. Activation, build and resolve took about 4 minutes, with no hang and no crash. Generation 5 is active and generation 4 superseded, with "owed: nothing" and refs_resolved 82,738.

Related: #334, #341.

Field report from zammad-dev (A1X code-index-dev, 2026-10-08), on 0.34.1. **What happened.** The daemon (pid 855440) was building generation 5 after the upgrade. At that moment `project_overview` showed `pending_state "building"` with 6,518 of 10,208 files done. Yet `code-index plugin status` printed: `activation owed: generation 5 was interrupted mid-build — code-index plugin retry` That advice is wrong for a build that is still running. The reporter correctly did not run `retry`, because the daemon was the activation owner. A less careful user would have started a second activation against a live one. **Expected.** When a live process holds the activation (the daemon is alive and owns the build), status should say so, e.g. `building generation 5 (owner: daemon pid …, 6,518/10,208 files)`, and offer no retry advice. The "interrupted" wording, with its `retry` hint, belongs only to a build whose owner is gone. **Outcome, for the record.** v0.34.1 fixed #334 in the field. Activation, build and resolve took about 4 minutes, with no hang and no crash. Generation 5 is active and generation 4 superseded, with "owed: nothing" and `refs_resolved` 82,738. Related: #334, #341.
Author
Member

Released in v0.35.0 (https://git.h-dv.de/h-dv/code-index/releases/tag/v0.35.0), via PR #351.

plugin status now probes for the activation's owner and reports one of three states:

  • Owner running: it names the live daemon's build with the pid, the port and how many queued files have settled. It gives no retry advice.
  • No owner: it keeps the "interrupted — retry" line.
  • Owner can't be determined: it says so.
Released in v0.35.0 (https://git.h-dv.de/h-dv/code-index/releases/tag/v0.35.0), via PR #351. `plugin status` now probes for the activation's owner and reports one of three states: - **Owner running:** it names the live daemon's build with the pid, the port and how many queued files have settled. It gives no retry advice. - **No owner:** it keeps the "interrupted — retry" line. - **Owner can't be determined:** it says so.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
h-dv/code-index#346
No description provided.