reorproject / reor

Private & local AI personal knowledge management app.

Home Page:https://reorproject.org

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Persistent "Initializing vector database..." Error on Windows 11

yuchiho2008 opened this issue · comments

Description:
I am experiencing a recurring issue where the application always displays "Initializing vector database..." upon launch. Despite multiple reinstalls and attempts to clear any residual files, the issue persists. When I attempt to start the application via the icon shortcut, it bypasses the setup menu and directly shows "Initializing vector database...". After a few minutes, a JavaScript error occurs in the main process.

Steps to Reproduce:

Launch the application using the desktop icon shortcut.
Observe the application bypassing the setup menu and displaying "Initializing vector database...".
Wait for a few minutes.
A JavaScript error in the main process is displayed.
Expected Behavior:
The application should successfully initialize the vector database and proceed to the main interface without errors.

Actual Behavior:
The application gets stuck at "Initializing vector database..." and eventually throws a JavaScript error in the main process.

Environment:

OS: Windows 11

Additional Information:

Reinstalling the application did not resolve the issue.
The issue occurs consistently with every launch.

image

To resolve the persistent 'Initializing vector database...' error on Windows 11, follow these steps:

  1. Check Database Initialization: Ensure the database schema is correctly initialized. Verify the CreateDatabaseSchema function in /electron/main/database/Schema.ts.

  2. Verify LanceDB Table: Confirm the LanceDB table is created correctly. Check the GetOrCreateLanceTable function in /electron/main/database/Lance.ts.

  3. IPC Handlers: Ensure IPC handlers for database operations are correctly set up in /electron/preload/index.ts. Specifically, check handlers like indexFilesInDirectory and getDatabaseFields.

  4. Store Migration: Verify the store migration logic in /electron/main/Store/storeMigrator.ts. Ensure initializeAndMaybeMigrateStore and setupDefaultStoreValues are functioning as expected.

  5. Error Handling: Add error handling to catch and log any JavaScript errors in the main process. This can help identify the root cause of the issue.

References

/.github/ISSUE_TEMPLATE/bug_report.md
/README.md
/electron/main/database/Schema.ts
/electron/main/database/dbSessionHandlers.ts
/.github/ISSUE_TEMPLATE/feature_request.md
/src/components/Settings/InitialSettingsSinglePage.tsx
/electron/main/Files/registerFilesHandler.ts
/.github/ISSUE_TEMPLATE
/electron/main/index.ts
/src/App.tsx
/.github
/.package.json.un~
/vite.config.ts
/src/components/Settings/InitialEmbeddingSettings.tsx
/src/components/Similarity/SimilarFilesSidebar.tsx
/src/components/Settings/ExtraModals/NewEmbeddingModelBothTypes.tsx
/electron/main/database
/electron/main/database/Embeddings.ts
/electron/main/Store/storeMigrator.ts
/src/components/Settings/ExtraModals/NewRemoteEmbeddingModel.tsx
/package.json
/electron/electron-env.d.ts
/electron/preload/index.ts
/electron/main/Store/storeHandlers.ts
/src/components/Settings/HardwareSettings.tsx

About Greptile

This response provides a starting point for your research, not a precise solution.

Help us improve! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

Ask Greptile · Edit Issue Bot Settings

To resolve the persistent 'Initializing vector database...' error on Windows 11, follow these steps:

  1. Check Database Initialization: Ensure the database schema is correctly initialized. Verify the CreateDatabaseSchema function in /electron/main/database/Schema.ts.
  2. Verify LanceDB Table: Confirm the LanceDB table is created correctly. Check the GetOrCreateLanceTable function in /electron/main/database/Lance.ts.
  3. IPC Handlers: Ensure IPC handlers for database operations are correctly set up in /electron/preload/index.ts. Specifically, check handlers like indexFilesInDirectory and getDatabaseFields.
  4. Store Migration: Verify the store migration logic in /electron/main/Store/storeMigrator.ts. Ensure initializeAndMaybeMigrateStore and setupDefaultStoreValues are functioning as expected.
  5. Error Handling: Add error handling to catch and log any JavaScript errors in the main process. This can help identify the root cause of the issue.

References

/.github/ISSUE_TEMPLATE/bug_report.md /README.md /electron/main/database/Schema.ts /electron/main/database/dbSessionHandlers.ts /.github/ISSUE_TEMPLATE/feature_request.md /src/components/Settings/InitialSettingsSinglePage.tsx /electron/main/Files/registerFilesHandler.ts /.github/ISSUE_TEMPLATE /electron/main/index.ts /src/App.tsx /.github /.package.json.un~ /vite.config.ts /src/components/Settings/InitialEmbeddingSettings.tsx /src/components/Similarity/SimilarFilesSidebar.tsx /src/components/Settings/ExtraModals/NewEmbeddingModelBothTypes.tsx /electron/main/database /electron/main/database/Embeddings.ts /electron/main/Store/storeMigrator.ts /src/components/Settings/ExtraModals/NewRemoteEmbeddingModel.tsx /package.json /electron/electron-env.d.ts /electron/preload/index.ts /electron/main/Store/storeHandlers.ts /src/components/Settings/HardwareSettings.tsx

About Greptile

not work

I have the same issue

Unfortunately this seems to be a memory issue :(
So not much I can do given that the app is loading embedding models locally and your systems probably can't handle the load - perhaps you could share with me your hardware configs @yuchiho2008 @phnghia99 ?

Unfortunately this seems to be a memory issue :(不幸的是,這似乎是一個記憶體問題:( So not much I can do given that the app is loading embedding models locally and your systems probably can't handle the load - perhaps you could share with me your hardware configs @yuchiho2008 @phnghia99 ?因此,鑒於該應用程式正在本地載入模型,而您的系統可能無法處理負載,我無能為力 - 也許您可以與我分享您的硬體配置?

Hardware:

Processor: Intel Core i7-8700
RAM: 49,103 MB (approximately 48 GB) of DDR4 RAM.

GTX1070 8GB

Ok in that case, it seems like you both have quite powerful machines @yuchiho2008 @phnghia99 😅

Could you try running Reor from source? Instructions are as follows:

Make sure you have nodejs installed. Run:

git clone https://github.com/reorproject/reor
cd reor
npm install
npm run dev

Then in the terminal, you should be able to see more granular detail about the errors that occur on startup...