Field (zammad-dev, 9.9k files): every daemon restart after idle timeout re-enters a full reconcile, answers stay floors, and per-language resolution reads stale until a resolve pass completes #326
Labels
No labels
code-review
correctness
dos
performance
security
severity/high
severity/low
severity/medium
tech-debt
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
h-dv/code-index#326
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Field report from zammad-dev (A1X code-index-dev, 2026-10-07) on a Zammad 7.0.2 fork at /opt/zammad-dev, about 9.9k files, running v0.33.1 (
74f45e7b). Not yet reproduced here.Observed
project_overviewreportsstate=reconcilingand "no resolve transaction has run yet in this daemon", withresolve_progress pass_seq=0.language_ownership: package_owns, de.h-dv.ruby). Ruby resolution then reported 4.6% of 361k refs, with method_call at 0.5% / 5.3% and read at 0.8%.find_callersandchange_impactwere mostly empty for Rails code.To answer
pass_seq=0?pass_seq=0after an owner switch?I asked the reporter for the reconcile duration and the restart cause.
Reporter follow-up with
daemon.logdata, 2026-10-07. This narrows the issue.Item 1 (reconcile after restart): mostly withdrawn.
/mcpreconnect). Its startup reconcile also took 14 s.Item 3 (Ruby at 4.6%): probably real.
de.h-dv.rubyactivation was re-armed at 2026-10-06T19:18:13Z.Next: reproduce on a Rails app here, with builtin and package owners compared. The tier-1 corpus has no Rails app, so this is unmeasured territory for both owners.
Measured on Zammad 7.0.2: 5,155
.rbfiles and 359,509 Ruby refs.The package is not the cause
The builtin and
de.h-dv.rubyproduce exactly the same binds, joined on path, line, col, kind and occurrence. The gap is in the host resolver.Why refs go unresolved
A sample of 60 refs, each read at source:
require, andConst.methodcalls on themAcross the whole population, 133k unresolved refs name nothing declared in the project at all.
Fix (not yet released)
Const.methodbinds to the receiver class'sdef self.method. It is refused when the class also definesmethod=.Results:
Ticket::Article→Sequencer::…::Ticket::Article). The new lookup corrects them, and clears 69 more phantom binds.It ships together with #327, #328 and #329. Implicit-self calls that reach concern or inherited methods remain unmeasured.
Released in v0.34.0 (https://git.h-dv.de/h-dv/code-index/releases/tag/v0.34.0), via PR #333.
12b26efd,8129d3bb): lexical nesting first, then in-project ancestors, then the top level. Where several declarations match, the file that spells the constant wins.Const.methodbinds todef self.method. Wrong binds from compactclass A::B::Cdeclarations are re-pointed or cleared.Const.methodcalls resolve, 1,884 binds moved, 69 phantom binds cleared. Ruby resolution goes 4.6% → 11.7%, constants 11.7% → 64.2%. The opt-in Ruby package is bind-for-bind identical to the builtin.2a2e2629) re-resolves an existing Ruby index once on upgrade. No file is re-parsed.