-
Notifications
You must be signed in to change notification settings - Fork 96
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
[4.0.7] regression -> gnome secrets crashes on expiration date check with missmatch of date format #382
Comments
This might be related to a2da685 However this can't be reverted on top of current stable. |
A simple fix could be to replace |
Or maybe just replace the |
@City-busz This works for one case, thanks. But I just hit on another one.
So far I have
|
Ah, just replace the line 824 with: It should work in all cases. :) |
The ISO formatted string can be stored in multiple formats. Use the built-in datetime.isoformat() and datetime.fromisoformat() functions, which able to handle all variants. Fixes: libkeepass#382
I submitted #383, which should fix this problem. |
LGTM - With #383 I can open, edit and save both of my files 👍 |
The ISO formatted string can be stored in multiple formats. Use the built-in datetime.isoformat() and datetime.fromisoformat() functions, which able to handle all variants. Replace 'Z' with '+00:00' to ensure compatibility with Python < 3.11. Fixes: libkeepass#382
The ISO formatted string can be stored in multiple formats. Use the built-in datetime.isoformat() and datetime.fromisoformat() functions, which able to handle all variants. Replace 'Z' with '+00:00' to ensure compatibility with Python < 3.11. Fixes: #382
Secrets is a password manager.
After importing #378 to make secrets even build and work (see the PR), secrets now crashes when trying to unlock the .kdbx. It looks like at least one of my expiration dates does have an incompatible format. This shouldn't happen inside a minor release. Rolling back to pykeepass 4.0.6 makes secrets work again.
This is the output I get when starting it from the terminal.
The text was updated successfully, but these errors were encountered: