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

GPT4All locks files #3238

Open
dswwood opened this issue Dec 9, 2024 · 1 comment
Open

GPT4All locks files #3238

dswwood opened this issue Dec 9, 2024 · 1 comment
Labels
bug-unconfirmed chat gpt4all-chat issues

Comments

@dswwood
Copy link

dswwood commented Dec 9, 2024

Bug Report

When GPT4ALL is open, files in LocalDocs are locked and cannot be edited or deleted in Windows. The problem occurs in ALL folders that are in LocalDocs whether they are selected in chat or not.

Why is it a problem. I was embedding a fairly large folder which was taking a long time to do. I wanted to create a file that happened to be in one of my other localdocs folders and couldn't because of this problem.

Steps to Reproduce

  1. Open GPT4ALL
  2. Create a new file in one of the localdocs folders
  3. Try to delete or rename the file. It cannot be deleted or renamed. The error box says the file is open in chat.exe.

Expected Behavior

I expect to be able to rename or delete the file. The only way to do it would be to close gpt4all. I assume the reason is that gpt4all opens the files to determine if the embeddings need to updated (whic is GREAT) but doesn't close the file afterwards.

Your Environment

  • GPT4All version: 3.4.2
  • Operating System: Windows 11
  • Chat model used (if applicable):
@dswwood dswwood added bug-unconfirmed chat gpt4all-chat issues labels Dec 9, 2024
@manyoso
Copy link
Collaborator

manyoso commented Dec 10, 2024

This is likely a windows specific issue as it does not occur on Linux. It also could be related to file system permissions on your specific system. We open the files for embedding, but once they are indexed/embedded they are closed. They don't stay open. We do put watches on the file system though to detect when the files change... i wonder if the watches are interfering with the specific file system permissions you have.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-unconfirmed chat gpt4all-chat issues
Projects
None yet
Development

No branches or pull requests

2 participants