8 month and I cannot index the repo… its not working…
I click in compute index and always get the 100% in 1 second…
Nothign happens
I use Macos Sequoia
It’s an issue many of us are having at the moment.
While it is frustrating, I don’t think flooding the forum with the exact same posts other have made will help you solve your problem.
Here is a link to a post with a similar issue and the type of logs you should send to make it easier for other people to help you, since “I use MacOs Sequoia” is a little superficial.
Ok, many thanks
I will take a look to this info
After reviewing the message, it’s like a joke… Nobody has solved the issue with clear instructions, and you are telling me that I am flooding
It might not help fix the issue, but it sends a clear message to the developers and to the PAYING USERS, that are blowing through their tokens and paying money for a product that doesn’t work as advertised.
2024-09-30 17:55:07.033 [info] Creating merkle client.
2024-09-30 17:55:07.033 [info] Done creating merkle client.
2024-09-30 17:55:07.033 [info] Doing a startup handshake.
2024-09-30 17:55:07.033 [info] Indexing job successfully done or aborted.
2024-09-30 17:55:07.036 [info] Finished initializing merkle tree in 3.0683749988675117 ms.
2024-09-30 17:55:07.036 [info] Doing the initial handshake with hash:
2024-09-30 17:55:07.045 [info] Handshake start
2024-09-30 17:55:11.041 [info] Handshake start
2024-09-30 17:55:19.044 [info] Handshake start
2024-09-30 17:55:35.044 [info] Handshake start
2024-09-30 17:56:01.180 [info] Handshake start
2024-09-30 17:56:06.008 [info] Indexing job successfully done or aborted.
2024-09-30 17:56:34.196 [info] Setting indexing intent to should-index
2024-09-30 17:56:34.197 [info] Creating merkle client.
2024-09-30 17:56:34.197 [info] Done creating merkle client.
2024-09-30 17:56:34.197 [info] Doing a startup handshake.
2024-09-30 17:56:34.205 [info] Finished initializing merkle tree in 8.217000000178814 ms.
2024-09-30 17:56:34.206 [info] Doing the initial handshake with hash:
2024-09-30 17:56:34.206 [info] Handshake start
2024-09-30 17:56:38.212 [info] Handshake start
2024-09-30 17:56:46.216 [info] Handshake start
2024-09-30 17:57:02.220 [info] Handshake start
nothing happens…
[error] Handshake failed:
2024-09-30 17:59:40.515 [error] Error: timeout in handshake with retry
at t.RepoClientMultiplexer.handshakeWithRetry (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-retrieval/dist/main.js:2:826553)
at w.getServerStatus (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-retrieval/dist/main.js:2:841881)
at w.startIndexingRepository (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-retrieval/dist/main.js:2:844181)
2024-09-30 17:59:40.515 [error] Handshake failed.
2024-09-30 17:59:40.515 [info] Indexing job successfully done or aborted.
2024-09-30 18:06:34.211 [info] Creating merkle client.
2024-09-30 18:06:34.212 [info] Done creating merkle client.
2024-09-30 18:06:34.212 [info] Doing a startup handshake.
2024-09-30 18:06:34.228 [info] Finished initializing merkle tree in 16.65633299946785 ms.
2024-09-30 18:06:34.229 [info] Doing the initial handshake with hash:
2024-09-30 18:06:34.245 [info] Handshake start
2024-09-30 18:06:38.237 [info] Handshake start
2024-09-30 18:06:46.239 [info] Handshake start
2024-09-30 18:07:02.246 [info] Handshake start
2024-09-30 18:07:28.369 [info] Handshake start
2024-09-30 18:08:20.508 [info] Handshake start
This suggests that the application is unable to complete its indexing task due to the connection issues.
These errors indicate that the Cursor application is having difficulty connecting to its backend services. This could be caused by:
- Network connectivity issues
-
Server-side problems
-
Firewall or security software blocking the connection
-
Outdated application version
-
Corrupted application data
To resolve these issues, you might try:
-
Checking your internet connection
-
Restarting the Cursor application
-
Updating the Cursor application to the latest version
- Temporarily disabling firewall or security software to see if it’s causing the issue
- Contacting Cursor support for further assistance
Try pinging these addresses to check availability, and make sure you’re not using a VPN, Zscaler, firewall, or anything else that could block access.
Thanks,
i created this thread
https://forum.cursor.com/t/persistent-handshake-failures-and-indexing-issues-with-cursor/20439