-
Notifications
You must be signed in to change notification settings - Fork 3
[travsr-mcp] resolve the embed hook backend per repo, not machine-wide #770
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ritikpal1122
wants to merge
2
commits into
Travsr-com:master
Choose a base branch
from
ritikpal1122:fix/547-mcp-repo-backend
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two notes on this helper, neither blocking.
The duplication is three copies, not two, and the third already lives in the crate you name as the right long-term home.
resolve_backend_paths(embed_catalog.rs:1798-1802) already opens with these exact two lines, already takes adb_path, and is already intravsr-plugin-host:I think your argument for not consolidating is right, and for the reason you give: the bug was a call site that never learned the rule, not an implementation that diverged, so a shared home would not have caught it. But it does change the cost of the follow-up you describe. Exposing what is already written there, as a
pub fn backend_id_for_db(db_path: &Path), is a much smaller change than renamingactive_backend_idacross every caller, and it gets most of the same benefit: the per-repo rule becomes something you call rather than something you remember. Worth mentioning in the issue you file.The
parent().parent()verification misses a branch. The description says it was verified rather than assumed, viamain.rs:1263buildingrepo_root.join(".travsr/graph.db"). That is theelsearm; the statement isso
travsr mcp --stdio --db /somewhere/else.dbhands this an arbitrary path andparent().parent()is not a repo root.The behaviour is fine, which is why this is a note rather than a finding:
repo_backend_idfinds noembed.tomlthere and it falls through toactive_backend_id(), which is precisely today's behaviour. Andresolve_backend_pathsmakes the identical assumption on the spawn side, so hook and spawn still agree even in that case, which is the invariant that actually matters. Worth a sentence in the doc comment saying a--dboutside a repo degrades to the machine default, since the next reader ofparent().parent()will ask.