Skip to content
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

Codebase indexing doesnt work #1998

Closed
athmanar opened this issue Sep 25, 2024 · 12 comments
Closed

Codebase indexing doesnt work #1998

athmanar opened this issue Sep 25, 2024 · 12 comments

Comments

@athmanar
Copy link

New cursor install on windows 11. Codebase indexing always gives error "Handshake failed"

[error] Error: Command failed: git config --get remote.origin.url
	at ChildProcess.exithandler (node:child_process:422:12)
	at ChildProcess.emit (node:events:514:28)
	at maybeClose (node:internal/child_process:1105:16)
	at Socket.<anonymous> (node:internal/child_process:457:11)
	at Socket.emit (node:events:514:28)
	at Pipe.<anonymous> (node:net:337:12)

2024-09-25 15:12:11.785 [info] Doing the initial handshake with hash: 59493feeb029b25394e73eb3116b6be8a6b9d956d8b135a1f2f7ad8067b698ec
2024-09-25 15:12:11.785 [info] Handshake start
2024-09-25 15:12:15.642 [info] Handshake start
2024-09-25 15:12:23.658 [info] Handshake start
2024-09-25 15:12:39.670 [info] Handshake start
2024-09-25 15:13:11.677 [info] Handshake start
2024-09-25 15:14:05.271 [info] Handshake start
2024-09-25 15:15:30.841 [error] Handshake failed:
2024-09-25 15:15:30.842 [error] Error: timeout in handshake with retry

2024-09-25 15:15:30.842 [error] Handshake failed. 2024-09-25 15:15:30.843 [info] Indexing job successfully done or aborted.

@jamesryancooper
Copy link

Having the same issue.

@Maxime-Fleurant
Copy link

Same issue, many people have problem with this, i m using wsl2 right now with a fresh install of cursor and this is happening

@soumen02
Copy link

Facing the same issue and created an issue #2035 (didn't realize this was created)

@ascanio
Copy link

ascanio commented Sep 30, 2024

Same here!
image

@georgeliu1998
Copy link

Just log out and log back in under "General - Account" and it should start working again!

@athmanar
Copy link
Author

athmanar commented Oct 2, 2024

@georgeliu1998 Sorry tried that and it doesn't work. Still get a similar error:

2024-10-02 10:06:07.652 [info] Setting indexing intent to should-index
2024-10-02 10:06:07.655 [info] Creating merkle client.
2024-10-02 10:06:07.655 [info] Done creating merkle client.
2024-10-02 10:06:07.656 [info] Doing a startup handshake.
2024-10-02 10:06:08.528 [info] Finished initializing merkle tree in 873.6273000240326 ms.
2024-10-02 10:06:08.530 [info] Doing the initial handshake with hash: ba088e651205d23a2561a2a127ba47f54bd00ba8382e36a8877b1168027f860d
2024-10-02 10:06:08.533 [info] Handshake start
2024-10-02 10:06:11.588 [info] Handshake start
2024-10-02 10:06:19.607 [info] Handshake start
2024-10-02 10:06:35.630 [info] Handshake start
2024-10-02 10:07:07.639 [info] Handshake start
2024-10-02 10:08:01.208 [info] Handshake start
2024-10-02 10:09:26.825 [error] Handshake failed:
2024-10-02 10:09:26.827 [error] Error: timeout in handshake with retry
at t.RepoClientMultiplexer.handshakeWithRetry (c:\Users\USER\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:826553)
at async w.getServerStatus (c:\Users\USER\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:841881)
at async w.startIndexingRepository (c:\Users\USER\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:844181)
2024-10-02 10:09:26.829 [error] Handshake failed.
2024-10-02 10:09:26.829 [info] Indexing job successfully done or aborted.

@duzefu
Copy link

duzefu commented Oct 8, 2024

same problem

@LegalPrimes
Copy link

same issue

@samgabrail
Copy link

samgabrail commented Oct 8, 2024

Same issue here, tried logging out and in and same problem. I'm also running Cursor installed on Windows 11 and have WSL2 running my repo

@athmanar
Copy link
Author

athmanar commented Oct 8, 2024

@georgeliu1998 This is making cursor unusable

@danperks
Copy link
Collaborator

danperks commented Oct 8, 2024

Closing for #2035
Feel free to comment in there!

@danperks danperks closed this as not planned Won't fix, can't repro, duplicate, stale Oct 8, 2024
@duzefu
Copy link

duzefu commented Oct 9, 2024

Same issue here, tried logging out and in and same problem. I'm also running Cursor installed on Windows 11 and have WSL2 running my repo

running below command in wls2

killall node

and reload windows , it works for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants