-
Notifications
You must be signed in to change notification settings - Fork 771
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
Repo indexing is confused #5302
Comments
can you provide some repro sample project? or step by step instructions on how to repro it? |
I can't really provide a repo, but I can give more logs if needed. Aren't the logs I've added enough to get an idea why this happens ? Thank you ! |
@andreigh I am not sure I am following the repro step. and I can't access the log you linked. It said so, you have same repo cloned in 2 folders. let's say so, where did it go? |
Hello, this is the log. No, it didn't happen. When I click on "s" on a file in repository B it opens the file in repository A where "s" is defined. 25e59b6598ac4a6e001ddb9e3b5df0a1-c36cb496677370fad6a411101c74476cc75b3aa7.zip |
@andreigh so the log is not full log, it is random portion of the full logs. we need full logs to see what source files are loaded into the server and what options you have and etc. otherwise, there is not much we can do. if capturing logging is an issue, can you provide us some sample workspaces that we can use to repro the issue? the thing we are confused is that our server is isolated between each vscode or workspace, so confused how go to def on one |
Can you please check this ? Thank you |
I added an issue so we can just get log ourselves. unfortunately, the log you shared is just random part of full log. not unedited full log that we need to figure out how things are configured and executed. |
by the way, I see from the log this
I think your setting is messed up somewhere causing us to not ignore |
Environment data
Code Snippet
Repro Steps
I have the same repository cloned in multiple folders, let's say "/driving" and "/driving2", and am working on both but in different VSCode instances. In the VSCode instance open on "/driving2", when I command-click a symbol:
for example tracking.fetch_model
it navigates to the source file where the symbol is defined (tracking.py), but in the other folder the repo is cloned ("/driving"), not the tracking.py under "/driving2", as it should.
Expected behavior
It should navigate to the correct file under "/driving2", the folder open in VSCode.
Actual behavior
It navigates to a file in the wrong folder.
Logs
https://git.zooxlabs.com/gist/agheorghe/25e59b6598ac4a6e001ddb9e3b5df0a1
The text was updated successfully, but these errors were encountered: