Codebase Index State Resets Randomly

Since the 0.45.X update, I’m unable to index the codebase for one of my big repo, and have to delete and re-create codebase index every time i have to use it.

Initial (Manual delete, plus resync):

And as soon as I’m trying to use the codebase:
pr3V0un.png (529×192)
When it gives error and if I check the Codebase indexing area, it’s always stuck around this area into syncing:
Mak32LT.png (845×232)

PS: I’m on latest V0.45.9. The interesting bit is it works on one repo, however, is breaking on this particular repo.

Hi,

Can you activated the Disable HTTP2 button? (search bar on top, >preferences: Open Settings UI, and search “http2” you will see the button)

after that, please check the composer/agent mode. some users say they overcome the problem by disabling http2, I think it will be solved if you are not on a corporate network. If you are on a corporate/organisation proxy address you will have a problem like mine, my problem persists.

gave this a try, but the issue still exists.

Hey, if you copy your codebase to a new folder, does that index correctly?

Having it at a new path will get Cursor to treat it as a whole new project. If it still fails, it suggests something specific about those files / code is causing an issue!

Nope the issue still continues, not sure what could be conflicting with this in the code, any suggestions what to look out for?

How big is your repo? Not sure how big we support, or if there is something we need to do for very big repos!

I guess it’s safe to say that it’s big, it’s a rushjs monorepo with 1 library and 4 react portals within it.
Tried calculating the LLM Token using gpt’s help: 894267
(source incase anyone else wants to try: ChatGPT - Repo Size for LLM)

Logs From the Output > Cursor Indexing:

2025-02-12 23:20:41.818 [info] Completed job unsuccessfully, will retry: .\src\components\last-contact\last-contact.tsx error: Bad unexpected error
2025-02-12 23:20:41.818 [info] fileQueue.length: 1799
2025-02-12 23:20:41.818 [info] Waiting for jobs to finish. currentIndexingJobs.length: 1 concurrentUploads.current: 1 fileQueue.length: 1799
2025-02-12 23:20:51.828 [info] Completed job unsuccessfully, will retry: .\src\components\last-contact\last-contact.stories.tsx error: Bad unexpected error
2025-02-12 23:20:51.828 [info] fileQueue.length: 1799
2025-02-12 23:20:51.829 [info] Waiting for jobs to finish. currentIndexingJobs.length: 1 concurrentUploads.current: 1 fileQueue.length: 1799
2025-02-12 23:21:01.837 [info] Completed job unsuccessfully, will retry: .\src\components\flags\if-flags.tsx error: Bad unexpected error
2025-02-12 23:21:01.837 [info] fileQueue.length: 1799
2025-02-12 23:21:01.837 [info] Waiting for jobs to finish. currentIndexingJobs.length: 1 concurrentUploads.current: 1 fileQueue.length: 1799
2025-02-12 23:21:11.843 [info] Completed job unsuccessfully, will retry: .\src\components\flags\hooks.ts error: Bad unexpected error
2025-02-12 23:21:11.843 [info] fileQueue.length: 1799
2025-02-12 23:21:11.843 [info] Waiting for jobs to finish. currentIndexingJobs.length: 1 concurrentUploads.current: 1 fileQueue.length: 1799
2025-02-12 23:21:21.857 [info] Completed job unsuccessfully, will retry: .\src\components\flags\readme.md error: Bad unexpected error
2025-02-12 23:21:21.857 [info] fileQueue.length: 1799
2025-02-12 23:21:21.857 [info] Waiting for jobs to finish. currentIndexingJobs.length: 1 concurrentUploads.current: 1 fileQueue.length: 1799

Hey, we are seeing some increased reports regarding indexing errors, but should have this resolved soon hopefully!

1 Like