Every version upgrade re-extracts the whole project: "the recorded activation cannot be recovered" although packages and files are unchanged #590

Open
opened 2026-11-14 20:02:49 +01:00 by buildagent · 0 comments
Member

Report

From the zammad-dev field report of 2026-11-08 (v0.41.44 → v0.41.45, a large Ruby/Vue project), found again during dogfood triage batch 25 and not tracked by any open issue:

each version change logs the recorded activation cannot be recovered; re-extracting every walked file reason=no_match: none of 17 candidate activation(s) is the recorded one; something besides [languages] moved: packages, container... — same 5 packages/digests, nothing else changed, yet a full re-extract + resolve (~12 min) on 0.41.44 and again on 0.41.45. Expected: recover the recorded activation when only the host version changed.

What is not known yet

  • Whether this is by design: the activation identity includes the worker's identity line, and a release whose extraction code changed must re-extract. If so, the message is wrong ("something besides [languages] moved: packages, container" names inputs that did not move) and the cost is paid on every upgrade, including releases that changed nothing an extractor reads.
  • Whether v0.41.53 still does it. Not re-tested since the report.

Acceptance

  • Reproduce: one project, the same approved packages, index with release A, start release B.
  • If nothing an extractor's output depends on changed between A and B, the recorded activation is recovered and no file is re-extracted.
  • If something did change, the log and the payload name exactly what changed (the worker's extraction identity), not inputs that are identical.
  • The upgrade path of a release that bumps the index schema is stated separately (that one rebuilds by design).
## Report From the zammad-dev field report of 2026-11-08 (v0.41.44 → v0.41.45, a large Ruby/Vue project), found again during dogfood triage batch 25 and not tracked by any open issue: > each version change logs `the recorded activation cannot be recovered; re-extracting every walked file reason=no_match: none of 17 candidate activation(s) is the recorded one; something besides [languages] moved: packages, container...` — same 5 packages/digests, nothing else changed, yet a full re-extract + resolve (~12 min) on 0.41.44 and again on 0.41.45. Expected: recover the recorded activation when only the host version changed. ## What is not known yet - Whether this is by design: the activation identity includes the worker's identity line, and a release whose extraction code changed must re-extract. If so, the message is wrong ("something besides [languages] moved: packages, container" names inputs that did not move) and the cost is paid on every upgrade, including releases that changed nothing an extractor reads. - Whether v0.41.53 still does it. Not re-tested since the report. ## Acceptance - Reproduce: one project, the same approved packages, index with release A, start release B. - If nothing an extractor's output depends on changed between A and B, the recorded activation is recovered and no file is re-extracted. - If something did change, the log and the payload name exactly what changed (the worker's extraction identity), not inputs that are identical. - The upgrade path of a release that bumps the index schema is stated separately (that one rebuilds by design).
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#590
No description provided.