fix(search): get_symbol_info AMBIGUOUS + docs + README badge - #33
Merged
Merged
Conversation
ManSio
commented
Sep 10, 2026
ManSio
commented
Owner
- fix(search): get_symbol_info returns AMBIGUOUS when len(defs)>1 (issue Ambiguous identical-symbol lookup silently picks first match; write path can hit wrong file #21 read-path fork). Shows all candidates instead of silently picking defs[0]. 3 new tests, 1704 total, ruff clean.- docs(experiments): VOR catch-up (exp1) and HEAD-polling (exp3) results added to EXPERIMENTS_LOG.md and AGENT_DIARY.md.- docs(readme): bump tests badge to 1773 and tools count to 64.
added 3 commits
September 10, 2026 06:02
…en(defs) > 1 Closes issue #21 read-path fork. When build_call_graph returns multiple definitions, the tool now surfaces all candidates (up to 10) instead of silently picking defs[0]. Single-definition path is unchanged. Verified: 3 new tests + 38 related tests passed, 1704 total, ruff clean.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…interval fix Research (Exp 2 chain): inform-the-agent is unreliable (agent can ignore STALE alerts, PlanFence 30/30 failures); server-side blocking gives 0% stale. Add a fail-closed gate so memory reads/writes no longer silently use stale data. - config: MemoryConfig.freshness_gate (off|read|write|both, default both) - read gate: intel_get_project_memory marks unverified nodes stale_unverified on incomplete VOR pass, marks domain CONSISTENT on full pass, surfaces freshness_gate status in stats and ui_formatter - write gate: intel_add_memory_node refuses while memory is STALE with pointer to intel_get_project_memory - dirty tree: _is_dirty() git-status probe with TTL cache; dirty fingerprints rebuilt every pass (never persisted) and dirty verdicts bypass the cache entirely (dirty-bit in cache key), closing the notify->commit toxic interval - background verify marks memory CONSISTENT after a full pass - tests: conftest autouse ConsistencyTracker reset (singleton leak)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.