Show the writer-blocked state in index_freshness / project_overview #304
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#304
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?
Follow-up from v0.32.2 (PR #303).
Current behaviour: when another process holds the SQLite write lock, the daemon writer now backs off (
BEGIN IMMEDIATE, 25 ms→1 s) and writes a line todaemon.log. Nothing is shown in a tool reply. An agent that sees stale answers cannot tell "writer is blocked by another process" from "still indexing".Wanted:
index_freshnessandproject_overviewcarry awriter_blockedfield that says since when the writer has been blocked and names the lock holder where it is known. The render inserver.rsis the missing piece.Test: hold a write lock on
index.dbfrom a second connection, then assert the field is present. Mutation: remove the render and the test fails.