-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
ERROR:root:IndexFlat.search() missing 3 required positional arguments: 'k', 'distances', and 'labels' #61
Comments
same |
Having similar issue: |
Anyway to resolve this? I'm getting the same issue |
This is what happens (in my opinion): FAISS has different wheels for arm64 chips & Intel/AMD chips. If you vectorise a document using arm64, you should use FAISS to interact with this document on a arm64 machine. So right now, my mac is arm64 and I vectorised docs on my mac using the arm64 wheel. However in the Azure functions, it attempts to use the Intel wheel which is slightly different. Intel/AMD chips use something called AVX2 support in FAISS (no idea what it actually is but it's different to the way arm64 machines use FAISS). So how can you solve this? |
I opened an issue for the faiss-cpu lib here: kyamagu/faiss-wheels#74 |
I'll also share that I had the error when I created the vectorstore using windows cmd and its environment but then ran |
same problem when build app on windows and next put into docker container.... |
I had the same issue. I created my vectorstore on my window machine but when I deployed it on the AWS Ubuntu server, I had the issue. I resolved it by creating a new vectorestore(knowledgebase) on Ubuntu. Everything works well. |
me, too |
+1 |
Same |
My computer is arm64. I stored the vector in the index and pkl files locally, then deployed it to the Linux environment, and built an API for searching the index and pkl files in different situations, for larger file, I found that an error will appear when calling the search API for the second time, but smaller files do not have this problem. my code:
error output:
I also discovered another strange phenomenon. For larger index and pkl files, this method can stably reproduce the error reported on the second api call.
However, through this method, the same error will be reported for the first time. The problem occurs in
|
I got the same error while deploying my app on render. This is the issue with faiss. First I used faiss-cpu==1.7.4 and then changed it to faiss-cpu==1.7.2 in requirements file and the issue was solved. |
You're a lifesaver. I was dealing with this issue for almost 4 hours and wasn't sure why. Then read about faiss-cpu having different wheels in different OS and downgrading it to 1.7.2 fixed the problem. :)) |
I run my code in Windows Conda and all is OK. I tried in Ubuntu 20 and encountered the same issue. So I downgraded faiss-cpu to 1.7.2 and everything is OK |
I also fixed the issue on Ubuntu 20. Thanks! |
Is there going to be any solution to this absolute amateur hour issue other than version locking to 1.7.2? |
Hi All there |
I'd like to bump this issue. I'm running a job on my m3 mac to build the search index and then deploy it in linux with docker. This is incredibly annoying that the same versions are not compatible across architectures. |
Using Faiss through txtai does not have this problem.
https://github.com/neuml/txtai
…On Thursday, September 12th, 2024 at 7:22 PM, Brad Willard ***@***.***> wrote:
I'd like to bump this issue. I'm running a job on my m3 mac to build the search index and then deploy it in linux with docker. This is incredibly annoying that the same versions are not compatible across architectures.
—
Reply to this email directly, [view it on GitHub](#61 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AO4JE5HQHIL34Y6QJ2GTAELZWHEVDAVCNFSM6AAAAAAXHKBXKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBWHA2DMNJTGY).
You are receiving this because you commented.Message ID: ***@***.***>
|
Please update the Faiss Version and try it again i was facing similar issue with version 1.8.0 after i downgraded it to 1.7.2 it resolved my issue.. |
It's good to hear that it worked for you 😊.
…On Mon, 19 Feb, 2024, 10:58 pm Suhas M L, ***@***.***> wrote:
I got the same error while deploying my app on render. This is the issue
with faiss. First I used faiss-cpu==1.7.4 and then changed it to
faiss-cpu==1.7.2 in requirements file and the issue was solved.
You're a lifesaver. I was dealing with this issue for almost 4 hours and
wasn't sure why. Then read about faiss-cpu having different wheels in
different OS and downgrading it to 1.7.2 fixed the problem. :))
—
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFTZWATASMCNVOIYJY2WMXLYUODUFAVCNFSM6AAAAAAXHKBXKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJSHEZDIMZRGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
It resolved for me as well |
I am not sure where this is coming from? I was thinking maybe FAISS?
Also is this project supposed to work? I feel like I have dumped 3-4 hours into making updates for a variety of issues
The text was updated successfully, but these errors were encountered: