fix(indexer): let watcher edits interrupt forced resolution #403
No reviewers
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!403
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/forgejo-issues-top-down"
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?
Watcher edits could wait behind a complete resolve after eight unresolved flushes: the starvation guard deliberately stopped arming preemption. Reuse the existing durable resolver queue at that boundary, commit one bounded reference batch, then yield to waiting writer work.
Carry a matching checkpoint across body-only edits, including requeued incoming calls to reminted symbol IDs. Outline, classification, delegated-pool, project-alias and external snapshot changes still invalidate it. Cancellation stays immediate. Add one debug record per committed watcher batch and resolve scheduling records.
Fixes #390's reproduced forced-pass preemption hole. This bounds forced work to a reference batch, not a wall-clock deadline; the original zammad field report still needs confirmation. No schema, ABI or plugin artifact changes. Bump the core patch version to 0.41.5; all external dependency lock records are unchanged.
Validation:
--no-default-features, separate CLI/daemon/MCP and worker invocations): fresh adoption of seven language packages and refusal of all seven removed builtin owners passed with published bundles; no project config was created.bf4e1023a46e8345d2ec500c2b8a9c571882ad6epassed all four workflows: Windows, core and corpus, packages, and pilots. Core: 4,998 main tests and 37 serial timing tests passed; native Windows: 4,781 main tests and 27 serial timing tests passed.Published as stable/latest v0.41.5; release workflow 6230 passed all ten jobs. Independent published verification passed: all four archive hashes; all seven bundled package/signature pairs unchanged in each archive; all eleven signed-channel plugin records unchanged and all 30 package versions retained; seven checksum sidecars and installer Git blob identities; fresh seven-language adoption, removed builtin refusal, and live C# alias add/remove through the same daemon. The previous and current released runtimes both verify the new signed catalog/channel with compiled-in anchors alone.
#401 remains open: PR #402 fixed a reproduced stale-PID cleanup defect, but did not establish the original initialize EOF's cause.