You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Open GPT4ALL
Create a new file in one of the localdocs folders
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):
The text was updated successfully, but these errors were encountered:
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.
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
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
The text was updated successfully, but these errors were encountered: