-
Notifications
You must be signed in to change notification settings - Fork 4
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
How to deal with a full safe (edited) #9
Comments
One possibility is to display the key & value, and offer to skip. |
Thanks for reporting the problem. I should make this error message more user friendly. You have to many entries to fit in the default size of the container. (Actually, it's the combined size of the entries.) Are you sure there are no unnecessarily large entries in there? You can show the entries while importing by adding |
After removing the "trash" folder in KeepassX DB, the import finished successful for 425 items. But the safe is broken apparenly. I get the following error for list, edit, etc. The safe was empty before import.
|
Can you create a new safe and try the import again, but this time adding
|
Hmmm. Cannot reproduce. |
I will try to reproduce the bug you hit. |
The text was updated successfully, but these errors were encountered: