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
LanceDb/indexing issue #1218
Comments
@nmcostello thanks for making an issue for this—I've been seeing it the last couple of days in the preview branch as well, but oddly not in production. I've not yet confirmed that it doesn't happen after packaging, but that seems to be the case. Probably a git bisect will reveal the offending commit (assuming there is one) |
I am seeing this issue as well -- even after packaging and installing the extension (built from source). |
@spew @sestinj We fixed the issue today by doing a few things:
Edit: I ran |
Definitely happening with me. I've been seeing it for a few days. |
@nmcostello thanks for sharing the fix. Will try and get this integrated today |
Confirming that switching back to ^0.4.12 solves the issue (3749a8c). The original reason for pinning to 0.4.12 was this, which is now fixed, so the change is safe. I'm making a release for 0.9.127 right now, but I'll leave this issue for a couple of days to confirm that the new version solves the problem |
Before submitting your bug report
Relevant environment info
Description
When building from the main branch in the vscode debugger, no lancedb is created within the
.continue
directory. This leads to indexing issues when the@Docs
or@Codebase
contexts are used.Downloading an older version, leaving the
.continue
directory alone, then installingmain
again works because.continue/index/lancedb
already exists in that scenario.To reproduce
.continue
on your environment.install-dependancies
and run VSCode Debugger inmain
..continue/index/lancedb
.@Docs
or@Codebase
.Log output
The text was updated successfully, but these errors were encountered: