Reply honesty: five disclosure defects found dogfooding v0.38.0 (wrong unmeasured-population prose, concise rows drop resolved_by, startup ghost labels, "nearest" wording, cursor/did_you_mean diagnoses) #379
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#379
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?
Found dogfooding v0.38.0 (
4ab97367) on this repo. All five are in reply text or fields; the index itself was correct.The UNMEASURED POPULATION prose ignores the row's reason.
compose_evidence_semantics(mcp-server/src/server.rs~31840) emits one fixed paragraph, written forno_use_reference_channel. It says "no reference kind captures a USE … A0in this reply is STRUCTURAL".find_callers(all_plugins)ships that paragraph for a row whose reason isuses_may_be_generated, in a reply withtotal_resolved: 262.search_symbolsexplains the same symbol correctly.reason.Concise
find_references/find_callersrows dropresolved_byandinfluence. The tool descriptions say concise keepsfile/line/kind/name/target_id/resolution/resolved_by/influence. Make the rows and the description agree.Deleted files are mislabelled during the startup reconcile window. 82 files deleted while no daemon ran were listed until the first reconcile removed them (about 70 s):
project_overviewcounted them aspermanently_unclaimed(symbol_blind_extensionsrust/permanently_unclaimed, 82).list_filesmarked each onedisk_unmeasured: not_readable.The
langhint's "nearest" wording.search_text(lang:"py")says "the 12 nearest of the 20 spellings":python(an extension match) and then 11 alphabetical ones. Only the near ones may be called nearest.Two misdiagnoses.
search_symbols(query:"all_plugins", lang:"rs")shipsdid_you_mean: ["ALL","all","ALLOC","alloc"](other symbol names), although its ownempty_populationshows thelangfilter alone emptied the result."2@x") is refused as "belongs to a DIFFERENT index snapshot". It is malformed, not stale.Released in v0.39.0 (PR #386,
25a45918). Every item:list_files: reportsnot_on_diskfor a file that is gone. A real permission error staysnot_readable.langhint: says "nearest" only for an extension, a prefix, or a typo within 1–2 edits.did_you_mean: no longer offered when a filter, not the query, emptied the result.Also in this release, for the indexer:
Two small leftovers from the dogfood of this release are in the next train:
search_symbolslang:"rsut"does not say "nearest" in its "all N fit" branch, and a project-pinned reply reports the primary project'sindex_state.